firmware update
Bjørn Mork
bjorn at mork.no
Tue Dec 22 01:58:37 PST 2015
dailijin <dailijin126 at 126.com> writes:
> Hi All,
>
>
> yes, you are right. I think the issue should be caused by the
> GobiSerial driver.
>
>
> if I use the the driver GobiSerial from Sierra S2.24N2.33, the issue
> will happen. if use the old GobiSerial driver(NTGR_2.12), seems no
> issue appear, Sorry to send incorrect driver source code, I should
> send the source code from S2.24N2.33.
>
>
> I know the driver GobiSerial which I am using is not from Sierra, and
> the newest Sierra driver package should be S2.25N2.35, I want to test
> it, could you send the source codes to me?
Sure, it's dual GPL/BSD licensed so that should not be a problem. I'll
send it in a private mail. The source is also downloadable from
Sierra's "source" website.
> Another thing is that I am testing MC7430 modem via libqmi 1.10.2,
> always can't successfully get QMI response from the modem, I think
> maybe the libqmi version is old, should I upgrade libqmi version for
> the modem?
Ah, right. I don't know if there are any relevant libqmi changes yet,
but 1.10.2 is very old and MC7430 is very new. That's not a good
combination in general ;)
The MC74xx modems have some new flow control restrictions which I am
still trying to figure out. That's what this is an attempt to solve:
https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/drivers/net/usb/qmi_wwan.c?id=93725149794d3d418cf1eddcae60c7b536c5faa1
The info comes from the newest Sierra GobiNet drivers. And testing on
MC7455 showed that the QMI channel will not respond until DTR is on.
Previously we did not care about DTR at all. But it appears to have a
meaning to earlier firmwares too: A DTR off/on sequence has about the
same effect as sending QMI_CTL SYNC. Which means that we cannot do DTR
on/off in the driver based on /dev/cdc-wdmX open/close, since a QMI
session can be active even if the device is closed.
Then the latest Sierra GobiNet driver (N2.35) added another interesting
part:
MODULE_PARM_DESC( iTEEnable, "Enable/Disable TE Flow Control" );
which controls TLV 0x1a of the driver WDS Set Data Format request. But
I don't know what that does to the firmware. I tested it on an EM7305
and an MC7455, but could not figure out what it is supposed to change.
Both modems accept the TLV without changing the reply. The MC7455
always returns TLV 0x1a = 0x00000000, and the EM7305 doesn't return any
0x1a TLV (but still accepts it as input).
Writing too much again :) You may not need the latest libqmi, but you
definitely need the latest drivers for MC74xx modems.
Bjørn
More information about the libqmi-devel
mailing list