On Mon, 2016-02-22 at 18:03 +0700, Lars Melin wrote: > On 2016-02-21 10:09, Daniel Johnson wrote: > > On Fri, Feb 19, 2016 at 12:27 AM, Bjørn Mork <bjorn@xxxxxxx> wrote: > > > One of them is likely a QCDM port if this is really a Qualcomm > > > based > > > device. The other might be an inactive NMEA port. Serial > > > doesn't > > > necessarily imply AT commands... > > > > I found the FCC ID for the device. > > QISME206V-561 > > > > Searching for this at the FCC website revealed internal photos. > > Looks > > like it's Intel based. The significant non intel parts seem to be > > DRAM, and a radio amplifier. > > https://www.fcc.gov/general/fcc-id-search-page > > -- > > 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 > > > > The serial interfaces should be handled by the option serial driver > which btw already has support for it. > > qcserial will fight with option for ownership of the interfaces so > the > currently defined DEVICE_HWI(0x03f0, 0x581d) should be taken out of > qcserial. Bjorn? If it's an Intel device, which it certainly looks like from the FCC photos, then it should not be in qcserial at all. The Windows driver config and the usb-devices dumps indicate that instead of the normal Intel cdc-acm/mbim configuration that this device uses a Huawei- specific layout like their Qualcomm-based devices. So this device should probably go into 'option' for Cfg#1 (Jungo) and Cfg#2 (cdc_ether) and it'll certainly need locking on specific Class/SubClass/Protocol to ensure that option only claims the serial interfaces and not the ethernet/ncm ones. Dan > /Lars > > > -- > 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 -- 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
