From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Thu, 18 Nov 2004 18:22:11 +0000 Subject: Re: udev complains about BestCrypt Message-Id: <1100802131.7238.60.camel@localhost.localdomain> List-Id: References: <40070.192.168.1.55.1100744339.squirrel@192.168.1.55> In-Reply-To: <40070.192.168.1.55.1100744339.squirrel@192.168.1.55> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Thu, 2004-11-18 at 10:04 -0800, Greg KH wrote: > On Thu, Nov 18, 2004 at 09:51:32AM -0800, Patrick Mansfield wrote: > > On Thu, Nov 18, 2004 at 02:55:59PM +0100, Kay Sievers wrote: > > > Btw: With kernel 2.6.10 all of these issues will be solved, as the > > > kernel exports in the hotplug environment what we can expect to show up > > > in sysfs. > > > > > > > Is that the PHYSDEVBUS code? > > Yes, it is. It is meant as a hint what is expected to show up in sysfs. > > Why doesn't udev or libsysfs use PHYSDEVBUS to find the bus (I don't see > > any udev code using the value of PHYSDEVBUS)? We have that values only at event time, so libsysfs need to be able to do the reverse lookup anyway. We may give libsysfs a hint where to look first for the bus, but in the most expensive use of it, the udevstart case we can't do this. > Because we _just_ added that to the kernel. > > Give Kay a few days at least :) Yeah, it's already used in wait_for_sysfs. We don't lookup the exception lists if we are on a recent kernel. Thanks, Kay ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ 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