[mythtv-users] dtv, ivtv swapping /dev/video0,1 across reboots

[John Drescher]

On Tue, Jun 22, 2010 at 9:43 PM, Douglas Peale
<Douglas_Peale at comcast.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 06/22/2010 06:12 PM, John Drescher wrote:
>> On Tue, Jun 22, 2010 at 8:21 PM, Harry Coin <hcoin at quietfountain.com> wrote:
>>> I have a debian lenny backend, it has an ivtv card and a dvico dtv card.
>>> Sometimes when it boots the ivtv is video0, and the dtv is video1, sometimes
>>> the dtv is /dev/video0 and the ivtv hauppauge is video1.   I think it has
>>> something to do with how fast firmware loads but I really can't tell.
>>>
>>> How does a person always cause each particular pci card to get the same
>>> /dev/video# is systems with two tuner cards that are not the same mythtv
>>> driver class no matter what?
>>>
>>
>> You can fix that with a udev rule.
>>
>> http://ivtvdriver.org/index.php/Howto#Howto_use_udev_rules.21
>>
>> John
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>
>
> Those instructions require running an application called "udevinfo" which does not exist on Ubuntu, and there does not appear to
> be a way to install it. Are there any more recent instructions?

Sorry. I believe the command

udevadm  info

is the same


jmd0 ~ # udevadm info -a -p /class/video4linux/video0

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device
'/devices/pci0000:00/0000:00:1e.0/0000:05:01.0/0000:06:08.0/video4linux/video0':
    KERNEL=="video0"
    SUBSYSTEM=="video4linux"
    DRIVER==""
    ATTR{name}=="ivtv0 encoder MPG"
    ATTR{index}=="0"

  looking at parent device
'/devices/pci0000:00/0000:00:1e.0/0000:05:01.0/0000:06:08.0':
    KERNELS=="0000:06:08.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="ivtv"
    ATTRS{vendor}=="0x4444"
    ATTRS{device}=="0x0016"
    ATTRS{subsystem_vendor}=="0x0070"
    ATTRS{subsystem_device}=="0xe807"
    ATTRS{class}=="0x040000"
    ATTRS{irq}=="17"
    ATTRS{local_cpus}=="ffffffff,ffffffff"
    ATTRS{local_cpulist}=="0-63"
    ATTRS{modalias}=="pci:v00004444d00000016sv00000070sd0000E807bc04sc00i00"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}==""

  looking at parent device '/devices/pci0000:00/0000:00:1e.0/0000:05:01.0':
    KERNELS=="0000:05:01.0"
    SUBSYSTEMS=="pci"
    DRIVERS==""
    ATTRS{vendor}=="0x3388"
    ATTRS{device}=="0x0021"
    ATTRS{subsystem_vendor}=="0x0000"
    ATTRS{subsystem_device}=="0x0000"
    ATTRS{class}=="0x060400"
    ATTRS{irq}=="0"
    ATTRS{local_cpus}=="ffffffff,ffffffff"
    ATTRS{local_cpulist}=="0-63"
    ATTRS{modalias}=="pci:v00003388d00000021sv00000000sd00000000bc06sc04i00"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}=="1"

  looking at parent device '/devices/pci0000:00/0000:00:1e.0':
    KERNELS=="0000:00:1e.0"
    SUBSYSTEMS=="pci"
    DRIVERS==""
    ATTRS{vendor}=="0x8086"
    ATTRS{device}=="0x244e"
    ATTRS{subsystem_vendor}=="0x0000"
    ATTRS{subsystem_device}=="0x0000"
    ATTRS{class}=="0x060401"
    ATTRS{irq}=="0"
    ATTRS{local_cpus}=="ffffffff,ffffffff"
    ATTRS{local_cpulist}=="0-63"
    ATTRS{modalias}=="pci:v00008086d0000244Esv00000000sd00000000bc06sc04i01"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}=="1"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

John