Re: The DRIVER rule doesn't seem to work

[Anthony Wright <anthony@communitymesh.com>]

Kay Sievers wrote:
>> Would it be possible to provide a short explanation of the new 
>> ENV(DRIVER) variable? I had a look at the documentation in 097 and 
>> couldn't find anything.
>>     
> Ok, we hopefully fixed that in 098. Newer kernels will add DRIVER to the
> event environment and udev 098 will just fake the same key for older
> kernels. ENV{DRIVER}= should work now for you, to determine at coldplug
> time, if a device is already bound to a driver.
>   
>> Also, it would be really helpful to understand the DRIVER keyword as 
>> well. Does it now include the device as well as it's parents or still 
>> just the parents? Also, while I'm sure there's a very good reason for 
>> it, I'm still unclear why it's useful for the DRIVER keyword to examine 
>> the device's parents.
>>     
> >From udev 098 on, we will have DRIVERS= (plural) to match all the
> parents, and after a while we will switch DRIVER= to match only the
> event device (like ENV{DRIVER}) to be consistent.
>
> Hope that all works now without using the deprecated PHYSDEV* stuff,
> Kay
>   
This is super, many thanks.

Tony.

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel