> it's a bit unclear to me which entries there should be considered 'generic USB IDs'?
They are marked "Generic Identifier", that's 0403:6001 10C4:EA60 10C4:EA80 > I also don't understand why those rules are debian specific See the diff between ./debian/brltty-udeb.udev.rules and ./Autostart/Udev/device.rules.in Note that in debian we use the udev rules *only* inside the installer. The current strategy in Debian is that in the installer we use udev rules to autodetect braille devices. But in the installed system we don't: when the user installs brltty, the user means that they have a Braille device and want to probe it, whether it uses a generic USB ID or not, i.e. we always start brltty > How does upstream handle the devices? When brltty is started it just always probes all devices. Its udev rules file always starts brltty, be it generic IDs or not. > We should stop installing brltty by default going forward That would align with the way it happens in Debian yes. Ideally the udev rules would be split so that the non-generic pieces get always installed to start brltty, and the generic pieces are installed only when necessary. That's a matter of actually spending time on implementing it. > we aren't going to respin ISOs on old serie for such changes and that wouldn't be a solution for already installed systems... Yes, rather disable the generic udev rules. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
