Bjørn Mork <bj...@mork.no> writes: > Aleksander Morgado <aleksan...@aleksander.es> writes: > >> Just add a ID_MM_DEVICE_IGNORE rule as you would have done with udev, >> and restart the daemon. > > I should obviously have tried that first. Worked perfectly. After a > reboot though. I believe the caching made it a noop on restart?
One problem with this, which is an argument for replacing the udev rules with simpler config files, is that there is no way to add local persistent (across system upgrades) udev rules in OpenWrt. Unless I missed that as well... OK, I could of course add a file in /lib/udev/rules.d and add the name of that file in /etc/sysupgrade.conf, but that's a little more than should be needed for a local blacklist override IMHO. I believe a nice addition to the OpenWrt packaging would be a modemmanager UCI file, with any configurable stuff like log level, local blacklists etc. Making such settings survive a sysupgrade is essential. >> Also, could you please retry running ModemManager with >> "--filter-policy=STRICT" (e.g. just edit the /etc/init.d/modemmanager >> file to add that)? I would suggest we switch to that filter policy for >> the defaults everywhere, including openwrt. When using that filter >> policy, a USB device that only exposes ttyUSB ports would not be >> probed automatically. > > > Will do that later. Don't have time for more testing right now. Works perfectly, as expected. I believe it's a good default, at least for OpenWrt. Right now, there is no install-base expecting current behaviour. And I don't think OpenWrt users want to edit any config files outside /etc/config. Defaulting to "--filter-policy=STRICT" will reduce the need to do that. Bjørn _______________________________________________ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
