Last Thursday or so, "Dunlap, Randy" wrote:
>
> David Brownell: what features/functionality do you
> think must be added to usbdevfs to make it complete?
I don't believe everything must expand to the point at which it
reads and sends email, for what it's worth!!
Also I'm not sure about expectations for 2.4 usbdevfs, so I'll
just point out a few things that caused trouble when I started
to use devfs:
- Needing root access is just the **wrong** answer.
It should be _easy_ to have desktop tools both scan a
USB and claim access to unclaimed interfaces.
If I can plug and unplug the device, I should be able
to access it logically too (not just physically), with
the same permissions (normal user, physical access to
what passes for the "machine room").
I'm seeing how "mount -o devmode=0666 /proc/bus/usb"
behaves. Of course it should at last be getting read
access always (including GET_DESCRIPTOR and GET_STATUS,
which need write permissions!). I'll see how also
having "write" permission affects interactions with
other driver software, in kernel or in other processes.
- Everything in /proc/bus/usb/devices should be visible
through the .../XXX/YYY files, but I don't know that
it's all available there yet.
If it is, I'm just not sure how to find it all. For
example, the interface binding ioctls don't have a
"say who's bound it" mode, just a "bind it now". I'll
hope that most of the "T:" line is hub info that I've
not parsed yet.
- Hmm, the devfs include file isn't <linux/usbdevfs.h>
but is "/usr/src/linux/drivers/usb/...h" ... if it's
going to become very official, that must change. (I
noticed that the current rio500 tools ship have their
own copy of this kernel header file ... ugh.)
The last of these should be a simple patch.
In general, I think that devfs hasn't been getting enough
use for its feature set to be considered mature enough to
be called complete.
Next on my agenda: look at how interrupt endpoints get
passed through devfs. There wouldn't be anything written
on this, would there?
- Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
