Messages in this thread | | | From | Dmitry Torokhov <> | Subject | Re: unify sysfs device tree | Date | Thu, 12 Jan 2006 23:24:49 -0500 |
| |
On Thursday 12 January 2006 20:56, Kay Sievers wrote: > Here is for illustration the "input" layer as a flat /sys/class directory. All > devices point to /sys/devices which exposes the device hierarchy if userspace > wants to know that: > /sys/class/ > ... > |-- input > | |-- input0 -> ../../devices/platform/i8042/serio1/input0 > | |-- input1 -> ../../devices/platform/i8042/serio0/input1 > | |-- input3 -> ../../devices/platform/i8042/serio0/serio2/input3 > | |-- input4 -> ../../devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input4 > | |-- mice -> ../../devices/mice > | |-- mouse0 -> ../../devices/platform/i8042/serio0/input1/mouse0 > | |-- mouse1 -> ../../devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input4/mouse1 > | `-- mouse2 -> ../../devices/platform/i8042/serio0/serio2/input3/mouse2
Looks nice with exception of my standard argument that inputX and mouseX are objects of different (but related) classes.
I believe this also relies on overriding class' methods (release, uevent) by individual devices and inability for class to define standard attributes for such devices. Pretty yucky...
-- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |