the output *before* any driver install is the same (I've pasted it in this mail).
However the problem could be in Linux as Robert pointed out (the IDs seem to be correctly recognised on Windows).
I'll patch the driver by myself from now on, but my proposal remains to add the possibility to configure the Vendor ID/Device ID before compiling.
I hope it's not a PCI problem, it could be very difficult to find out the reason for it.
Kind regards Paolo
Here is the dump before driver installation:
00:0b.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Subsystem: Unknown device a000:a000
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (3750ns min, 9500ns max)
Interrupt: pin A routed to IRQ 5
Region 0: Memory at dfffc600 (32-bit, non-prefetchable) [size=512]
00: 31 11 46 71 06 00 80 02 01 00 80 04 00 40 00 00
10: 00 c6 ff df 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 a0 00 a0
30: 00 00 00 00 00 00 00 00 00 00 00 00 05 01 0f 26
From: Oliver Endriss <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [linux-dvb] Re: TechnoTrend DVB-T Card PCI Dump (unknown V.ID/Dev.ID)
Date: Tue, 10 Jun 2003 20:02:20 +0200
Paolo Casagranda wrote: > I've dumped the PCI settings with lspci -vxx and this is the section > of interest when the Drivers are installed: > > 00:0b.0 Multimedia controller: Philips Semiconductors SAA7146 (rev > 01) Subsystem: Unknown device a000:a000 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- > Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- > Latency: 64 (3750ns min, 9500ns max) > Interrupt: pin A routed to IRQ 5 > Region 0: Memory at dfffc600 (32-bit, non-prefetchable) [size=512] > 00: 31 11 46 71 06 00 80 02 01 00 80 04 00 40 00 00 > 10: 00 c6 ff df 00 00 00 00 00 00 00 00 00 00 00 00 > 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 a0 00 a0 ^^^^^^^^^^^ > 30: 00 00 00 00 00 00 00 00 00 00 00 00 05 01 0f 26
Looks fine except vendor id/device id (marked ^^^^). Do you get the same values immediately after reboot when the DVB driver has not been loaded yet? If yes, it's not a DVB driver problem. A PCI driver expert should have a look at this.
Oliver
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
_________________________________________________________________
Chiacchiera in tempo reale solo con chi vuoi tu! http://www.msn.it/messenger/
-- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
