From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Wright Date: Mon, 14 Aug 2006 07:29:15 +0000 Subject: Re: The DRIVER rule doesn't seem to work Message-Id: <44E0264B.3010406@communitymesh.com> List-Id: References: <44CCAD5F.9010407@communitymesh.com> In-Reply-To: <44CCAD5F.9010407@communitymesh.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Kay Sievers wrote: > As all the PHYSDEV* variables should go away some day, cause they are > just misleading, describe nothing necessarily 'physical', and 'class' > devices should not have such values at all, we should add a DRIVER= key > to all 'bus' devices as a replacement for the PHYSDEVDRIVER key now. > Then we can could just check with ENV{DRIVER}. I will do this now. > 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. 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. 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&kid0709&bid&3057&dat1642 _______________________________________________ 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