[vdr] VDSB with Kernel 2.6.13

[Stephan Schreiber]

Hi Oliver, 

Oliver Endriss wrote:
> There are several versions of Nova-type cards.
> Please provide the sub-system ids (-> "lspci -vn").

Kernel 2.6.12 reports:

0000:02:0a.0 Class 0480: 1131:7146 (rev 01)
        Subsystem: 13c2:100f
        Flags: bus master, medium devsel, latency 64, IRQ 22
        Memory at fbfff800 (32-bit, non-prefetchable) [size=512]

0000:02:0b.0 Class 0480: 1131:7146 (rev 01)
        Subsystem: 13c2:0000
        Flags: bus master, medium devsel, latency 64, IRQ 23
        Memory at fbfff400 (32-bit, non-prefetchable) [size=512]

0000:02:0c.0 Class 0480: 1131:7146 (rev 01)
        Subsystem: 13c2:100f
        Flags: bus master, medium devsel, latency 64, IRQ 20
        Memory at fbfff000 (32-bit, non-prefetchable) [size=512]

0000:02:0d.0 Class 0480: 1131:7146 (rev 01)
        Subsystem: 13c2:100f
        Flags: bus master, medium devsel, latency 64, IRQ 21
        Memory at fbffec00 (32-bit, non-prefetchable) [size=512]


Kernel 2.6.13:

0000:02:0a.0 Class 0480: 1131:7146 (rev 01)
        Subsystem: 13c2:100f
        Flags: bus master, medium devsel, latency 64, IRQ 16
        Memory at fbfff800 (32-bit, non-prefetchable) [size=512]

0000:02:0b.0 Class 0480: 1131:7146 (rev 01)
        Subsystem: 13c2:0000
        Flags: bus master, medium devsel, latency 64, IRQ 18
        Memory at fbfff400 (32-bit, non-prefetchable) [size=512]

0000:02:0c.0 Class 0480: 1131:7146 (rev 01)
        Subsystem: 13c2:100f
        Flags: bus master, medium devsel, latency 64, IRQ 23
        Memory at fbfff000 (32-bit, non-prefetchable) [size=512]

0000:02:0d.0 Class 0480: 1131:7146 (rev 01)
        Subsystem: 13c2:100f
        Flags: bus master, medium devsel, latency 64, IRQ 22
        Memory at fbffec00 (32-bit, non-prefetchable) [size=512]


> > Of course I also tried the latest (yesterday's) CVS driver and the 
> > latest Firmware (fb2620).
> 
> This firmware is not used by budget cards.

Yes I know that, but still some people had reported similar problems,
allegedly due to different driver/firmware combinations...

> Try to find out which change in the driver caused this problem...

There is no change in the driver whatsoever, unfortunately ;-)
The interesting thing is that the driver version does not seem to matter at
all...
It simply works with Kernel 2.6.12, but doesn't with 2.6.13.
I tried the built-in drivers as well as CVS from 28.08.05 and 19.09.05
respectively.
Always same result. 2.6.12 -> no problem, 2.6.13 -> VDSB :-/

> It might be better to report driver bugs on the linux-dvb 
> mailing list.

Yes, sorry, it's been quite a while since I've been subscribed to either
list....
So far, VDR Portal had all the answers I needed...
Next time I'll try to address the correct list ;-)

> Oliver

Thanks,
Stephan