Re: UDEV identical devices. How to?

On Tue, Jul 3, 2012 at 11:20 AM, Budnev Vladimir
<[email protected]> wrote:
> We have Debian 2.6.32 and DVB cards with two/four tunners on the each card.
> We want to assign specific number in /dev/dvb/ tree for each tuner.
>
> The problems is that from udev point of view those devices(tuners) are
> absolutely equal(udefinfo gives absolutely identical output), because tuners
> are placed in one dvb card.
>
> We'v googled and found that theoretically we can assign numbers in specific
> order with using ENV options in udev rules.
>
> Here is a working example which creates symlinks:
> # Create a symlinks for both tuners of Kworld device
> SUBSYSTEM=="dvb", ATTRS{idVendor}=="1b80", ATTRS{idProduct}=="e399",
> ENV{kworld}!="two", ENV{kworld}="two", PROGRAM="/bin/sh -c 'K=%k;
> K=$${K#dvb}; printf dvb/adapter_kw1/%%s $${K#*.}'", SYMLINK+="%c"
> SUBSYSTEM=="dvb", ATTRS{idVendor}=="1b80", ATTRS{idProduct}=="e399",
> ENV{kworld}=="two", ENV{kworld}="one", PROGRAM="/bin/sh -c 'K=%k;
> K=$${K#dvb}; printf dvb/adapter_kw2/%%s $${K#*.}'", SYMLINK+="%c"
>
> But we do want devices instead of symlinks, like e.g. /dev/dvb/adapterX
>
> We'v tried such rules, but has no luck:
>
> SUBSYSTEM=="dvb", KERNELS=="0000:04:00.0", ENV{kworld}!="two",
> ENV{kworld}="one", PROGRAM="/bin/sh -c 'K=%k; K=$${K#dvb}; printf
> dvb/adapter1/%%s $${K#*.}'", NAME="%c", GROUP="video"
> SUBSYSTEM=="dvb", KERNELS=="0000:04:00.0", ENV{kworld}=="two",
> ENV{kworld}="one", PROGRAM="/bin/sh -c 'K=%k; K=$${K#dvb}; printf
> dvb/adapter2/%%s $${K#*.}'", NAME="%c", GROUP="video"
>
> Can someone give an advice how to properly construct rules to assign
> devices. It woul be great with an example string
> Mb we missing some global udev option to enable such constructions?

You can't. You have to use symlinks.

http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/5503/focus=5504

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html