On Tuesday, 11 of November 2008, Andi Kleen wrote: > > It does. The problem is on the other side: Your power switch presents > > itself as an HID device, so when it is _detected_ it binds to usbhid. > > Ok, but it worked in all kernels before. Why has that changed? > > Looks like a regression to me. Rafael, can you please add it to the list? Done. Thanks, Rafael > > > Why should sispm need to unbind someone else? > > > > The usbfs API does not allow user programs to set a device's > > configuration if any drivers are bound to the device. Therefore, if a > > program wants to set a config then it must unbind all the existing > > drivers first. This is a safety precaution against programs > > interfering with other drivers. > > > > Now in fact, sispm probably doesn't need to set the configuration at > > all. This is undoubtedly a holdover from a Windows version, because > > Windows does not set device configurations by default whereas Linus > > does. > > So you're saying that sispm should be changed to not do something? > What something exactly? And it would work then? > > And why exactly does what it used to do before not work anymore now? -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
