On Wed, Jun 14, 2000 at 01:05:38PM -0700, Johannes Erdfelt wrote:
> On Tue, Jun 13, 2000, Greg KH <[EMAIL PROTECTED]> wrote:
> > What happens if the configuration changes after the device is reset?
> > Firmware download could cause this to happen.
>
> Hmm, problem. I'll reload the configuration from the device. If it has
> changed, it will not go through the rest of the process of programming
> the active configuration, etc. It will only program the device id.
> The calling driver is then responsible for doing the right thing.
That sounds like a good solution. So the driver will have to pay attention
to the past and then current configuration, correct?
(In reality this is probably a very rare occurrence, so until someone has
some hardware that will do this, I don't really see this as a problem.)
> > If usbdevfs calls the ioctl, then the disconnect and probe will not
> > happen for the driver that is currently connected to this device,
> > correct? That isn't a good thing, is it?
>
> I'll make the ioctl() simulate disconnect() and probe() for all interfaces
> the calling process doesn't have claimed. Sound good?
Yes, I like it.
Randy, I like the current patch, as it is better than what we have now.
And if Johannes changes it to implement the changes he has mentioned, I'll
like it even better.
For those of you who are wondering why I care so much about this, it
relates directly to devices that implement the USB Device Firmware Upgrade
spec (of which I am still trying to find a device that uses this spec, I
know they are out there...)
greg k-h
greg@(kroah|wirex).com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
