Running ModemManager without udev (v2)

Aleksander Morgado aleksander at aleksander.es
Thu Sep 29 13:38:58 UTC 2016


Hey,

This is the second attempt to consolidate a set of patches to, among other
things, allow disabling udev as a requirement for ModemManager.

The 'generic' kernel device backend now reads and loads all udev rule files
once on boot, which allows us to prepare some unit tests that will do the
same for each available rules before doing a release. Note that the actual
loading process of the rules is the one validating them, and we only validate
them for correctness (i.e. we don't validate that a given rule will be applied
to a given device, as that would require the device to be present).

Allowing to disable udev is not the only new feature added; these patches also
provide support to name a given modem device with a unique id (e.g. via a
udev property set in the parent udev_device) that can later be used to identify
the modem in "mmcli -m" calls.

Comments welcome!

[PATCH 1/5] core: allow identifying devices by a user-provided 'uid'
[PATCH 2/5] core: new kernel device object instead of an explicit...
[PATCH 3/5] core: allow disabling auto-scan and notifying ports one...
[PATCH 4/5] core: use the kernel device object in the port object and...
[PATCH 5/5] core: allow building and running without udev


More information about the ModemManager-devel mailing list