Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
26 lines
1.0 KiB
Plaintext
26 lines
1.0 KiB
Plaintext
What: /sys/devices
|
|
Date: February 2006
|
|
Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|
Description:
|
|
The /sys/devices tree contains a snapshot of the
|
|
internal state of the kernel device tree. Devices will
|
|
be added and removed dynamically as the machine runs,
|
|
and between different kernel versions, the layout of the
|
|
devices within this tree will change.
|
|
|
|
Please do not rely on the format of this tree because of
|
|
this. If a program wishes to find different things in
|
|
the tree, please use the /sys/class structure and rely
|
|
on the symlinks there to point to the proper location
|
|
within the /sys/devices tree of the individual devices.
|
|
Or rely on the uevent messages to notify programs of
|
|
devices being added and removed from this tree to find
|
|
the location of those devices.
|
|
|
|
Note that sometimes not all devices along the directory
|
|
chain will have emitted uevent messages, so userspace
|
|
programs must be able to handle such occurrences.
|
|
|
|
Users:
|
|
udev <linux-hotplug-devel@lists.sourceforge.net>
|