From: Tim Jansen <tim@tjansen.de>
To: linux-hotplug@vger.kernel.org
Subject: Device Registry (DevReg) Patch 0.2.0
Date: Tue, 24 Apr 2001 01:08:20 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98809173308222@msgid-missing> (raw)
The Linux Device Registry (devreg) is a kernel patch that adds a device
database in XML format to the /proc filesystem. It collects all information
about the system's physical devices, creates persistent device ids and
provides them in the file /proc/devreg.
Devreg has three purposes:
- collect all configuration data from drivers so the user can browse his
hardware configuration.
-allow an application to display all devices that provide a certain interface
(for example all mice) so the user can chose one.
-allow an application to find the device that the user has selected after a
reboot or a hotplug action: the device files in /dev do not offer stable
names, they depend on the order in that the devices have been plugged in or
powered on.
Changes since last release (0.1.1):
- converted file format to XML
- bus-specific information from pci and usb added
- fixed locking
The patch (for 2.4.3) can be found at
http://www.tjansen.de/devreg/devreg-2.4.3-0.2.0.diff.gz
To test it, apply the patch, select CONFIG_DEVFS_FS and CONFIG_DEVREG and
compile. Note that the patch will break binary drivers.
Supported hardware in version 0.2.0: PCI subsystem, USB subsystem, most PCI
sound cards, USB HID devices, USB hubs, USB printers
Other information and a user-space library can be found at
http://www.tjansen.de/devreg
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2001-04-24 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 1:08 Tim Jansen [this message]
2001-04-24 9:40 ` Device Registry (DevReg) Patch 0.2.0 Martin Dalecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-hotplug-98809173308222@msgid-missing \
--to=tim@tjansen.de \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).