RFC: New device filter policies

Carlo Lobrano c.lobrano at gmail.com
Tue Nov 21 14:39:10 UTC 2017


Hi Aleksander,

On Nov 20 2017, at 2:33 pm, Carlo Lobrano <c.lobrano at gmail.com> wrote:
> Hi Aleksander,
>
> > I plan to get this merged to git master sometime this week; tests and
> > comments welcome!
>
> I plan to have some testing done in the next couple of days
>
> Carlo

I just tested the following modems:

HE910, LE910, LE910 V2 (with AT and MBIM protocols), LM940 (which is QMI).

Modems are all detected the same way:
**mmcli** output is the same for all of the modems using both **master** and *device-filter-policies* branches and the latter both in default and strict mode. This also means that the primary protocol used is also the same for each modem.

Probed devices (I looked for log message "probe required"):
master and device-filter-policies in **default mode** probe the same ports, while in **strict mode** modemmanager skips only the ports that in master/device-filter-policies default mode are not used.

Below an example from LM940 logs

+ grep 'probe required' lm940-master.log
ModemManager ... (Telit) [cdc-wdm1] probe required: 'qmi'
ModemManager ... (Telit) [ttyUSB5] probe required: 'at'
ModemManager ... (Telit) [ttyUSB4] probe required: 'at'
ModemManager ... (Telit) [ttyUSB3] probe required: 'at'
ModemManager ... (Telit) [ttyUSB2] probe required: 'at'
ModemManager ... (Telit) [ttyUSB1] probe required: 'at'
ModemManager ... (Iridium) [ttyS4] probe required: 'at, at-vendor, at-product'
ModemManager ... (u-blox) [ttyS4] probe required: 'at, at-vendor'
ModemManager ... (Telit) [ttyS4] probe required: 'at, at-vendor'
ModemManager ... (Cinterion) [ttyS4] probe required: 'at, at-vendor'
ModemManager ... (Nokia) [ttyS4] probe required: 'at, at-vendor, at-icera'
ModemManager ... (Via CBP7) [ttyS4] probe required: 'at, at-vendor, at-product'
ModemManager ... (Generic) [ttyS4] probe required: 'at, qcdm'

+ grep 'probe required' lm940-device-filter-policies-default.log
ModemManager ... (Telit) [cdc-wdm1] probe required: 'qmi'
ModemManager ... (Telit) [ttyUSB5] probe required: 'at'
ModemManager ... (Telit) [ttyUSB4] probe required: 'at'
ModemManager ... (Telit) [ttyUSB3] probe required: 'at'
ModemManager ... (Telit) [ttyUSB2] probe required: 'at'
ModemManager ... (Telit) [ttyUSB1] probe required: 'at'
ModemManager ... (Iridium) [ttyS4] probe required: 'at, at-vendor, at-product'
ModemManager ... (u-blox) [ttyS4] probe required: 'at, at-vendor'
ModemManager ... (Telit) [ttyS4] probe required: 'at, at-vendor'
ModemManager ... (Cinterion) [ttyS4] probe required: 'at, at-vendor'
ModemManager ... (Nokia) [ttyS4] probe required: 'at, at-vendor, at-icera'
ModemManager ... (Via CBP7) [ttyS4] probe required: 'at, at-vendor, at-product'
ModemManager ... (Generic) [ttyS4] probe required: 'at, qcdm'

+ grep 'probe required' lm940-device-filter-policies-strict.log
ModemManager ... (Telit) [cdc-wdm1] probe required: 'qmi'
ModemManager ... (Telit) [ttyUSB5] probe required: 'at'
ModemManager ... (Telit) [ttyUSB4] probe required: 'at'
ModemManager ... (Telit) [ttyUSB3] probe required: 'at'
ModemManager ... (Telit) [ttyUSB2] probe required: 'at'
ModemManager ... (Telit) [ttyUSB1] probe required: 'at

So, regarding modem recognition, everything looks fine to me.

Carlo

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20171121/36ee1300/attachment.html>


More information about the ModemManager-devel mailing list