On Mon, 29 Jan 2007, Oleg Verych wrote:
> On Mon, Jan 29, 2007 at 05:05:56PM +0100, Oliver Neukum wrote:
> > Am Montag, 29. Januar 2007 17:10 schrieb Oleg Verych:
> > > Also, i think usb_set_configuration() must be renamed to
> >
> > There you have a point. It looks like a generally callable API.
> >
> > > sysfs_usb_set_coniguration(). One, that you have wrote for drivers,
> > > and such approach must be removed. 100% configured device, must be
> > > delivered to (USB interface) driver, and if this driver wants to have
> > > {conf#n, interface#k}, please do as it wants on higher levels of setup.
> >
> > Don't we get all that if we try all configurations currently within budget?
>
> I think so. But where are the *options*? I believe, that option must be
> near ID options of a driver. First approximation is ID table, but it's
> bad, inflexible. As more optimized solution, there are may be callback
> functions, or #ifdef magic, as i've wrote before.
>
> USB Core somewhere in its device greeting routine, must check driver,
> that according to ID is going to manage device, for stuff, described
> earlier.
What about adding a table of USB device/vendor/revision IDs together with
preferred config values, so that generic.c's choose_configuration()
routine can handle these special cases?
Alan Stern
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
