Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: ivtv: devel

Unfair treatment of ivtv8 and ivtv9

 

 

ivtv devel RSS feed   Index | Next | Previous | View Threaded


liontooth at cogweb

Aug 26, 2008, 5:23 PM

Post #1 of 5 (2196 views)
Permalink
Unfair treatment of ivtv8 and ivtv9

On a Debian sid running kernel.org's 2.6.26, I installed five WinTV PVR
500 units. The first nine "encoder MPG" devices are numbered
consecutively 0 through 8.
The ninth, as you can see below, gets confused: ivtv9 "Registered device
video10 for encoder MPG", yet also "Registered device vbi9 for encoder
VBI".

This seems to be happening because video9 has already been used --
"ivtv8: Registered device video9 for encoder PCM" -- breaking the
pattern of a distinct series:

/var/log# grep "encoder PCM" dmesg
ivtv0: Registered device video24 for encoder PCM (320 kB)
ivtv1: Registered device video25 for encoder PCM (320 kB)
ivtv2: Registered device video26 for encoder PCM (320 kB)
ivtv3: Registered device video27 for encoder PCM (320 kB)
ivtv4: Registered device video28 for encoder PCM (320 kB)
ivtv5: Registered device video29 for encoder PCM (320 kB)
ivtv6: Registered device video30 for encoder PCM (320 kB)
ivtv7: Registered device video31 for encoder PCM (320 kB)
ivtv8: Registered device video9 for encoder PCM (320 kB)
ivtv9: Registered device video11 for encoder PCM (320 kB)

ivtv0: Registered device video0 for encoder MPG (4096 kB)
ivtv1: Registered device video1 for encoder MPG (4096 kB)
ivtv2: Registered device video2 for encoder MPG (4096 kB)
ivtv3: Registered device video3 for encoder MPG (4096 kB)
ivtv4: Registered device video4 for encoder MPG (4096 kB)
ivtv5: Registered device video5 for encoder MPG (4096 kB)
ivtv6: Registered device video6 for encoder MPG (4096 kB)
ivtv7: Registered device video7 for encoder MPG (4096 kB)
ivtv8: Registered device video8 for encoder MPG (4096 kB)
ivtv9: Registered device video10 for encoder MPG (4096 kB)

Meanwhile, ivtv9's encoder YUV gets 41 as it should.

Any reason ivtv8 is not getting the video32 it so clearly deserves, and
ivtv9 video33?

I realize this may not be a big social justice issue for everyone, but
it doesn't seem fair.

I'm also guessing I can control this through module parameters, though
we're advised to avoid them.

What can I use as a workaround?

Cheers,
Dave


