Date: Fri, 2 Nov 2018 07:59:24 -0600 From: Warner Losh <imp@bsdimp.com> To: Hans Petter Selasky <hps@selasky.org> Cc: "Andrey V. Elsukov" <bu7cher@yandex.ru>, mandrews@bit0.com, "freebsd-usb@FreeBSD.org" <freebsd-usb@freebsd.org> Subject: Re: umodem0, Cisco USB serial console, and quirks Message-ID: <CANCZdfqoC8QaDDRP0QoYO0C1WvT_EBmNC8UXAzG-GEbaoK0Xyg@mail.gmail.com> In-Reply-To: <bbdda4ab-567f-2658-b83e-5bf0e1176e9a@selasky.org> References: <alpine.BSF.2.21.1709191021260.34953@beast.int.bit0.com> <d9dbef0b-c22e-c7ea-34a2-f36e9e768745@selasky.org> <alpine.BSF.2.21.1709191205280.1218@beast.int.bit0.com> <0c4022f3-bd21-49b5-cadd-daeb9f1f3081@selasky.org> <alpine.BSF.2.21.1709262210180.33243@beast.int.bit0.com> <33f3a1f8-69d1-9240-6381-8a851beb97d0@yandex.ru> <18d57cbe-1235-aedf-45e6-e36b495ca1eb@bit0.com> <15cff2a5-021f-49e5-b287-37a14a9321b3@selasky.org> <5d0a544d-517c-2fb9-84e8-d87704474cce@yandex.ru> <5cdb37b5-fca1-99db-cacc-cf72f0cee0df@selasky.org> <51ae0fc4-7e93-30d6-caa3-393afbe278b6@yandex.ru> <bbdda4ab-567f-2658-b83e-5bf0e1176e9a@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 2, 2018 at 3:57 AM Hans Petter Selasky <hps@selasky.org> wrote: > On 11/2/18 10:24 AM, Andrey V. Elsukov wrote: > > On 02.11.2018 12:12, Hans Petter Selasky wrote: > >>> # cu -l /dev/cuaU0 > >>> Connected > >>> > >>> <nothing here> > >>> > >> > >> Did you try "-s" option to set another baudrate? > > > > Yes, the result is the same. > > > > # cu -s 115200 -l /dev/cuaU0 > > Connected > > > > If I understand correctly from > > https://www.bit0.com/tmp/usbmon-ciscoasa-verbose.txt > > > > The > > > > Leftover Capture Data: 80250000000008 > > > > and > > > > frame[1] WRITE 7 bytes > > 0000 80 25 00 00 00 00 08 -- -- -- -- -- -- -- -- -- |.%..... > > > > is something like configuration data, where 80 25 is 0x2580 == 9600, so > > it should work with default speed. When I use 115200, I see this: > > > > All the commands for USB modems should be described here: > > https://www.usb.org/sites/default/files/CDC_EEM10.pdf > > I'm sorry, but I don't have time currently to decode the Linux traces > and compare with FreeBSD. > One thing to also note about the Linux driver. "it just works" is only because people have inserted a crap-ton of special cases and dealt with weird quirks of different devices, and devices that are only kinda sorta standards conforming, but easy enough to hack the driver to make work. Chances are quite good you'll have to, as hps points out, puzzle through the traces to find where it's non-conformant and/or our driver is non-compliant. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqoC8QaDDRP0QoYO0C1WvT_EBmNC8UXAzG-GEbaoK0Xyg>