> > > What about drivers that are loaded by hand, well after the initial device
> > > setup has finished? Would they get a say in choosing a configuration?
> >
> > Certainly they should. In the same way their probe() gets called.
> > It's another way to (implicitly) request a config change.
>
I think at this point we're pretty much in agreement.
On Wed, 13 Aug 2003, David Brownell wrote:
> Yes, choosing between those assumptions/approaches implies design choices
> beyond "usb_set_configuration() needs a task context" and "kernel code
> other than khubd should be able to choose configu
Good morning,
I just noticed that my previous usb_set_configuration() experiment
http://marc.theaimsgroup.com/?l=linux-usb-devel&m=105484578921888&w=2
was the simplified version, without a driver configure() callback.
Posted back in June! No wonder I don't remember it :-) (Quite aside fro
