diff options
| author | Bjørn Mork <bjorn@mork.no> | 2012-09-19 21:18:05 +0000 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2012-09-21 13:21:22 -0400 |
| commit | 42d94dcb68b939c72fded1b3974cd240723afa0c (patch) | |
| tree | 1ad2e2c42d8c316bc09b745809804190faad5de7 /Documentation/filesystems/nfs/nfsroot.txt | |
| parent | fc18162520b642a46ea556300bfdee80810fc538 (diff) | |
| download | blackbird-op-linux-42d94dcb68b939c72fded1b3974cd240723afa0c.tar.gz blackbird-op-linux-42d94dcb68b939c72fded1b3974cd240723afa0c.zip | |
net: qmi_wwan: adding Huawei E367, ZTE MF683 and Pantech P4200
One of the modes of Huawei E367 has this QMI/wwan interface:
I:* If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=07 Driver=(none)
E: Ad=83(I) Atr=03(Int.) MxPS= 64 Ivl=2ms
E: Ad=84(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=4ms
Huawei use subclass and protocol to identify vendor specific
functions, so adding a new vendor rule for this combination.
The Pantech devices UML290 (106c:3718) and P4200 (106c:3721) use
the same subclass to identify the QMI/wwan function. Replace the
existing device specific UML290 entries with generic vendor matching,
adding support for the Pantech P4200.
The ZTE MF683 has 6 vendor specific interfaces, all using
ff/ff/ff for cls/sub/prot. Adding a match on interface #5 which
is a QMI/wwan interface.
Cc: Fangxiaozhi (Franko) <fangxiaozhi@huawei.com>
Cc: Thomas Schäfer <tschaefer@t-online.de>
Cc: Dan Williams <dcbw@redhat.com>
Cc: Shawn J. Goff <shawn7400@gmail.com>
Signed-off-by: Bjørn Mork <bjorn@mork.no>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/filesystems/nfs/nfsroot.txt')
0 files changed, 0 insertions, 0 deletions
