Re: 03f0:521d Hewlett-Packard (HP hs3110)

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

 



Hello,

As I have started this discussion, I'd like to assure you that I'm 
willing to do any tests you want/need in order to clarify it. Even a 
teamviewer session can be an option if needed.

Thanks,
Victor

On 07/23/2014 11:52 AM, Bjørn Mork wrote:
> Lars Melin <larsm17@xxxxxxxxx> writes:
>> On 2014-07-23 04:17, Dan Williams wrote:
>>> On Tue, 2014-07-22 at 14:02 +0000, Stanescu Victor wrote:
>>>> Hello,
>>>>
>>>> This device works perfectly with usbserial generic, loaded with forced
>>>> vendor/product parameters. Can you please add it to the proper driver?
>>>>
>>>> T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  7 Spd=480 MxCh= 0
>>>> D:  Ver= 2.00 Cls=ff(vend.) Sub=02 Prot=01 MxPS=64 #Cfgs=  2
>>>> P:  Vendor=03f0 ProdID=521d Rev=00.01
>>>> S:  Manufacturer=Hewlett-Packard
>>>> S:  Product=HP hs3110 HSPA+ Mobile Broadband Device
>>> This device appears to be a Huawei "jungo"-type rebrand, given the
>>> drivers:
>>>
>>> %HP3110MDMDeviceDesc% = DevInstall, USBCDCACM\VID_03F0&PID_521D&MI_00
>>> %HP3110PCUIDeviceDesc% = DevInstall, USBCDCACM\VID_03F0&PID_521D&MI_01
>>> %HP3110DIAGDeviceDesc% = DevInstall, USBCDCACM\VID_03F0&PID_521D&MI_02
>>> <interface 3 is standard USB_CLASS_CSCID>
>>> %HP3110ECMDeviceDesc% = ew_juwwanecm.ndi, USBCDCECM\VID_03F0&PID_521D&MI_04
>>> %HP3110GNSSDeviceDesc% = GPS_DevInstall, USBCDCACM\VID_03F0&PID_521D&MI_05
>>>
>>> 03F0:541D (3114) has the same USB layout and same drivers.
>>>
>>> So interfaces 0, 1, 2, and 5 should be driven by 'option', and interface
>>> 4 by one of the ECM/NCM drivers, but I'm not sure here.
>>>
>>> Bjorn, any idea where this one should go?  The Windows drivers make a
>>> distinction between "ew_jucdcncm.ndi" and "ew_jucdcecm.ndi", and this
>>> device falls in the "ecm" part.  So not sure it's appropriate for
>>> huawei_cdc_ncm?
>>>
>>> Dan
>> The interface attributes ff/02/07 is used by Huawei for QMI single
>> interface (combined ctrl and data) so it should go into the qmi_wwan
>> driver
> I'm sure I've asked this before, but my memory (aka Google) is
> completely useless due to too many similar, but still different,
> discussions...
>
> So I just have to ask again: Are we positively sure that this firmware
> supports QMI? We probably do not want to add any non-QMI device to
> qmi_wwan because that will just make things unnecessarily complicated
> for userspace.
>
> AFAIK, Huawei use ff/01/07 for Qualcomm ECM (i.e. QMI functions).
> ff/02/07 is, as noted above, used for Jungo ECM.  We do not know exactly
> what that means wrt management (or I do not know at least, possibly
> because I've forgotten). But what I do know is that the Jungo NCM
> products do not speak QMI.  They have an embedded AT command management
> channel instead.  Is this the same for Jungo ECM?
>
> The serial functions should be pretty straight forward though.  Only
> question there is whether we should add them as device specific, or make
> them vendor specific (like they are for the Huawei vendor ID)?
>
>
>
> Bjørn
��.n��������+%������w��{.n�����{���)��jg��������ݢj����G�������j:+v���w�m������w�������h�����٥





[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux