This issue should be hopefully solved in ModemManager 1.10.6 after adding
several new heuristics to the "strict" filter mode.
Also, the logic behind ID_MM_DEVICE_IGNORE was updated and this udev tag is now
applicable in all filter modes (including "strict") and for all device types
(not only
And this is the suggested change to avoid the issue with the Arduinos wrongly
claiming AT protocol support:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/143
--
Aleksander
https://aleksander.es
The ID_MM_DEVICE_IGNORE udev tag is being ignored in strict filter mode, I'm
trying to change that in this MR for the next MM release:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/merge_requests/138
Iain, could you let me know the full lsusb -v output of that specific DMR
Control: affects -1 + dmrconfig
Hi,
I've hit this problem with a DMR radio that uses a USB programming
cable. It presents as a ttyACM device, which is snapped up by
ModemManager. These are not the most robust interfaces and I could
easily see radios being bricked by accepting an "upload" of
4 matches
Mail list logo