On 16 May 2001 01:56:23 +0200, Tim Jansen wrote:
> On Wednesday 16 May 2001 01:16, David Brownell wrote:
> >Only if it's augmented by additional device IDs, such as the
> >"what 's the physical connection for this interface" sort of
> >primitive that's been mentioned.
> >[...]
> > I suppose that for network interface names, some convention for
> > interface ioctls would suffice to solve that "identify" step. PCI
> > devices would return the slot_name, USB devices need something
> > like a patch I posted to linux-usb-devel a few months back.
>
> 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.
Does your approach solve the problem of USB devices, like mice, that
don't have device ID's of any sort, where topology is the only way to
distinguish them? IIRC, the USB development team was planning to use
topology to provide a limited ability to associate a mouse on a given
port with a display, when XFree86 supports per-Xinerama-display input
device associations.
They new VT console work would benefit from this, too.
Miles
-
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/
This archive was generated by hypermail 2b29 : Tue May 15 2001 - 21:00:47 EST