<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <div class="moz-cite-prefix">Am 11.11.2023 um 20:25 schrieb Bjørn Mork: </div> <blockquote type="cite" cite="mid:87wmuom6rt.fsf@miraculix.mork.no"> <pre class="moz-quote-pre" wrap="">Martin Maurer <a class="moz-txt-link-rfc2396E" href="mailto:martin.maurer@mmeacs.de"><martin.maurer@mmeacs.de></a> writes: </pre> <blockquote type="cite"> <pre class="moz-quote-pre" wrap="">Hello, on <a class="moz-txt-link-freetext" href="https://source.sierrawireless.com/resources/airprime/software/linux-qmi-sdk-software-latest/#sthash.v0regNmz.dpbs">https://source.sierrawireless.com/resources/airprime/software/linux-qmi-sdk-software-latest/#sthash.v0regNmz.dpbs</a> (perhaps login needed) it says: "Linux QMI SDK Software (SLQS bin + Lite bin) Aug 14, 2020 - Author: Sierra Wireless - Version 04.00.27 *** NOTE: This product is now EOL. Sierra Wireless recommends customers move to MBPL on supported modules. ***" So no more supported QMI for new Sierra Wireless radio modules (like EM92) anymore? Or only the SDK obsolete? </pre> </blockquote> <pre class="moz-quote-pre" wrap=""> If you look at <a class="moz-txt-link-freetext" href="https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/">https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/</a> you'll find that their currently supported USB drivers includes qmi_wwan. So it looks like QMI still is supported, using qmi_wwan and libqmi. The Qualcomm Gobi drivers and associated SDK are unsupported. </pre> <blockquote type="cite"> <pre class="moz-quote-pre" wrap="">Am I forced to use something different? Or something (which I only know the name) like MHI? Can libqmi and qmicli still be used with MHI? I found this page: <a class="moz-txt-link-freetext" href="https://docs.kernel.org/mhi/mhi.html">https://docs.kernel.org/mhi/mhi.html</a> Is MHI something completely different? Or similar to QMI and MBIM? </pre> </blockquote> <pre class="moz-quote-pre" wrap=""> In my simple mind, MHI is the Qualcomm PCIe transport framework. Orobably imprecise or even incorrect. </pre> <blockquote type="cite"> <pre class="moz-quote-pre" wrap="">I have not heard of MHI from vendors other than Sierra Wireless? Or skip Sierra Wireless? MBIM is supported by qmicli. Back to MBIM? My aim would be to support multiple modules with same protocol, but this task seems to be not so easy... </pre> </blockquote> <pre class="moz-quote-pre" wrap=""> Predicting the future is difficult. I tried to write a simple driver for a Huawei modem back in 2011... Never imagined that Sierra Wireless would provide it with their 5G modules in 2023. MBIM using MHI/PCIe as transport looks like the most future proof solution at the moment, given that you can use QMI over MBIM. But don't worry if you're stuck with a USB host interface. Doesn't look like it will disappear as fast as we (or maybe just I?) thought a couple of years ago. Bjørn</pre> </blockquote> Many thanks for your answer! <pre class="moz-quote-pre" wrap="">> <a class="moz-txt-link-freetext" href="https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/">https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/</a></pre> This was a good hint. After taking the USB sources, compiling and installing them (reboot important! -> follow readme!), /dev/cdc-wdm0 occured. I was able to execute commands via qmicli. At first I was not able to build up a connection, got always "CallFailed". > Couldn't start network: QMI protocol error (14): 'CallFailed' Used AT command showed "Low Power Mode": AT!PCINFO? State: Low Power Mode I had to disable handling of HW signal W_DISABLE. Furthermore module needed a simple AT+CFUN=1. Then I was able to build up an IPv4 connection, as well as an IPv6 connection and transfer data over it (at least some pings). Next thing: When trying to activate qmimux, kernel crashes. This needs detailed analysis. Perhaps sources from MBPL do not fit to the kernel used by me (tested on Raspberry Pi 4 with linux kernel 6.1.0-rpi4-rpi-v8). And I assume that patched qmi_wwan.c (from MBPL) could perhaps conflict with radio modules by other manufacturers. Testing/comparing/merging needed. Best regards, Martin </body> </html>