On Tue, Aug 19, 2003 at 09:57:37AM -0400, Alan Cox wrote: > > > People shouldn't be seeing these with newer ones. The only problem we've > > > really had with newer VIA was IRQ routing errors and those turned out to = > > be > > > our fault (and fixed in the newest kernels). > > > > what do you mean for newest kernel? the last 2.4 or the new 2.6? > > Latest 2.4 trees (22rc) and 2.6 test tree I think also got fixed excuse me, but should I enable some particular option? I've compiled a 2.4.22-rc2-ac3 kernel and it doesn't work. At boot time I've got: PCI: PCI BIOS revision 2.10 entry at 0xfb260, last bus=1 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) PCI: Using IRQ router default [1106/3123] at 00:00.0 If I try to read the device I get robot:~/linux-2.4.22-rc2-ac3# cat /dev/video0 cat: /dev/video0: Invalid argument If I give insmod with card=0 I get Aug 20 01:29:56 robot kernel: bttv: driver version 0.7.107 loaded Aug 20 01:29:56 robot kernel: bttv: using 4 buffers with 2080k (8320k total) for capture Aug 20 01:29:56 robot kernel: bttv: Host bridge is VIA Technologies, Inc. VT8623 [Apollo CLE266] Aug 20 01:29:56 robot kernel: bttv: Bt8xx card found (0). Aug 20 01:29:56 robot kernel: bttv0: Bt878 (rev 17) at 00:14.0, irq: 10, latency: 32, mmio: 0xde003000 Aug 20 01:29:56 robot kernel: bttv0: using: BT878( *** UNKNOWN/GENERIC **) [card=0,insmod option] Aug 20 01:29:56 robot kernel: tuner: chip found @ 0xc0 Aug 20 01:29:56 robot kernel: i2c-core.o: client [(tuner unset)] registered to adapter [bt848 #0](pos. 0). Aug 20 01:29:56 robot kernel: i2c-dev.o: Registered 'bt848 #0' as minor 0 Aug 20 01:29:56 robot kernel: i2c-core.o: adapter bt848 #0 registered as adapter 0. Aug 20 01:29:56 robot kernel: bttv: readee error Aug 20 01:29:56 robot kernel: bttv0: using tuner=-1 Aug 20 01:29:56 robot kernel: bttv0: i2c: checking for MSP34xx @ 0x80... not found Aug 20 01:29:56 robot kernel: bttv0: i2c: checking for TDA9875 @ 0xb0... not found Aug 20 01:29:56 robot kernel: bttv0: i2c: checking for TDA7432 @ 0x8a... not found Aug 20 01:29:56 robot kernel: bttv0: registered device video0 Aug 20 01:29:56 robot kernel: bttv0: registered device vbi0 and if I pass the optuion I use on the other computer (crad=70, pll=1, tuner=1 radio=1) I get Aug 20 01:31:40 robot kernel: bttv: driver version 0.7.107 loaded Aug 20 01:31:40 robot kernel: bttv: using 4 buffers with 2080k (8320k total) for capture Aug 20 01:31:40 robot kernel: bttv: Host bridge is VIA Technologies, Inc. VT8623 [Apollo CLE266] Aug 20 01:31:40 robot kernel: bttv: Bt8xx card found (0). Aug 20 01:31:40 robot kernel: bttv0: Bt878 (rev 17) at 00:14.0, irq: 10, latency: 32, mmio: 0xde003000 Aug 20 01:31:40 robot kernel: bttv0: using: BT878(Prolink Pixelview PV-BT) [card=70,insmod option] Aug 20 01:31:40 robot kernel: tuner: chip found @ 0xc0 Aug 20 01:31:40 robot kernel: i2c-core.o: client [(tuner unset)] registered to adapter [bt848 #0](pos. 0). Aug 20 01:31:40 robot kernel: i2c-dev.o: Registered 'bt848 #0' as minor 0 Aug 20 01:31:40 robot kernel: i2c-core.o: adapter bt848 #0 registered as adapter 0. Aug 20 01:31:40 robot kernel: bttv0: using tuner=1 Aug 20 01:31:40 robot kernel: tuner: type set to 1 (Philips PAL_I (FI1246 and compatibles)) Aug 20 01:31:40 robot kernel: bttv0: i2c: checking for MSP34xx @ 0x80... not found Aug 20 01:31:40 robot kernel: bttv0: i2c: checking for TDA9875 @ 0xb0... not found Aug 20 01:31:40 robot kernel: bttv0: i2c: checking for TDA7432 @ 0x8a... not found Aug 20 01:31:40 robot kernel: bttv0: PLL: 28636363 => 35468950 .. ok Aug 20 01:31:40 robot kernel: bttv0: registered device video0 Aug 20 01:31:40 robot kernel: bttv0: registered device vbi0 Aug 20 01:31:40 robot kernel: bttv0: registered device radio0 I don't know what to do... -- Non c'è più forza nella normalità, c'è solo monotonia.
Attachment:
pgpOk147lEQog.pgp
Description: PGP signature
