udev-043

udev-043

[Michael Geithe]

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, pleasereport to 
<linux-hotplug-devel@lists.sourceforge.net>


tree /sys/class/i2c-dev/i2c-2

/sys/class/i2c-dev/i2c-2
|-- dev
|-- device -> ../../../devices/platform/i2c-2
|-- driver -> ../../../bus/i2c/drivers/i2c_adapter
`-- name


ls -l /sys/bus/i2c/devices

7. Nov 03:53 0-0050 
-> ../../../devices/pci0000:00/0000:00:1f.3/i2c-0/0-0050
7. Nov 03:53 0-0052 
-> ../../../devices/pci0000:00/0000:00:1f.3/i2c-0/0-0052
7. Nov 03:53 1-0050 
-> ../../../devices/pci0000:00/0000:00:1e.0/0000:02:02.0/i2c-1/1-0050
7. Nov 03:53 1-0051 
-> ../../../devices/pci0000:00/0000:00:1e.0/0000:02:02.0/i2c-1/1-0051
7. Nov 03:53 1-0052 
-> ../../../devices/pci0000:00/0000:00:1e.0/0000:02:02.0/i2c-1/1-0052
7. Nov 03:53 1-0053 
-> ../../../devices/pci0000:00/0000:00:1e.0/0000:02:02.0/i2c-1/1-0053
7. Nov 03:53 1-0060 
-> ../../../devices/pci0000:00/0000:00:1e.0/0000:02:02.0/i2c-1/1-0060
7. Nov 03:53 2-0290 -> ../../../devices/platform/i2c-2/2-0290



2.6.10-rc1-bk16 #1 SMP Sat Nov 6 19:36:09 CET 2004 i686 Intel(R) Pentium(R) 4 
CPU 2.80GHz GenuineIntel GNU/Linux


thanks

-- 
Michael Geithe









-------------------------------------------------------
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_id\x12065&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

Re: udev-043

[Kay Sievers]

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 
> <linux-hotplug-devel@lists.sourceforge.net>
> 

class:  /sys/class/i2c-dev/i2c-2/
device: /sys/devices/platform/i2c-2
bus:    /sys/bus/i2c/devices/2-0290

Hmm, looks like the "device" link should point to:

  /sys/devices/platform/i2c-2/2-0290

instead, to match the bus link.

Greg, any idea?

Thanks,
Kay
  



-------------------------------------------------------
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_id\x12065&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

Re: udev-043

[Greg KH]

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 
> > <linux-hotplug-devel@lists.sourceforge.net>
> > 
> 
> 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_id\x12065&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

Re: udev-043

[Kay Sievers]

On Mon, 2004-11-08 at 13:18 -0800, Greg KH wrote:
> 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 
> > > <linux-hotplug-devel@lists.sourceforge.net>
> > > 
> > 
> > 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?

I extracted it from Michael's post:
>
> ls -l /sys/bus/i2c/devices
  ...
> 7. Nov 03:53 2-0290 -> ../../../devices/platform/i2c-2/2-0290
>

> > 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 :)

I know nothing about i2c. :)

Hmm, so libsysfs should look for the "bus" at the parent of
the /sys/devices/ device to get the "bus" of _this_ device?

Or should there be one /sys/bus/devices link for every "chip" created by
the kernel?

Kay



-------------------------------------------------------
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_id\x12065&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

Re: udev-043

[Greg KH]

On Mon, Nov 08, 2004 at 11:02:30PM +0100, Kay Sievers wrote:
> On Mon, 2004-11-08 at 13:18 -0800, Greg KH wrote:
> > 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 
> > > > <linux-hotplug-devel@lists.sourceforge.net>
> > > > 
> > > 
> > > 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?
> 
> I extracted it from Michael's post:
> >
> > ls -l /sys/bus/i2c/devices
>   ...
> > 7. Nov 03:53 2-0290 -> ../../../devices/platform/i2c-2/2-0290
> >
> 
> > > 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 :)
> 
> I know nothing about i2c. :)
> 
> Hmm, so libsysfs should look for the "bus" at the parent of
> the /sys/devices/ device to get the "bus" of _this_ device?

Ah, so the "problem" is that there is no bus assigned to this device,
right?  Yeah, I'll agree with that, that's the way the kernel code
works for this device, and for others (like scsi-host "devices" right?)

Hm, I think no bus is correct for this case, as that's what really is
happening.

> Or should there be one /sys/bus/devices link for every "chip" created by
> the kernel?

There should be one in the /sys/bus/i2c/devices directory for every
"i2c chip", but there is nothing in /sys/bus/* for any i2c adapter
devices (think of them as the same way scsi host devices are.)

Does that help?

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_id\x12065&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

Re: udev-043

[Kay Sievers]

On Mon, 2004-11-08 at 14:12 -0800, Greg KH wrote:
> On Mon, Nov 08, 2004 at 11:02:30PM +0100, Kay Sievers wrote:
> > On Mon, 2004-11-08 at 13:18 -0800, Greg KH wrote:
> > > 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 
> > > > > <linux-hotplug-devel@lists.sourceforge.net>
> > > > > 
> > > > 
> > > > 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?
> > 
> > I extracted it from Michael's post:
> > >
> > > ls -l /sys/bus/i2c/devices
> >   ...
> > > 7. Nov 03:53 2-0290 -> ../../../devices/platform/i2c-2/2-0290
> > > 
> > Hmm, so libsysfs should look for the "bus" at the parent of
> > the /sys/devices/ device to get the "bus" of _this_ device?
> 
> Ah, so the "problem" is that there is no bus assigned to this device,
> right? Yeah, I'll agree with that, that's the way the kernel code
> works for this device, and for others (like scsi-host "devices" right?)

Yes, that's what I'm looking for. :)
(Sorry, my question sounds a bit confused)

> Hm, I think no bus is correct for this case, as that's what really is
> happening.

Fine, I will add the "class/i2c-dev/*" device to the list of devices
without a "bus" link.

Thanks,
Kay




-------------------------------------------------------
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_id\x12065&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

Re: udev-043

[Michael Geithe]

Hi,
 
i think it was my stupid lm_sensors.
 
removed lm_sensors.
Compiled all the stuff in my kernel-2.6.10-rc1-bk16 and now it looks much 
cleaner.
 
 ls /sys/bus/i2c/devices
 1-0290  2-0060
 
 ls -l /sys/bus/i2c/devices
 8. Nov 23:27 1-0290 -> ../../../devices/platform/i2c-1/1-0290
 8. Nov 23:27 2-0060 
-> ../../../devices/pci0000:00/0000:00:1e.0/0000:02:02.0/i2c-2/2-0060

 /sys/class/i2c-dev/i2c-0
|-- dev
|-- device -> ../../../devices/pci0000:00/0000:00:1f.3
|-- driver -> ../../../bus/pci/drivers/i801_smbus
`-- name

