Re: LANANA: To Pending Device Number Registrants

[David Brownell]

> > At this point of the discussion I would like to point to the Device Registry 
> > patch (http://www.tjansen.de/devreg) that already solves these problems and 
> > offers stable device ids for the identification of devices and finding their 
> > /dev nodes.
> > 
> > The devreg device id has four components: the bus identifier, the location of 
> > the device (for pci bus number and slot number, for usb the bus number and a 
> > list of port numbers), a model (product and device id) and, if available, a 
> > serial number. 
> 
> Hmm.  It's interesting to me that there have been no replies discussing
> Tim's code.  

I'd want to put it in the context of some of the USB work already done,
and also know how it generalizes to other busses ... 

For example, that usb-devname patch of mine, posted to linux-usb-devel
somewhere around 12/6/2000 (2.4.0-test12), which worked the issue
of teaching USB about "stable" identifiers (like pci slot_name, except
it didn't address functions within device configurations since PCI doesn't
have that notion of "configuration").

Or the patch providing a standard API for USB device drivers to report
what major/minor device numbers are associated with a given interface
(I think it was Alan Barnett who provided that).

Or the original (userspace) XML dump of XML tree structure, shown
at  http://jusb.sourceforge.net/?selected=tree ... it's not clear to me which
structural information there is also found in the "devreg" XML syntax
(from the kernel!), and which isn't.  (Class information omitted from
"devreg"?  Interface structure?)  Most of it's known to be needed.

For example, USB "bus numbers" are themselves unstable identifiers;
PCI slot_name fields work better, at least for host controllers (most!)
which use PCI.  If "devreg" uses "bus numbers", that needs to change.

- Dave