Ok...I this is fixed.  Jarod just released some updates that make sure
the drivers are loaded very early as udev starts.  It now creates the
video0 and video1 devices correctly.

[EMAIL PROTECTED] ~]# dmesg | grep bttv                                         
       
bttv: driver version 0.9.15 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 2) at 0000:01:0a.0, irq: 5, latency: 32, mmio: 0xdc000000
bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
bttv0: using: Hauppauge (bt878) [card=10,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00fffffb [init]
bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
bttv0: Hauppauge eeprom: model=62471, tuner=Philips FM1236 (2), radio=yes
bttv0: using tuner=2
bttv0: i2c: checking for MSP34xx @ 0x80... not found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: i2c: checking for TDA9887 @ 0x86... not found
bttv0: registered device video1
bttv0: registered device vbi1
bttv0: registered device radio1
bttv0: PLL: 28636363 => 35468950 .. ok
bttv0: PLL can sleep, using XTAL (28636363).


[EMAIL PROTECTED] ~]# dmesg | grep ivtv
ivtv: no version for "struct_module" found: kernel tainted.
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.2.0 (rc3e) loading
ivtv: Linux version: 2.6.10-1.760_FC3 686 REGPARM 4KSTACKS gcc-3.4
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing the ivtv-devel mailinglist.
ivtv: Autodetected WinTV PVR 250 card
ivtv: Found an iTVC16 based chip
ivtv: Unreasonably low latency timer, setting to 64 (was 32)
ivtv: XXX PCI device: 0x01e0 vendor: 0x10de
ivtv: i2c attach [client=tveeprom[0],ok]
ivtv: Tuner Type 8, Tuner formats 0x00001000, Radio: yes, Model
0x00893496, Revision 0x00000000
ivtv: NTSC tuner detected
ivtv: Radio detected
tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv: i2c attach [client=(tuner unset),ok]
saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
ivtv: i2c attach [client=saa7115[0],ok]
ivtv: i2c attach [client=MSP3448W-A2,ok]
ivtv: Encoder revision: 0x02040024
ivtv: Encoder Firmware is buggy, use version 0x02040011
ivtv: Configuring WinTV PVR 250 card with 5 streams
ivtv: Create DMA stream 0 using 256 16384 byte buffers  4194304 kbytes total
ivtv: Registered v4l2 device, streamtype 0 minor 0
ivtv: Create DMA stream 1
ivtv: Registered v4l2 device, streamtype 1 minor 32
ivtv: Create stream 2 using 40 52224 byte buffers  2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 2 minor 224
ivtv: Create DMA stream 3 using 455 4608 byte buffers  2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 3 minor 24
ivtv: Create stream 4
ivtv: Registered v4l2 device, streamtype 4 minor 64
ivtv: Setting Tuner 8
tuner: type set to 8 (Temic NTSC (4036 FY5)) by ivtv i2c driver #0
ivtv: Setting audio matrix to input 3, output 1
ivtv: Switching standard to NTSC.
ivtv: Initialized WinTV PVR 250, card #0
ivtv: ====================  END INIT IVTV  ====================
ivtv: ivtv_enc_thread: pid = 2292, itv = 0xe097b020
ivtv: i2c attach [client=Hauppauge IR,ok]




On Mon, 21 Feb 2005 13:57:41 -0500, David George <[EMAIL PROTECTED]> wrote:
> On 2/21/2005 1:03 PM, Jason Blair wrote:
> 
> >Also, doesn't this line tell me that the ivtv card is /dev/video0?
> >
> >
> >
> >>ivtv: Initialized WinTV PVR 250, card #0
> >>
> >>
> Nope.  That just means that it is the first ivtv card.
> 
> >
> >If I pull out the bttv card the ivtv card works fine on /dev/video0.
> >I upgraded this machine to FC3 recently, before that with fc2 I had
> >both cards working with the ivtv as video0 and the bttv as video1.
> >
> >
> Interesting.  I am still on FC2.  There is no reason to go to FC3.  The
> only major difference I can think of that would affect this is the new
> UDEV in FC3.
> 
> --
> David
> _______________________________________________
> mythtv-users mailing list
> [email protected]
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Reply via email to