Aug 26 09:51:22 mcbama kernel: ivtv8: Initializing card #8
Aug 26 09:51:22 mcbama kernel: ivtv8: Autodetected Hauppauge card
(cx23416 based)
Aug 26 09:51:22 mcbama kernel: ACPI: PCI Interrupt 0000:07:08.0[A] ->
Link [APC3] -> GSI 18 (level, low) -> IRQ 18
Aug 26 09:51:22 mcbama kernel: ivtv8: Unreasonably low latency timer,
setting to 64 (was 32)
Aug 26 09:51:22 mcbama kernel: tveeprom 10-0050: Hauppauge model 23552,
rev D492, serial# 8428475
Aug 26 09:51:22 mcbama kernel: tveeprom 10-0050: tuner model is Philips
FQ1236A MK4 (idx 92, type 57)
Aug 26 09:51:22 mcbama kernel: tveeprom 10-0050: TV standards NTSC(M)
(eeprom 0x08)
Aug 26 09:51:22 mcbama kernel: tveeprom 10-0050: second tuner model is
Philips TEA5768HL FM Radio (idx 101, type 62)
Aug 26 09:51:22 mcbama kernel: tveeprom 10-0050: audio processor is
CX25843 (idx 37)
Aug 26 09:51:22 mcbama kernel: tveeprom 10-0050: decoder processor is
CX25843 (idx 30)
Aug 26 09:51:22 mcbama kernel: tveeprom 10-0050: has radio, has no IR
receiver, has no IR transmitter
Aug 26 09:13:14 mcbama kernel: ivtv8: Autodetected WinTV PVR 500 (unit #1)
Aug 26 09:13:14 mcbama kernel: cx25840 10-0044: cx25843-23 found @ 0x88
(ivtv i2c driver #8)
Aug 26 09:13:14 mcbama kernel: tuner 10-0060: chip found @ 0xc0 (ivtv
i2c driver #8)
Aug 26 09:13:14 mcbama kernel: tea5767 10-0060: type set to Philips
TEA5767HN FM Radio
Aug 26 09:13:14 mcbama kernel: tuner 10-0043: chip found @ 0x86 (ivtv
i2c driver #8)
Aug 26 09:13:14 mcbama kernel: tda9887 10-0043: creating new instance
Aug 26 09:13:14 mcbama kernel: tda9887 10-0043: tda988[5/6/7] found
Aug 26 09:13:14 mcbama kernel: tuner 10-0061: chip found @ 0xc2 (ivtv
i2c driver #8)
Aug 26 09:13:14 mcbama kernel: wm8775 10-001b: chip found @ 0x36 (ivtv
i2c driver #8)
Aug 26 09:13:14 mcbama kernel: tuner-simple 10-0061: creating new instance
Aug 26 09:13:14 mcbama kernel: tuner-simple 10-0061: type set to 57
(Philips FQ1236A MK4)
Aug 26 09:13:14 mcbama kernel: ivtv8: Registered device video8 for
encoder MPG (4096 kB)
Aug 26 09:13:14 mcbama kernel: ivtv8: Registered device video40 for
encoder YUV (2048 kB)
Aug 26 09:13:14 mcbama kernel: ivtv8: Registered device vbi8 for encoder
VBI (1024 kB)
Aug 26 09:13:14 mcbama kernel: ivtv8: Registered device video9 for
encoder PCM (320 kB) ***
Aug 26 09:13:14 mcbama kernel: ivtv8: Registered device radio8 for
encoder radio
Aug 26 09:13:14 mcbama kernel: ivtv8: Initialized card #8: WinTV PVR 500
(unit #1)

Aug 26 09:13:14 mcbama kernel: ivtv9: Initializing card #9
Aug 26 09:13:14 mcbama kernel: ivtv9: Autodetected Hauppauge card
(cx23416 based)
Aug 26 09:13:14 mcbama kernel: ACPI: PCI Interrupt 0000:07:09.0[A] ->
Link [APC4] -> GSI 19 (level, low) -> IRQ 19
Aug 26 09:13:14 mcbama kernel: ivtv9: Unreasonably low latency timer,
setting to 64 (was 32)
Aug 26 09:13:14 mcbama kernel: tveeprom 11-0050: Hauppauge model 23552,
rev D492, serial# 8428475
Aug 26 09:13:14 mcbama kernel: tveeprom 11-0050: tuner model is Philips
FQ1236A MK4 (idx 92, type 57)
Aug 26 09:13:14 mcbama kernel: tveeprom 11-0050: TV standards NTSC(M)
(eeprom 0x08)
Aug 26 09:13:14 mcbama kernel: tveeprom 11-0050: second tuner model is
Philips TEA5768HL FM Radio (idx 101, type 62)
Aug 26 09:13:14 mcbama kernel: tveeprom 11-0050: audio processor is
CX25843 (idx 37)
Aug 26 09:13:14 mcbama kernel: tveeprom 11-0050: decoder processor is
CX25843 (idx 30)
Aug 26 09:13:14 mcbama kernel: tveeprom 11-0050: has radio, has no IR
receiver, has no IR transmitter
Aug 26 09:13:14 mcbama kernel: ivtv9: Correcting tveeprom data: no radio
present on second unit
Aug 26 09:13:14 mcbama kernel: ivtv9: Autodetected WinTV PVR 500 (unit #2)
Aug 26 09:13:14 mcbama kernel: cx25840 11-0044: cx25843-23 found @ 0x88
(ivtv i2c driver #9)
Aug 26 09:13:14 mcbama kernel: tuner 11-0043: chip found @ 0x86 (ivtv
i2c driver #9)
Aug 26 09:13:14 mcbama kernel: tda9887 11-0043: creating new instance
Aug 26 09:13:14 mcbama kernel: tda9887 11-0043: tda988[5/6/7] found
Aug 26 09:13:14 mcbama kernel: tuner 11-0061: chip found @ 0xc2 (ivtv
i2c driver #9)
Aug 26 09:13:14 mcbama kernel: wm8775 11-001b: chip found @ 0x36 (ivtv
i2c driver #9)
Aug 26 09:13:14 mcbama kernel: tuner-simple 11-0061: creating new instance
Aug 26 09:13:14 mcbama kernel: tuner-simple 11-0061: type set to 57
(Philips FQ1236A MK4)
Aug 26 09:13:14 mcbama kernel: ivtv9: Registered device video10 for
encoder MPG (4096 kB) ***
Aug 26 09:13:14 mcbama kernel: ivtv9: Registered device video41 for
encoder YUV (2048 kB)
Aug 26 09:13:14 mcbama kernel: ivtv9: Registered device vbi9 for encoder
VBI (1024 kB)
Aug 26 09:13:14 mcbama kernel: ivtv9: Registered device video11 for
encoder PCM (320 kB) ***
Aug 26 09:13:14 mcbama kernel: ivtv9: Initialized card #9: WinTV PVR 500
(unit #2)

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


bolek-mythtv at curl

Aug 26, 2008, 7:44 PM

Post #2 of 5 (2097 views)
Permalink
Re: Unfair treatment of ivtv8 and ivtv9 [In reply to]

David Liontooth wrote:
> On a Debian sid running kernel.org's 2.6.26, I installed five WinTV PVR
> 500 units. The first nine "encoder MPG" devices are numbered
> consecutively 0 through 8.
> The ninth, as you can see below, gets confused: ivtv9 "Registered device
> video10 for encoder MPG", yet also "Registered device vbi9 for encoder
> VBI".
>
> This seems to be happening because video9 has already been used --
> "ivtv8: Registered device video9 for encoder PCM" -- breaking the
> pattern of a distinct series:
>
> /var/log# grep "encoder PCM" dmesg
> ivtv0: Registered device video24 for encoder PCM (320 kB)
> ivtv1: Registered device video25 for encoder PCM (320 kB)
> ivtv2: Registered device video26 for encoder PCM (320 kB)
> ivtv3: Registered device video27 for encoder PCM (320 kB)
> ivtv4: Registered device video28 for encoder PCM (320 kB)
> ivtv5: Registered device video29 for encoder PCM (320 kB)
> ivtv6: Registered device video30 for encoder PCM (320 kB)
> ivtv7: Registered device video31 for encoder PCM (320 kB)
> ivtv8: Registered device video9 for encoder PCM (320 kB)
> ivtv9: Registered device video11 for encoder PCM (320 kB)
>
> ivtv0: Registered device video0 for encoder MPG (4096 kB)
> ivtv1: Registered device video1 for encoder MPG (4096 kB)
> ivtv2: Registered device video2 for encoder MPG (4096 kB)
> ivtv3: Registered device video3 for encoder MPG (4096 kB)
> ivtv4: Registered device video4 for encoder MPG (4096 kB)
> ivtv5: Registered device video5 for encoder MPG (4096 kB)
> ivtv6: Registered device video6 for encoder MPG (4096 kB)
> ivtv7: Registered device video7 for encoder MPG (4096 kB)
> ivtv8: Registered device video8 for encoder MPG (4096 kB)
> ivtv9: Registered device video10 for encoder MPG (4096 kB)
>
> Meanwhile, ivtv9's encoder YUV gets 41 as it should.
>
> Any reason ivtv8 is not getting the video32 it so clearly deserves, and
> ivtv9 video33?

video32 is normally used by ivtv0 for the raw YUV capture:

$ dmesg | egrep 'ivtv.*Registered'
ivtv0: Registered device video0 for encoder MPG (4096 kB)
ivtv0: Registered device video32 for encoder YUV (2048 kB)
ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
ivtv0: Registered device video24 for encoder PCM (320 kB)
ivtv0: Registered device radio0 for encoder radio
ivtv0: Registered device video16 for decoder MPG (1024 kB)
ivtv0: Registered device vbi8 for decoder VBI (64 kB)
ivtv0: Registered device vbi16 for decoder VOUT
ivtv0: Registered device video48 for decoder YUV (1024 kB)

It is possible that ivtv (or maybe v4l) does not support more than 8
devices, at least without some trickery.

Bolek

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


hverkuil at xs4all

Aug 26, 2008, 11:04 PM

Post #3 of 5 (2075 views)
Permalink
Re: Unfair treatment of ivtv8 and ivtv9 [In reply to]

On Wednesday 27 August 2008 02:23:45 David Liontooth wrote:
>
> On a Debian sid running kernel.org's 2.6.26, I installed five WinTV
PVR
> 500 units. The first nine "encoder MPG" devices are numbered
> consecutively 0 through 8.
> The ninth, as you can see below, gets confused: ivtv9 "Registered
device
> video10 for encoder MPG", yet also "Registered device vbi9 for encoder
> VBI".

With more than eight devices the numbering goes off. Basically the
encoder PCM numbering bumps into the range of the encoder YUV devices,
so at that point it starts using the first free numbers.

Can't do anything about that, I'm afraid.

Regards,

Hans

>
> This seems to be happening because video9 has already been used --
> "ivtv8: Registered device video9 for encoder PCM" -- breaking the
> pattern of a distinct series:
>
> /var/log# grep "encoder PCM" dmesg
> ivtv0: Registered device video24 for encoder PCM (320 kB)
> ivtv1: Registered device video25 for encoder PCM (320 kB)
> ivtv2: Registered device video26 for encoder PCM (320 kB)
> ivtv3: Registered device video27 for encoder PCM (320 kB)
> ivtv4: Registered device video28 for encoder PCM (320 kB)
> ivtv5: Registered device video29 for encoder PCM (320 kB)
> ivtv6: Registered device video30 for encoder PCM (320 kB)
> ivtv7: Registered device video31 for encoder PCM (320 kB)
> ivtv8: Registered device video9 for encoder PCM (320 kB)
> ivtv9: Registered device video11 for encoder PCM (320 kB)
>
> ivtv0: Registered device video0 for encoder MPG (4096 kB)
> ivtv1: Registered device video1 for encoder MPG (4096 kB)
> ivtv2: Registered device video2 for encoder MPG (4096 kB)
> ivtv3: Registered device video3 for encoder MPG (4096 kB)
> ivtv4: Registered device video4 for encoder MPG (4096 kB)
> ivtv5: Registered device video5 for encoder MPG (4096 kB)
> ivtv6: Registered device video6 for encoder MPG (4096 kB)
> ivtv7: Registered device video7 for encoder MPG (4096 kB)
> ivtv8: Registered device video8 for encoder MPG (4096 kB)
> ivtv9: Registered device video10 for encoder MPG (4096 kB)
>
> Meanwhile, ivtv9's encoder YUV gets 41 as it should.
>
> Any reason ivtv8 is not getting the video32 it so clearly deserves,
and
> ivtv9 video33?
>
> I realize this may not be a big social justice issue for everyone, but
> it doesn't seem fair.
>
> I'm also guessing I can control this through module parameters, though
> we're advised to avoid them.
>
> What can I use as a workaround?
>
> Cheers,
> Dave
>
>
> Aug 26 09:51:22 mcbama kernel: ivtv8: Initializing card #8
> Aug 26 09:51:22 mcbama kernel: ivtv8: Autodetected Hauppauge card
> (cx23416 based)
> Aug 26 09:51:22 mcbama kernel: ACPI: PCI Interrupt 0000:07:08.0[A] ->
> Link [APC3] -> GSI 18 (level, low) -> IRQ 18
> Aug 26 09:51:22 mcbama kernel: ivtv8: Unreasonably low latency timer,
> setting to 64 (was 32)
> Aug 26 09:51:22 mcbama kernel: tveeprom 10-0050: Hauppauge model
23552,
> rev D492, serial# 8428475
> Aug 26 09:51:22 mcbama kernel: tveeprom 10-0050: tuner model is
Philips
> FQ1236A MK4 (idx 92, type 57)
> Aug 26 09:51:22 mcbama kernel: tveeprom 10-0050: TV standards NTSC(M)
> (eeprom 0x08)
> Aug 26 09:51:22 mcbama kernel: tveeprom 10-0050: second tuner model is
> Philips TEA5768HL FM Radio (idx 101, type 62)
> Aug 26 09:51:22 mcbama kernel: tveeprom 10-0050: audio processor is
> CX25843 (idx 37)
> Aug 26 09:51:22 mcbama kernel: tveeprom 10-0050: decoder processor is
> CX25843 (idx 30)
> Aug 26 09:51:22 mcbama kernel: tveeprom 10-0050: has radio, has no IR
> receiver, has no IR transmitter
> Aug 26 09:13:14 mcbama kernel: ivtv8: Autodetected WinTV PVR 500 (unit
#1)
> Aug 26 09:13:14 mcbama kernel: cx25840 10-0044: cx25843-23 found @
0x88
> (ivtv i2c driver #8)
> Aug 26 09:13:14 mcbama kernel: tuner 10-0060: chip found @ 0xc0 (ivtv
> i2c driver #8)
> Aug 26 09:13:14 mcbama kernel: tea5767 10-0060: type set to Philips
> TEA5767HN FM Radio
> Aug 26 09:13:14 mcbama kernel: tuner 10-0043: chip found @ 0x86 (ivtv
> i2c driver #8)
> Aug 26 09:13:14 mcbama kernel: tda9887 10-0043: creating new instance
> Aug 26 09:13:14 mcbama kernel: tda9887 10-0043: tda988[5/6/7] found
> Aug 26 09:13:14 mcbama kernel: tuner 10-0061: chip found @ 0xc2 (ivtv
> i2c driver #8)
> Aug 26 09:13:14 mcbama kernel: wm8775 10-001b: chip found @ 0x36 (ivtv
> i2c driver #8)
> Aug 26 09:13:14 mcbama kernel: tuner-simple 10-0061: creating new
instance
> Aug 26 09:13:14 mcbama kernel: tuner-simple 10-0061: type set to 57
> (Philips FQ1236A MK4)
> Aug 26 09:13:14 mcbama kernel: ivtv8: Registered device video8 for
> encoder MPG (4096 kB)
> Aug 26 09:13:14 mcbama kernel: ivtv8: Registered device video40 for
> encoder YUV (2048 kB)
> Aug 26 09:13:14 mcbama kernel: ivtv8: Registered device vbi8 for
encoder
> VBI (1024 kB)
> Aug 26 09:13:14 mcbama kernel: ivtv8: Registered device video9 for
> encoder PCM (320 kB) ***
> Aug 26 09:13:14 mcbama kernel: ivtv8: Registered device radio8 for
> encoder radio
> Aug 26 09:13:14 mcbama kernel: ivtv8: Initialized card #8: WinTV PVR
500
> (unit #1)
>
> Aug 26 09:13:14 mcbama kernel: ivtv9: Initializing card #9
> Aug 26 09:13:14 mcbama kernel: ivtv9: Autodetected Hauppauge card
> (cx23416 based)
> Aug 26 09:13:14 mcbama kernel: ACPI: PCI Interrupt 0000:07:09.0[A] ->
> Link [APC4] -> GSI 19 (level, low) -> IRQ 19
> Aug 26 09:13:14 mcbama kernel: ivtv9: Unreasonably low latency timer,
> setting to 64 (was 32)
> Aug 26 09:13:14 mcbama kernel: tveeprom 11-0050: Hauppauge model
23552,
> rev D492, serial# 8428475
> Aug 26 09:13:14 mcbama kernel: tveeprom 11-0050: tuner model is
Philips
> FQ1236A MK4 (idx 92, type 57)
> Aug 26 09:13:14 mcbama kernel: tveeprom 11-0050: TV standards NTSC(M)
> (eeprom 0x08)
> Aug 26 09:13:14 mcbama kernel: tveeprom 11-0050: second tuner model is
> Philips TEA5768HL FM Radio (idx 101, type 62)
> Aug 26 09:13:14 mcbama kernel: tveeprom 11-0050: audio processor is
> CX25843 (idx 37)
> Aug 26 09:13:14 mcbama kernel: tveeprom 11-0050: decoder processor is
> CX25843 (idx 30)
> Aug 26 09:13:14 mcbama kernel: tveeprom 11-0050: has radio, has no IR
> receiver, has no IR transmitter
> Aug 26 09:13:14 mcbama kernel: ivtv9: Correcting tveeprom data: no
radio
> present on second unit
> Aug 26 09:13:14 mcbama kernel: ivtv9: Autodetected WinTV PVR 500 (unit
#2)
> Aug 26 09:13:14 mcbama kernel: cx25840 11-0044: cx25843-23 found @
0x88
> (ivtv i2c driver #9)
> Aug 26 09:13:14 mcbama kernel: tuner 11-0043: chip found @ 0x86 (ivtv
> i2c driver #9)
> Aug 26 09:13:14 mcbama kernel: tda9887 11-0043: creating new instance
> Aug 26 09:13:14 mcbama kernel: tda9887 11-0043: tda988[5/6/7] found
> Aug 26 09:13:14 mcbama kernel: tuner 11-0061: chip found @ 0xc2 (ivtv
> i2c driver #9)
> Aug 26 09:13:14 mcbama kernel: wm8775 11-001b: chip found @ 0x36 (ivtv
> i2c driver #9)
> Aug 26 09:13:14 mcbama kernel: tuner-simple 11-0061: creating new
instance
> Aug 26 09:13:14 mcbama kernel: tuner-simple 11-0061: type set to 57
> (Philips FQ1236A MK4)
> Aug 26 09:13:14 mcbama kernel: ivtv9: Registered device video10 for
> encoder MPG (4096 kB) ***
> Aug 26 09:13:14 mcbama kernel: ivtv9: Registered device video41 for
> encoder YUV (2048 kB)
> Aug 26 09:13:14 mcbama kernel: ivtv9: Registered device vbi9 for
encoder
> VBI (1024 kB)
> Aug 26 09:13:14 mcbama kernel: ivtv9: Registered device video11 for
> encoder PCM (320 kB) ***
> Aug 26 09:13:14 mcbama kernel: ivtv9: Initialized card #9: WinTV PVR
500
> (unit #2)
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>



_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


liontooth at cogweb

Aug 27, 2008, 7:13 AM

Post #4 of 5 (2088 views)
Permalink
Re: Unfair treatment of ivtv8 and ivtv9 [In reply to]

Hans Verkuil wrote:
> On Wednesday 27 August 2008 02:23:45 David Liontooth wrote:
>
>> On a Debian sid running kernel.org's 2.6.26, I installed five WinTV
>>
> PVR
>
>> 500 units. The first nine "encoder MPG" devices are numbered
>> consecutively 0 through 8.
>> The ninth, as you can see below, gets confused: ivtv9 "Registered
>>
> device
>
>> video10 for encoder MPG", yet also "Registered device vbi9 for encoder
>> VBI".
>>
>
> With more than eight devices the numbering goes off. Basically the
> encoder PCM numbering bumps into the range of the encoder YUV devices,
> so at that point it starts using the first free numbers.
>
> Can't do anything about that, I'm afraid.
>
Thanks, I see how it works. Can I renumber the devices using module
parameters? My scripts assume the mpg and vbi devices have the same number.

For saa7134 I use /etc/modprobe.d/saa7134:

options saa7134 card=95,95,95,95,95 tuner=39,39,39,39,39
video_nr=1,2,3,4,5 vbi_nr=1,2,3,4,5 radio_nr=1,2,3,4,5 disable_ir=1,1,1,1,1

# Work around udev
install saa7134 /sbin/modprobe --ignore-install saa7134; /sbin/modprobe
saa7134-alsa

# Alsa
options saa7134-alsa index=1,2,3,4,5

Can I still pass device option numbers to the ivtv devices?

An alternative simple fix would be to add a zero to the other devices,
since udev now generates nodes on the fly anyway, but I guess demand is
modest. If you can point me to the code I may give it a try.

Dave



_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel


liontooth at cogweb

Aug 27, 2008, 7:44 PM

Post #5 of 5 (2047 views)
Permalink
Re: Unfair treatment of ivtv8 and ivtv9 [In reply to]

David Liontooth wrote:
> Hans Verkuil wrote:
>
>> On Wednesday 27 August 2008 02:23:45 David Liontooth wrote:
>>
>>
>>> On a Debian sid running kernel.org's 2.6.26, I installed five WinTV PVR500 units. The first nine "encoder MPG" devices are numbered
>>> consecutively 0 through 8. The ninth, as you can see below, gets confused: ivtv9 "Registered device
>>> video10 for encoder MPG", yet also "Registered device vbi9 for encoder VBI".
>>>
>>>
>> With more than eight devices the numbering goes off. Basically the
>> encoder PCM numbering bumps into the range of the encoder YUV devices,
>> so at that point it starts using the first free numbers.
>>
>> Can't do anything about that, I'm afraid.
>>
>>
> Thanks, I see how it works. Can I renumber the devices using module
> parameters? My scripts assume the mpg and vbi devices have the same number.
>
Ian Campbell, the Debian maintainer of ivtv-utils, suggested a
workaround using udev; I've added the following, which creates device
node symlinks.
It solves my problem and lets me use the same scripts for experimenting
with raw capture.

Cheers,
Dave


# /etc/udev/rules.d/ivtv.rules

BUS=="pci", KERNELS=="0000:03:08.0", ATTR{name}=="ivtv* encoder MPG",
SYMLINK+="video/mpg0"
BUS=="pci", KERNELS=="0000:03:09.0", ATTR{name}=="ivtv* encoder MPG",
SYMLINK+="video/mpg1"
BUS=="pci", KERNELS=="0000:04:08.0", ATTR{name}=="ivtv* encoder MPG",
SYMLINK+="video/mpg2"
BUS=="pci", KERNELS=="0000:04:09.0", ATTR{name}=="ivtv* encoder MPG",
SYMLINK+="video/mpg3"
BUS=="pci", KERNELS=="0000:05:08.0", ATTR{name}=="ivtv* encoder MPG",
SYMLINK+="video/mpg4"
BUS=="pci", KERNELS=="0000:05:09.0", ATTR{name}=="ivtv* encoder MPG",
SYMLINK+="video/mpg5"
BUS=="pci", KERNELS=="0000:06:08.0", ATTR{name}=="ivtv* encoder MPG",
SYMLINK+="video/mpg6"
BUS=="pci", KERNELS=="0000:06:09.0", ATTR{name}=="ivtv* encoder MPG",
SYMLINK+="video/mpg7"
BUS=="pci", KERNELS=="0000:07:08.0", ATTR{name}=="ivtv* encoder MPG",
SYMLINK+="video/mpg8"
BUS=="pci", KERNELS=="0000:07:09.0", ATTR{name}=="ivtv* encoder MPG",
SYMLINK+="video/mpg9"

BUS=="pci", KERNELS=="0000:03:08.0", ATTR{name}=="ivtv* encoder YUV",
SYMLINK+="video/yuv0"
BUS=="pci", KERNELS=="0000:03:09.0", ATTR{name}=="ivtv* encoder YUV",
SYMLINK+="video/yuv1"
BUS=="pci", KERNELS=="0000:04:08.0", ATTR{name}=="ivtv* encoder YUV",
SYMLINK+="video/yuv2"
BUS=="pci", KERNELS=="0000:04:09.0", ATTR{name}=="ivtv* encoder YUV",
SYMLINK+="video/yuv3"
BUS=="pci", KERNELS=="0000:05:08.0", ATTR{name}=="ivtv* encoder YUV",
SYMLINK+="video/yuv4"
BUS=="pci", KERNELS=="0000:05:09.0", ATTR{name}=="ivtv* encoder YUV",
SYMLINK+="video/yuv5"
BUS=="pci", KERNELS=="0000:06:08.0", ATTR{name}=="ivtv* encoder YUV",
SYMLINK+="video/yuv6"
BUS=="pci", KERNELS=="0000:06:09.0", ATTR{name}=="ivtv* encoder YUV",
SYMLINK+="video/yuv7"
BUS=="pci", KERNELS=="0000:07:08.0", ATTR{name}=="ivtv* encoder YUV",
SYMLINK+="video/yuv8"
BUS=="pci", KERNELS=="0000:07:09.0", ATTR{name}=="ivtv* encoder YUV",
SYMLINK+="video/yuv9"

BUS=="pci", KERNELS=="0000:03:08.0", ATTR{name}=="ivtv* encoder PCM",
SYMLINK+="video/pcm0"
BUS=="pci", KERNELS=="0000:03:09.0", ATTR{name}=="ivtv* encoder PCM",
SYMLINK+="video/pcm1"
BUS=="pci", KERNELS=="0000:04:08.0", ATTR{name}=="ivtv* encoder PCM",
SYMLINK+="video/pcm2"
BUS=="pci", KERNELS=="0000:04:09.0", ATTR{name}=="ivtv* encoder PCM",
SYMLINK+="video/pcm3"
BUS=="pci", KERNELS=="0000:05:08.0", ATTR{name}=="ivtv* encoder PCM",
SYMLINK+="video/pcm4"
BUS=="pci", KERNELS=="0000:05:09.0", ATTR{name}=="ivtv* encoder PCM",
SYMLINK+="video/pcm5"
BUS=="pci", KERNELS=="0000:06:08.0", ATTR{name}=="ivtv* encoder PCM",
SYMLINK+="video/pcm6"
BUS=="pci", KERNELS=="0000:06:09.0", ATTR{name}=="ivtv* encoder PCM",
SYMLINK+="video/pcm7"
BUS=="pci", KERNELS=="0000:07:08.0", ATTR{name}=="ivtv* encoder PCM",
SYMLINK+="video/pcm8"
BUS=="pci", KERNELS=="0000:07:09.0", ATTR{name}=="ivtv* encoder PCM",
SYMLINK+="video/pcm9"



_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

ivtv devel RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.