netdev - Re: cellular modem driver APIs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <822742983070376410fa550f1d2cc5683a617913.camel@sipsolutions.net>
Date:   Mon, 08 Apr 2019 21:51:00 +0200
From:   Johannes Berg <johannes@...solutions.net>
To:     Daniele Palmas <dnlplm@...il.com>
Cc:     Bjørn Mork <bjorn@...k.no>,
        netdev@...r.kernel.org, Dan Williams <dcbw@...hat.com>,
        Subash Abhinov Kasiviswanathan <subashab@...eaurora.org>,
        Sean Tranchetti <stranche@...eaurora.org>,
        Aleksander Morgado <aleksander@...ksander.es>
Subject: Re: cellular modem driver APIs

On Sat, 2019-04-06 at 19:20 +0200, Daniele Palmas wrote:
> 
> the qmi_wwan sysfs qmap feature, being very easy to use, is serving
> well for me and customers of the company I work for (mainly directly
> with libqmi, not ModemManager), 

Yeah, I don't doubt this. In fact, we could arguably provide the same
through some kind of common stack.

I sort of have to believe though that it's even more limiting that we
*don't* have any common interfaces, since that means you'll have to
rewrite your software even if you just want to switch to a different
Qualcomm modem (e.g. PCIe instead of USB).

> but I understand the need to have a
> common framework and will gladly test and provide feedback for any new
> development related to this.

Thanks :-)

johannes