/sys/class/i2c-dev/i2c-1
|-- dev
|-- device -> ../../../devices/platform/i2c-1
|-- driver -> ../../../bus/i2c/drivers/i2c_adapter
`-- name

 /sys/class/i2c-dev/i2c-2
|-- dev
|-- device -> ../../../devices/pci0000:00/0000:00:1e.0/0000:02:02.0
|-- driver -> ../../../bus/pci/drivers/bttv
`-- name

lspci

0000:00:00.0 Host bridge: Intel Corp. 82875P/E7210 Memory Controller Hub (rev 
02)
0000:00:01.0 PCI bridge: Intel Corp. 82875P Processor to AGP Controller (rev 
02)
0000:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI 
Controller #1 (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI 
Controller #2 (rev 02)
0000:00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 
(rev 02)
0000:00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI 
Controller #4 (rev 02)
0000:00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI 
Controller (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2)
0000:00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Interface 
Bridge (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) IDE Controller 
(rev 02)
0000:00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 
02)
0000:01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 
4200] (rev a3)
0000:02:01.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
0000:02:01.1 Input device controller: Creative Labs SB Audigy MIDI/Game port 
(rev 04)
0000:02:01.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 
04)
0000:02:02.0 Multimedia video controller: Brooktree Corporation Bt878 Video 
Capture (rev 11)
0000:02:02.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture 
(rev 11)
0000:02:03.0 SCSI storage controller: Advanced System Products, Inc ABP940-U / 
ABP960-U (rev 03)
0000:02:08.0 Ethernet controller: Intel Corp. 82562EZ 10/100 Ethernet 
Controller (rev 02)

and finally no udev-messages found in my logs. :)

great work

big thanks

-
Michael Geithe


-------------------------------------------------------
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_id\x12065&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