I'm not sure about that. I get this from udev:
babel dev # udevadm info --attribute-walk --name 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 '/class/video4linux/video0':
KERNEL=="video0"
SUBSYSTEM=="video4linux"
DRIVER==""
ATTR{name}==""
ATTR{index}=="0"
--- On Mon, 4/12/10, David Gatwood <[email protected]> wrote:
> From: David Gatwood <[email protected]>
> Subject: Re: [pvrusb2] Is it possible to discriminate between two HVR-1950s?
> To: [email protected]
> Date: Monday, April 12, 2010, 4:52 PM
> On Sat, 10 Apr 2010, Mike Isely
> <[email protected]>
> wrote:
>
> > The pvrusb2 driver itself doesn't do anything to make
> the device's
> > serial number visible to udev. HOWEVER, it was
> later discovered that
> > the udev is seeing the serial number anyway, very
> likely because the
> > number is being provided by the FX2 controller itself
> as part of the
> > generic USB endpoint configuration data.
>
> And even if you don't have a serial number, as long as you
> keep them plugged consistently into the same ports on your
> machine (sans hubs), you should be able to identify them by
> their location.
>
>
> David
>
> _______________________________________________
> pvrusb2 mailing list
> [email protected]
> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
>
_______________________________________________
pvrusb2 mailing list
[email protected]
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
