On 09.06.2016 23:42, Mark Kettenis wrote:
Date: Thu, 9 Jun 2016 22:59:28 +0200 (CEST)
From: Mark Kettenis <mark.kette...@xs4all.nl>
Date: Wed, 8 Jun 2016 15:08:52 +0200
From: Gerhard Roth <gerhard_r...@genua.de>
I would be glad to hear from some people trying this with a real MBIM
device.
Sierra Wireless EM7345 4G LTE here. This devices currently attached
as umodem(4). But I did add its vendor id and device id to umb_devs,
which makes it partially attach:
umb0 at uhub0 port 4 "Sierra Wireless Inc. Sierra Wireless EM7345 4G LTE" rev
2.00/17.29 addr 2
umb0: switching to config #1
umb0: ignoring invalid segment size 1500
umb0: ctrl_len=512, maxpktlen=8192, cap=0x4
umb0: no control interface found
(this is with UMB_DEBUG enabled)
It seems this device needs some additional poking to select alternate
interface settings.
With the appropriate alternate settings for the communication
interface and data interface (1 and 2) hardcoded in the driver, this
works!
Great!
Although another example of a device violating the MBIM spec which
clearly states that alternate settings 0 and 1 have to be used.
umb0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1500
index 5 priority 0
roaming disabled registration home network
state up cell-class LTE rssi -79dBm speed 47.7Mps up 95.4Mps down
SIM initialized PIN valid (3 attempts left)
subscriber-id XXXXXXXX ICC-id YYYYYYYYYY provider NL KPN
device XMM7160_V1.2_MB IMEI ZZZZZZZZZ firmware FIH7160_V1.2_WW
APN umts.xs4all.nl
groups: egress
status: active
inet 83.161.163.248 --> 83.161.163.1 netmask 0xffffff00
