From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Mon, 08 Nov 2004 21:18:33 +0000 Subject: Re: udev-043 Message-Id: <20041108211833.GA19891@kroah.com> List-Id: References: <200411070449.21228.warpy@gmx.de> In-Reply-To: <200411070449.21228.warpy@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Mon, Nov 08, 2004 at 10:00:54PM +0100, Kay Sievers wrote: > On Sun, 2004-11-07 at 04:49 +0100, Michael Geithe wrote: > > Hi, > > > > only one udev-message found in my logs ;-) > > > > wait_for_sysfs[10013]: either wait_for_sysfs (udev 043) needs an update to > > handle the device '/class/i2c-dev/i2c-2' properly (no bus device link) or the > > sysfs-support of your device's driver needs to be fixed, please report to > > > > > > class: /sys/class/i2c-dev/i2c-2/ > device: /sys/devices/platform/i2c-2 > bus: /sys/bus/i2c/devices/2-0290 Where do you get this "bus:" info from? > Hmm, looks like the "device" link should point to: > > /sys/devices/platform/i2c-2/2-0290 > > instead, to match the bus link. No, the i2c-2 class device points to the i2c-2 adapter device. Now, that adapter device can "find" a number of individual i2c chip devices that i2c chip drivers can then bind to. Those chip devices are the "2-0290" and such devices. Make more sense? Yeah, it's a mess, sorry, but the i2c code isn't the nicest either :) thanks, greg k-h ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88&alloc_id065&op=click _______________________________________________ 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