differences between with rmnet and qmi_wwan
Martin Maurer
martin.maurer at mmeacs.de
Mon Jun 17 18:02:09 UTC 2024
Hi,
Am 19.05.2024 um 16:07 schrieb Daniele Palmas:
> Hi Alexander,
>
> Il giorno dom 19 mag 2024 alle ore 14:00 Alexander 'lynxis' Couzens
> <lynxis at fe80.eu> ha scritto:
>> Hi,
>>
>>
>> I'm looking into the different modes of qmi user traffic.
>> Currently I'm only using usb based modems, but would like to support
>> pcie based modems in near future.
>>
>> qmi_wwan can be configured via /sysfs [1]. (add_mux del_mux pass_through raw_ip)
>> rmnet devices can be connected to the wwan0 interface with `ip link` or netlink.
>>
>> What are the differences between rmnet and qmi_wwan regarding the user traffic?
>> Is rmnet just more flexible and generic way to support qmap?
> rmnet is now the maintained way for using qmap, new qmap-related
> features are added to rmnet and no more to qmi_wwan.
>
How do I recognize, that I use rmnet? How can I select that I use rmnet
instead of qmi_wwan?
When I call lsusb -t I see
|__ Port 001: Dev 004, If 4, Class=[unknown], Driver=qmi_wwan, 480M
I think it was automatically using qmi_wwan driver. Do I need to switch
off a kernel switch for qmi_wwan and enable one for rmnet to get to the
new one?
You mentioned:
> Yes, there are (e.g. uplink aggregation, flow control commands...).
Are these all "internal" feature, which work by itself? Or are there programs like qmicli to control these?
Or is qmicli detecting automatically that rmnet is used and offers me more commands?
Has qmimux something to do with rmnet? Or is it even the same?
Best regards,
Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20240617/925ea1b2/attachment.htm>
More information about the libqmi-devel
mailing list