> > I see. Are you sure about usb_physical_set_conf() ?
> > There might be strange vendor specific webcams or such things that
> > abuse configurations.
>
> The word is "abuse". Setting configurations changes a lot
> of state inside usbcore, and should also interact with the
> HCDs more than it does. I can't think of any reason to
> let a webcam make the innards of usb self-inconsistent.
OK. I am convinced. The next version will do that.
> >>It'd be good if we could set config to zero ... that's the
> >>same state as a device is in after set_address is called.
> >>We don't need it yet ... but it's a good capability to have.
> >
> > Interessting suggestion, but where is the benefit of this over switching
> > over from the default configuration?
>
> That's a policy question. Shouldn't answering that be in the
> hands of the system's sysadmin? But this is a low priority
> issue for me.
>
> I just thought it was worth raising because it's potentially
> useful: it's a part of the usb model that we don't yet
> support; it gives a way to unbind all drivers and keep them
> that way; and it'd let us test that new logic of yours to
> clear away and restore interfaces, both internally and with
> driverfs. (You were just asking for testing support in
> another message ... every device should have both config zero
> and its default! :)
OK. The next version will have it.
Regards
Oliver
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
