Am Montag, 20. Januar 2003 19:21 schrieb David Brownell:
> Oliver Neukum wrote:
> > Hi,
> >
> > I was just looking at the TODO list and it seemed to me that a list
> > somewhat more specific and focused on usbcore might be useful.
>
> I think the real issue is who will fix the various bugs and issues that
> turn up, but having lists can help focus that energy.

Yes, but bugs in usbcore are most important as they affect everything
in USB.

> > So here's the list of things related to the core I remember so we can
> > look at the issues and see which need attention before 2.6.0
> >
> > - reseting during probe will deadlock
> > - reseting through usbfs will not reprobe
> > - usb_reset_device() and usb_set_configuration() race with probe()
> > - bandwidth checking is broken
> >
> > Removals? Additions? Comments?
>
> Yes, I'll be glad to see more of the usbcore cleanups happen.
> Here are a random bunch of things
>
>   - Someone just emailed me for help on that classic, and still
>     unresolved, issue of associating a device from 'lsusb' (etc)
>     with the right /dev/... printer node.  This is largely an
>     issue usbcore (or the driver model) should solve; it's not
>     specific to printers (or scanners, or any other driver).

Not terribly specific to USB. That's why driverfs was invented,
wasn't it?

>   - Your set_configuration updates should happen -- do you have a
>     current version of that patch?

Still working on it. The old version was racy.

>   - Now that the driver model core supports explicit bind/unbind of
>     drivers to devices, we should get rid of usb_interface->driver
>     since usb_interface->dev.driver does that job.  (This is a case
>     of me needing to update a patch.)
>
>   - usb_set_interface() signature:  should take an interface and an
>     altsetting, not a device and two magic numbers.
>
>   - We should have some notion of device state so that we can make
>     sure that once disconnect processing begins, urb submits fail.
>
>   - I still want to see that nasty synchronization code used by
>     usb_{control,bulk}_msg() get replaced.  (I've got a patch
>     to dust off, but the real issue is that 'struct completion'
>     should have iowait-and-timeout primitives too...)
>
>   - More work can/should be done to merge the "usb_bus" and "hcd"
>     layers.
>
>   - In usb_device we should maintain an array of the current
>     endpoint descriptors, replacing the maxpacket arrays.
>
> That's hardly a complete list of course.

And how much is 2.7? It's a very long list :-(.
I am afraid we'll have to set priorities.

        Regards
                Oliver



-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to