On 2016-02-20 03:34, Dan Williams wrote:
On Fri, 2016-02-19 at 18:21 +0100, Bjørn Mork wrote:
Dan Williams <dcbw@xxxxxxxxxx> writes:
On Fri, 2016-02-19 at 21:20 +0700, Lars Melin wrote:
cfg #1
MI_00 HP Mobile Connect - PC UI Interface
MI_01 HP Mobile Connect - Application Interface
MI_02 HP Mobile Connect - Modem
MI_03 HP Mobile Connect - Network Card (jungo ncm)
MI_04 HP Mobile Connect - GPS Interface
cfg#2
MI_00 HP Mobile Connect - Network Card (cdc_ether)
MI_02 HP Mobile Connect - Modem
MI_03 HP Mobile Connect - Application Interface
MI_04 HP Mobile Connect - PC UI Interface
MI_05 HP Mobile Connect - GPS Interface
cfg#3
MI_00 HP Mobile Connect - Network Card (cdc_mbim)
MI_02 HP Mobile Connect - GPS Interface
Bjorn, with these devices that technically "support" a bunch of
different modes, what should our advice be on mode select?
Personally
I'd love to switch modems that support MBIM into MBIM by default...
Yup, me too. That is the configuration with a class driver and
standardized management, allowing it to work without any device or
vendor specific support. It is also the configuration used by
current
Windows versions and therefore most likely tested.
I don't think such a policy is suitable for the kernel, though. In
fact, I don't think the current kernel policy is appropriate for the
kernel either :) But we'll have to leave that as it is.
Do you think it is possible to create a catch-all udev rule
preferring
MBIM? I guess we'll need some helper for that, since it means making
a
choice based on the attributes of an inactive configuration.
usb_modeswitch would be the most logical helper.
Dan
usb_modeswitch does already handle one module under Huawei's own id so
it should also be able to switch the HP branded ones.
There are more HP branded modules which we may see in the future and
I'll make sure that they will be added to usb_modeswitch as soon as I
know their interface layout.
HP's own drivers tells what kind of interfaces are available but not in
which config they are present or in which order within a config.
There is at least some useful info in them about baseline drivers:
<item module="MU736" VID="03F0" PID="521D" Baseline="JUNGO" Remark="HP"/>
<item module="MU736" VID="03F0" PID="541D" Baseline="JUNGO" Remark="HP"/>
<item module="ME906" VID="03F0" PID="561D" Baseline="QUALCOMM" Remark="HP"/>
<item module="ME906" VID="03F0" PID="581D" Baseline="QUALCOMM" Remark="HP"/>
<item module="ME906" VID="03F0" PID="591D" Baseline="QUALCOMM" Remark="HP"/>
<item module="ME906J" VID="03F0" PID="631D" Baseline="QUALCOMM"
Remark="HP"/>
<item module="ME906J" VID="03F0" PID="641D" Baseline="QUALCOMM"
Remark="HP"/>
<item module="ME906J" VID="03F0" PID="681D" Baseline="QUALCOMM"
Remark="HP"/>
<item module="ME936" VID="03F0" PID="931D" Baseline="JUNGO" Remark="HP"/>
<item module="ME206" VID="03F0" PID="9A1D" Baseline="JUNGO" Remark="HP"/>
which makes me think that lt4114 should not be in qcserial but in option
instead.
--
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
