summaryrefslogtreecommitdiff
path: root/src/77-mm-usb-device-blacklist.rules
AgeCommit message (Collapse)AuthorFilesLines
2021-06-16filter: remove support for TTY blacklist, TTY greylist and TTY default allowedAleksander Morgado1-213/+0
These lists were used in the corresponding TTY_BLACKLIST and TTY_MANUAL_SCAN_ONLY filter rules, in the LEGACY and PARANOID filter types, which are no longer supported. The DEFAULT_ALLOWED filter rule made sense only in the LEGACY filter type, and therefore it is also now removed, leaving the DEFAULT_FORBIDDEN fallback rule exclusively. In other words, there is now no way to ask ModemManager to implicitly allow TTY ports; the only way to do that is by explicit making the TTY ports fall in one filter rule that would allow them.
2020-06-22blacklist: add chinese clone of Arduino nanoAleksander Morgado1-0/+3
Fixes https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/228
2020-06-04ublox: fully ignore GPS devices with plugin-installed rulesAleksander Morgado1-5/+0
Instead of setting up the ID_MM_TTY_BLACKLIST tag used in 'legacy' filter mode, tag all known u-blox GPS devices with the broader ID_MM_DEVICE_IGNORE tag that applies under all filter modes. Also, make this rules be installed by the plugin itself, because at the end, it is the u-blox plugin the one attempting to probe all devices with vid 0x1546.
2020-05-27blacklist: add USB CEC adaptersAleksander Morgado1-0/+4
These are not being probed when using the STRICT filter, so this blacklist update is relevant only for DEFAULT filter type. Fixes https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/212
2019-08-29udev: repurpose ID_MM_DEVICE_IGNORE and new MM_FILTER_RULE_EXPLICIT_BLACKLISTAleksander Morgado1-81/+81
Until now the ID_MM_DEVICE_IGNORE udev tag was being used in the internal blacklist of devices shipped by ModemManager when running in either DEFAULT or PARANOID filter modes. The name of the tag is extremely misleading because it doesn't really make the full device be ignored, the tag only applied to TTY ports. This commit repurposes the tag so that it applies to ANY kind of port (e.g. TTY, NET, cdc-wdm...) and also to any kind of filter type (i.e. also applicable in STRICT mode). The internal blacklist shipped by ModemManager, which should NOT be used in STRICT mode, uses a new tag name, ID_MM_TTY_BLACKLIST. The new ID_MM_DEVICE_IGNORE tag is therefore much more usable and its name is really meaningful. If there are users or third-party projects adding their own udev rules with the ID_MM_DEVICE_IGNORE tag name, they should have no problem as the new rule is more restrictive than the old one.
2018-07-19blacklist: include all devices from Prusa ResearchAleksander Morgado1-0/+3
2018-07-10blacklist: remove OpenMoko Hubs from the blacklistAlexander Couzens1-2/+2
The problem of full vendor blacklist are hubs. Because ATTRS{} matches all devices in the tree, a modem connected to a OpenMoko hub will be blacklisted as well.
2018-06-02udev: add tags also on bind actionAleksander Morgado1-1/+1
When a new USB device is hotplugged, e.g. a USB<->RS232 converter that exposes a single ttyUSB0, these udev events happen: add /devices/pci0000:00/0000:00:14.0/usb2/2-1 (usb/usb-device) add /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0 (usb/usb-interface) add /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/ttyUSB0 (usb-serial) add /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/ttyUSB0/tty/ttyUSB0 (tty) bind /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/ttyUSB0 (usb-serial) bind /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0 (usb/usb-interface) bind /devices/pci0000:00/0000:00:14.0/usb2/2-1 (usb/usb-device) Our udev rules in MM only added tags in the 'add' events, and it looks like the only ones 'persistent' after this sequence are those of the last event happening on the specific path. This meant that all TTY subsystem rules (e.g. ID_MM_CANDIDATE) would be stored for later check (e.g. if ModemManager is started after these rules have been applied), which was ok. "udevadm info -p ..." would show these tags correctly always. But this also meant that the 'bind' udev event happening for the USB device didn't get any of our device-specific tags, and so we would be missing them (e.g. ID_MM_DEVICE_MANUAL_SCAN_ONLY) if MM is started after the last event has happened. "udevadm info -p ..." would not show these tags. Modify all our rules to also run at the 'bind' events. See, for context: https://github.com/systemd/systemd/issues/8221
2017-12-18blacklist: Pycom uses Microchip's vid, so blacklist also by pidAleksander Morgado1-7/+7
The Microchip VID is added to the USB serial adapters greylist instead, as it is very generic. https://bugs.freedesktop.org/show_bug.cgi?id=104320
2017-12-18blacklist: include all Pycom devicesAleksander Morgado1-0/+5
https://bugs.freedesktop.org/show_bug.cgi?id=104320
2017-09-14blacklist: ignore Intel coredump downloader deviceDaniele Palmas1-0/+3
2017-09-10Blacklist Garmin ANT+ sticksArto Jantunen1-0/+3
2017-08-29blacklist: ignore Silicon Labs USB Zigbee donglesMario Limonciello1-0/+3
2017-05-18blacklist: ignore default Linux USB Serial GadgetAleksander Morgado1-0/+3
Blacklist the default VID:PID for the Linux USB Serial Gadget in ACM mode: {LINUX}/drivers/usb/gadget/legacy/serial.c #define GS_VENDOR_ID 0x0525 /* NetChip */ #define GS_CDC_PRODUCT_ID 0xa4a7 /* ... as CDC-ACM */ This should never be reused for real products by hardware manufacturers, but anyway... Patch actually ported from downstream Ubuntu: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1105352
2017-05-10blacklist: add keyboard.io devicesAleksander Morgado1-0/+4
See https://bugs.freedesktop.org/show_bug.cgi?id=85007#c5 Reported-by: Jesse Vincent <jesse@keyboard.io>
2017-04-24blacklist: add Analog Devices EVAL-ADXL362Z-DBMaksim Salau1-0/+3
Signed-off-by: Maksim Salau <maksim.salau@gmail.com>
2017-02-05blacklist: add promotion boards from RenesasMaksim Salau1-0/+4
Signed-off-by: Maksim Salau <maksim.salau@gmail.com>
2017-01-31blacklist: add Analog PlutoSDRAleksander Morgado1-0/+3
Reported-by: Robin Getz <Robin.Getz@analog.com>
2016-12-12telit: blacklist LE866 flashing deviceCarlo Lobrano1-0/+3
Moved blacklist code to 77-mm-usb-device-blacklist.rules as per code review
2016-10-24blacklist: ignore Sigma Sport docking stationsSławomir Bocheński1-0/+5
These CDC ACM class devices are docking stations for Sigma Sport bike computers. As they are sensitive to single byte commands, ModemManager probing mechanism actually caused training data on attached bike computer to be zeroed. https://bugs.freedesktop.org/show_bug.cgi?id=96430
2016-09-22blacklist: add another Infineon flashloader deviceDaniele Palmas1-0/+1
This patch adds another Infineon flashloader device 0x8087/0x0801 to the blacklist Reference to the kernel commit: github.com/torvalds/linux/commit/f190fd92458da3e869b4e2c6289e2c617490ae53
2016-08-29blacklist: add blacklist udev rule for U-blox7 GPS/GLOSNASS USB dongle.Tabor Kelly1-0/+1
Signed-off-by: Tabor Kelly <t.kelly@trailtech.net>
2016-08-06udev: remove ENV{DEVTYPE}!="usb_device" rulesAleksander Morgado1-1/+0
They're actually a subcase of SUBSYSTEM!="usb", which we apply just before.
2016-07-27blacklist: include some more ArduinosLubomir Rintel1-0/+1
All "2a03 dog hunter AG" devices seem to be Arduinos. https://bugzilla.redhat.com/show_bug.cgi?id=1261040
2016-02-20proxmark3 is not a modem, blacklist it.Michael Farrell1-0/+3
ModemManager locks the proxmark3 when it is connected. As it is not a modem, ModemManager shouldn't be talking to it. At present, the recommended action in the proxmark3 documentation is to purge ModemManager to fix this issue. Note that this vendor uses an unregistered USB device ID, so it is instead matched by the manufacturer string. References: - http://store.ryscc.com/blogs/news/45802433 - http://www.proxmark.org/forum/viewtopic.php?id=1759
2015-08-25blacklist: include MediaTek preloaderAleksander Morgado1-0/+3
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1473246
2015-07-02blacklist: ignore POSNET POLSKA S.A. devicesDan Williams1-0/+4
2015-06-19blacklist: ignore Palm M5xx devicesAleksander Morgado1-0/+9
https://bugs.freedesktop.org/show_bug.cgi?id=91032
2015-04-10blacklist: ignore all devices from Access Interface SolutionsAleksander Morgado1-0/+4
2015-03-06Adding IMC flashing device in blacklistDaniele Palmas1-0/+3
2015-01-26blacklist: ignore PalmOS devices driven by 'visor'Dan Williams1-0/+7
MM probing appears to make 'visor' module die; and anyway most of the devices driven by 'visor' are not phones, and of the 3 that are phones they are so old (2002 - 2005 era) that nobody is likely using them for dialup anymore. http://www.spinics.net/lists/linux-usb/msg120483.html
2014-10-28blacklist: ignore GW Instek AFG-2225 arbitrary waveform generatorDan Williams1-0/+3
2014-06-02blacklist: ignore Infineon flashloader deviceBjørn Mork1-0/+3
A device like this shows up briefly while the Sierra EM7345 is booting: P: Vendor=8087 ProdID=0716 Rev= 0.00 C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=500mA I:* If#= 0 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=(none) E: Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms We do have a driver identifying this as an "Infineon Flashloader" device. It is not a modem in any case, and should be ignored. Signed-off-by: Bjørn Mork <bjorn@mork.no>
2014-04-02blacklist: All devices from Pololu Corporation except some possible future ↵David (Pololu)1-0/+6
products. We make many USB virtual COM port devices, none of which are modems. ModemManager's automatic attempts to access those devices can cause problems. That might change in the future, so we have left two potential future product IDs off of the blacklist.
2014-03-24blacklist: ignore empiriKit science lab controller deviceAleksander Morgado1-0/+3
2014-02-04blacklist: ignore all devices from VID 0x26a, no modems from 3D RoboticsJulian Oes1-0/+3
2014-01-26udev: apply udev rules upon 'move' events as wellAleksander Morgado1-1/+1
Otherwise, we may end up losing the tags we expect if the device gets a 'move' event just after the initial 'add'.
2013-10-30blacklist: include the whole Openmoko VIDAleksander Morgado1-0/+3
2013-10-25blacklist/greylist: add more GPS devices (rh #1023234)Dan Williams1-0/+16
Attempt to blacklist entire drivers that we know aren't modems, and add a sprinkling of specific devices too.
2013-09-24blacklist: add Bluegiga BLE112BAleksander Morgado1-0/+3
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1229748
2013-09-24blacklist: add some missing commasAleksander Morgado1-2/+2
2013-09-23blacklist: Add Adafruit FloraArun Raghavan1-0/+4
The official PID is 8004, but I've seen the device sometimes turn up with a 0004, so adding both to be safe. https://bugzilla.gnome.org/show_bug.cgi?id=708644
2013-04-08blacklist: move Arduino USB/Serial adapter to greylistDan Williams1-6/+0
It's a generic adapter, should be in the manual-probe-only greylist instead of the blacklist.
2013-04-08blacklist: ignore a few more Arduinos (rh #861620)Dan Williams1-0/+6
2013-04-04serial,blacklist: fix file mode (0755 -> 0644)Ben Chan1-0/+0
2013-04-04altair-lte: initial altair lte pluginori inbar1-0/+3
2013-03-20blacklist: ignore Arduino devicesAleksander Morgado1-0/+5
https://bugs.launchpad.net/bugs/910736 https://bugs.launchpad.net/bugs/1153632
2013-03-13blacklist: ignore West Mountain radio devicesAleksander Morgado1-0/+5
https://bugs.launchpad.net/bugs/1154654
2013-03-05core: don't automatically probe ports of USB<->serial adaptersAleksander Morgado1-6/+0
We should not automatically probe ports marked as coming from USB to serial adapters, as we're not sure that a modem is behind the adapter. Still, let the user request a manual scan and have these devices probed in that case. https://bugzilla.gnome.org/show_bug.cgi?id=647556 https://bugzilla.gnome.org/show_bug.cgi?id=691076
2013-01-09blacklist: ignore all devices from VID 0x0617Aleksander Morgado1-0/+3
No modems from the Swiss Federal Institute of Technology. https://bugzilla.gnome.org/show_bug.cgi?id=691384
generated by cgit v1.2.3 (git 2.39.1) at 2024-04-28 14:02:40 +0000