Hmm. This work that you are doing sounds like it might
have value beyond the USB domain. Perhaps you should
be CCing [EMAIL PROTECTED]?
It's important that everyone doing hotplug related work
keep linux-hotplug-devel in the loop.
Cheers,
Miles
Tim Jansen wrote:
>
> On Fri, Mar 30, 2001 at 03:26:54PM -0500, Allen Barnett wrote:
> > after printer.o is loaded, however, there doesn't seem to be enough
> > information passed in from the hotplug invocation to extract the minor
> > device number of the newly plugged in device. (The user-space daemons
> > want to access /dev/usb/lp0, for example.)
>
> I'm working on the device registry patch (www.tjansen.de/devreg) that allows
> you to retrieve the DevFS filename of a physical device. The next release
> will be in a couple of days and adds a DEVICEID environment
> variable to the hotplug invocation. You can use give this device id to
> libdevreg (or lsdevreg in a shell script) to get the name of its device
> nodes.
>
> Note that devreg is experimental code and may be a dead end. I have not
> got any reaction from Linus or other kernel hackers, so I don't know
> whether it has a chance to be included in a official release. And even if
> it does, it wont before 2.5.
>
> bye...
>
> _______________________________________________
> [EMAIL PROTECTED]
> To unsubscribe, use the last form field at:
> http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
