A solution could be to have the mdev.conf file syntax to allow a match for alternate things, like the major/minor pair (which would work at least for devices with fixed assigned pairs).
One possible syntax could be:
--------- mdev.conf ---------
@180,0-15 0:0 660 =usb/ ## /dev/usb/lp{0-15}
@7,0-63 0:0 660 >vc/ ## /dev/vc/{vcs,vcs1,...}
@7,128-191 0:0 660 >vc/ ## /dev/vc/{vcsa,vcsa1,...}
@13,0-31 0:0 660 >input/ ## /dev/input/{js0,js1,...}
@13,32-62 0:0 660 >input/ ## /dev/input/{mouse0,mouse1,...}
@13,63 0:0 660 >input/ ## /dev/input/mice
@13,64-95 0:0 660 >input/ ## /dev/input/{event0,event1,...}
--------- mdev.conf ---------
One possible implication of this scheme (not actually tested) is that the scan task would be faster, as there is no need for regular expression matches for most rules.
Off course, the current rename of the old device would need to be fixed.
I would also vote for an exec rule that would not get called with the device already created (and possibly overwriting a previous one). The major/minor and type of the device file would just get passed by env vars and the executed script/binary would then create the device if needed.
bb-mdev-implement_matching_by_dev_pair.diff [^] (2,813 bytes) 09-04-08 08:20 
