> > > Device IDs can morph due to a power loss. After resumption another > > > driver would bind. > > > > What do you mean? I don't think I quite follow. > > Lots of USB hardware appears as one device id when powered on, then when > the firmware is loaded turns into something else that becomes relevant to > the user. > > So on powerup your wireless card goes > > 'I've no idea what I am, feed me firmware for this id" > > when it gets the firmware it disconnects, reconnects and says > > "I am a USB wireless card with this id" > > When you suspend the power gets killed so the device loses its firmware > and goes back to being a firmware requesting thing on resume. Ah, even worse then. I wasn't aware of devices like this at all. Mhmmmm ... > > Worse still - you don't easily know if the device is in fact new and was > added while suspended, or was always there. Yea, that's the problem I outlined in the subsequent email. > > So for those devices you do need to load the firmware into them > automatically after the resume to work out what they are and get the MAC > to see if its the same wireless card or not. Sure, but then you'd have to wait for userland to actually be ready to feed those. Sometimes, you'd like to avoid that -- for example for devices that are always present. But this solution is stupid as it doesn't solve the whole problem. > > Alan -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
