On Thu, Jun 28, 2007 at 02:53:22PM -0700, David Brownell wrote: > > Let's start with *JUST* a driver, not trying to update everything > else in the USB Gadget stack so that it looks like it's designed > specifically to handle all of Intel's design botches related to > endpoint config ... and work worse for essentially everything else. > > (Unlike pretty much every other vendor, Intel wanted hardware config > management. It was unusably buggy in pxa21x/25x/26x, and not much > better in pxa27x.) > > > So in technical terms, and to repeat what I've said before: just > configure it to act more like a PXA 25x chip (no altsettings) and > get it so it passes all the tests [1], modulo errata which have no > workarounds ... then submit that. No epautoconfig updates, no > patches to every gadget driver to cope with updated autoconfig.
This looks interesting... as you alredy told this driver derives from an older one, I just maintained it till now. If I well understand I should remove usb_ep_autoconfig() and program into the controller only one (the default) configuration. Is that right? Currently I tested the driver only with ether gadget, but if I do as above, should I get the driver working with all gadgets automagically? :) Thanks a lot, Rodolfo -- GNU/Linux Solutions e-mail: [EMAIL PROTECTED] Linux Device Driver [EMAIL PROTECTED] Embedded Systems [EMAIL PROTECTED] UNIX programming phone: +39 349 2432127 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
