I think I'll like this patch ... :-)

One more thing:  the topology information in /proc/bus/usb/devices
doesn't seem to be exposed through reasonable APIs.

I'm wondering what you (and others) would think of adding a new mechanism
to devfs, facilitating exposure of that and other things:  device-specific
ioctls.  A hub device would use these to expose which devices connect to
which ports.  Other devices might expose other information.

A general mechanism there would involve a new driver method (not just
{,un}link_urb, probe/disconnect, also the ioctl) triggered somehow via
the devfs calls.

Such a mechanism might also help address the locking issue that got
some discussion earlier (where there's an impedence mismatch between
the "interface claiming" mechanism and the need prevent arbitrary control
requests going to devices that can't deal with them ... including the case
of devices supporting multiple concurrent drivers (one per interface).

I've not yet drafted such an API proposal; I wanted some feedback on
the notions there first.

_ Dave



----- Original Message -----
From: Johannes Erdfelt <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 26, 2000 2:18 AM
Subject: [linux-usb] [patch] new minor features


> These are some minor patches to add a couple of a new features.
>
> They are from my bigger devfs patch but have nothing to do with devfs.
>
> The features
> - read() from a device now returns cached descriptors as well
> - new GETDRIVER command to see what driver is bound to an interface
>   the only difference from my previous patch is the lack of activated
>   field since it doesn't apply without the userspace binding patch
> - new CONNECTINFO to get device speed and device id
> - serialize all probe() and disconnect() calls to one driver
> - set address before grabbing descriptor
>
> The patch is against 2.4.0-test1.
>
> JE
>
>


----------------------------------------------------------------------------
----


> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to