Comment # 2 on bug 1063172 from
Hello Michael,
sure. This is the relevant output of lsusb:

Bus 001 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102/CP2109
UART Bridge Controller [CP210x family]

This, instead is coming from kernel logs (whre you can see brltty hijacking
ttyUSB0):

[19645.797064] usb 1-8: new full-speed USB device number 5 using xhci_hcd
[19645.938788] usb 1-8: New USB device found, idVendor=10c4, idProduct=ea60
[19645.938794] usb 1-8: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[19645.938797] usb 1-8: Product: CP2102 USB to UART Bridge Controller
[19645.938800] usb 1-8: Manufacturer: Silicon Labs
[19645.938802] usb 1-8: SerialNumber: 0001
[19645.958688] usbcore: registered new interface driver usbserial
[19645.958706] usbcore: registered new interface driver usbserial_generic
[19645.958723] usbserial: USB Serial support registered for generic
[19645.959709] usbcore: registered new interface driver cp210x
[19645.959730] usbserial: USB Serial support registered for cp210x
[19645.959758] cp210x 1-8:1.0: cp210x converter detected
[19645.961414] usb 1-8: cp210x converter now attached to ttyUSB0
[19646.174548] usb 1-8: usbfs: interface 0 claimed by cp210x while 'brltty'
sets config #1
[19646.174995] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[19646.175015] cp210x 1-8:1.0: device disconnected
[19650.241001] input: BRLTTY 5.5 Linux Screen Driver Keyboard as
/devices/virtual/input/input19

Best regards,
Giuseppe.


You are receiving this mail because: