On Mon, Dec 19, 2022 at 10:20:48PM +0000, dima.pasechnik@xxxxxxxxxxx wrote: > On Mon, Dec 19, 2022 at 07:25:03PM +0100, Greg KH wrote: > [...] > > > > That is only if you want to manually bind the generic driver to this > > device. The kernel takes this and says "are you sure you want to do > > this, if so, email this address and talk to these developers" :) > > One does need a dedicated /dev/ttyUSB. It is similar, but not > identical, to /dev/ttyACM. Cf. e.g. > https://rfc1149.net/blog/2013/03/05/what-is-the-difference-between-devttyusbx-and-devttyacmx/ > > And the board makes an effort to establish > a dedicated /dev/ttyUSB. Indeed, after I plugged the board in 21:35 > and did "ls -l /dev/tty*" I saw > > crw--w---- 1 root tty 4, 0 Dec 19 21:28 /dev/tty0 > crw------- 1 dima tty 4, 1 Dec 19 21:35 /dev/tty1 > crw--w---- 1 root tty 4, 10 Dec 19 21:28 /dev/tty10 > crw--w---- 1 root tty 4, 11 Dec 19 21:28 /dev/tty11 > ... > > - it's the Linux host that doesn't recognise this fact. > (it's not even seen in dmesg that something happened on /dev/tty1 - > probably a premature termination of something in the kernel) > > Needless to say, there is also /dev/ttyACM0 popping up - so this part > of the communication is OK. > > I think it's prudent that the kernel understands that it's a > a proper ttyUSB device, apparing as /dev/ttyUSB, and advertises it as > such. Without it, it's hard to detect it, and indeed, the only way I see > this, without an active usbserial driver, is by the time shown next to > /dev/tty* It might help if you post the output of "lsusb -v" for this device. Alan Stern
