On Thu, Mar 04, 2010 at 01:07:05PM -0700, Pete Zaitcev wrote: > On Thu, 04 Mar 2010 09:00:12 -0800 > Dan Williams <dcbw@xxxxxxxxxx> wrote: > > > The problem is that there are a ton more devices that need modeswitching > > than just Huawei, and upstream USB developers are refusing to take > > patches that add more devices to the kernel modeswitching code because > > they assert it should be done in userspace. Thus, usb_modeswitch is the > > only thing that can handle *all* modems that need modeswitching these > > days. Honestly we should just stop adding new Huawei IDs to > > unusual_devs, and just use usb_modeswitch. > > Who are these mysterious kernel developers? You don't happen to have > any e-mail saved? I'm one of those developers. We've hashed this out before. > If Greg Kroah rules that we should promote usb_modeswitch, then fine, > let's do that, and drop all Huawei nonsense from kernel. But I haven't > heard anything like that so far. In fact, the party line was exactly > the opposite: eradicate usb_modeswitch. I'm pretty sure Greg's with me on this one. If the device can be handled in userspace, then it should be. If it's storage emulation mode is not good enough to handle in userspace, then a kernel update will have to be done. My take has always been that it is easier for the distributions to update a userspace tool than to update kernels. It is certainly easier for end-users to update userspace apps rather than their kernel. Thus, we should push the fast-changing add-another-id-this-week stuff into userspace, if at all possible. This also opens up the possibility that someone could get access to the virtual storage on the device, should they need to, without jumping through a lot of hoops. Don't shrug this case off -- it has come up in the past. Matt -- Matthew Dharm Home: mdharm-usb@xxxxxxxxxxxxxxxxxx Maintainer, Linux USB Mass Storage Driver What the hell are you? -- Pitr to Dust Puppy User Friendly, 12/3/1997
Attachment:
pgpJChMZ8Tj4S.pgp
Description: PGP signature
