On Thu, 2008-11-20 at 15:29 -0600, charles zhuang wrote: > Dan, Inaky, > Thanks for the info. I am contacting Asus now to see if they have a > different usb dongle that works for linux out of the box. As I recall, > the previous post from Andrew Zabolotny stated that his dongle can work, > which I believe it's the same model as mine. I can't get response from > Andrew as what he needs to do. > If I get confirmed from Asus that there's no separate dongle for Linux > only, I will definitely have a try as we discuss here, any way I need to > get it going for my project. Will let you guys know once I have any > update. Would be great if you could do it as a patch like I've outlined above, so that we could get it into the upstream kernel and have it Just Work for everyone, without resorting to udev script hackery. Thanks! Dan > Thanks for the quick response. > > Charles > > -----Original Message----- > From: Inaky Perez-Gonzalez [mailto:inaky@xxxxxxxxxxxxxxx] > Sent: Thursday, November 20, 2008 3:21 PM > To: Dan Williams > Cc: charles zhuang; wimax@xxxxxxxxxxxxxx > Subject: Re: usb dongle enumerate as mass storage device > > On Thursday 20 November 2008, Dan Williams wrote: > > On Thu, 2008-11-20 at 10:54 -0800, Inaky Perez-Gonzalez wrote: > > > On Thursday 20 November 2008, Dan Williams wrote: > > > > On Wed, 2008-11-19 at 11:50 -0800, Inaky Perez-Gonzalez wrote: > > > > > > [snip] > > > > > > Oh, so that's how they do it? They wait for a eject command to > "change" > > > personas and become their real device? > > > > Yep. Some Option devices need to be sent the SCSI REZERO command > > instead of a simple eject. Firmware dependent method really. The > > Option 'hso' devices have: > > > > - bDeviceClass 0 (Defined at Interface level) > > - bDeviceSubClass 0 > > - bDeviceProtocol 0 > > + bDeviceClass 255 Vendor Specific Class > > + bDeviceSubClass 255 Vendor Specific Subclass > > + bDeviceProtocol 255 Vendor Specific Protocol > > > > that's - == pre REZERO, + == post REZERO. Same thing for the Huawei > > modems. So you can at least usually tell whether it's supposed to be > > the modem or the mass-storage device on the first plug. > > > > > Out of curiosity, how would it work when the device is reconnected > and/or > > > the system boots? The device requires another eject to switch into > being > > > what it should be? > > > > Yep. On Windows and Mac OS X, the custom drivers that the devices > have > > on their mass-storage CD thing probably handle this for you > > automatically. As should we under Linux :) > > ok, so then we need somebody with enough time on their hands to do that > to see > what is device really reporting as :) > > Thanks for the info! >
