Re: USB Serial Converter driver and multiple devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On Wed, 2012-05-16 at 15:59 -0500, Dan Williams wrote:
> On Wed, 2012-05-16 at 23:44 +0300, Olli Helin wrote:
> > > > > I downloaded the Gobi Serial driver "template" from CodeAurora home
> > > > > page, added the product info USB_DEVICE( 0x1c9e, 0x9801 ), and added
> > > > > an include clause for compiling on Linux 3.x. So far no problems. What
> > > > > would be the correct module to patch in the Linux kernel then? I guess
> > > > > USB Qualcomm Serial modem, no?
> > > > 
> > > > No, try the option driver.  You can add the device id to the new_id
> > > > sysfs file for the driver and see if that works out properly.  If so,
> > > > create a patch following the information in the
> > > > Documentation/SubmittingPatches file and send it to us so I can apply
> > > > it.
> > > 
> > > No, not option.  If it's a Gobi-derived device, then it needs IDs in
> > > qcserial, qmi_wwan, and possibly fixups for cdc-wdm.  Gobi devices
> > > should *never* be handled by option.
> > > 
> > > Dan
> > 
> > I caught a flu so I did not go into patching yet; however, I just tested the option driver by echoing the vendor and device IDs to the new_id file in sysfs and everything seems to be working correctly, I'm sending this mail with the option driver in use. About maximum speeds I am not yet sure, need to use this for a while. Is it possible that this device is some kind of abomination which can be used with pretty much every driver out there? Also, the vendor ID matches one already in the option driver, LONGCHEER_VENDOR_ID 0x1c9e, which covers quite a lot of smaller brand names.
> 
> Does this device need modeswitching?  If it does, would you mind tar-ing
> up the fake driver CD before it's modeswitched and sending it to me?  I
> can look at the driver and figure out what kind of device it really is.

Nevermind, I found some drivers for it.  It does indeed appear to be a
Gobi-derived device, as you've found from the CodeAurora drivers.  It
should be driven by qcserial and qmi_wwan.  Can you grab 'lsusb -v -d
1c9e:9801' after modeswitch for me?  We need to find out what class of
gobi it is.

The rough mapping between codeaurora drivers and the upstream is:

QCUSBNet = qmi_wwan
QCSerial = qcserial

Dan

--
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


B and H Foto and Electronics Corp.

[Linux Media]     [Video for Linux]     [Linux Input]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Free Online Dating]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]     [More Archives]

Add to Google Powered by Linux