Date: Fri, 2 Nov 2018 22:32:07 +0800 From: blubee blubeeme <gurenchan@gmail.com> To: Warner Losh <imp@bsdimp.com> Cc: "Andrey V. Elsukov" <bu7cher@yandex.ru>, "freebsd-usb@FreeBSD.org" <freebsd-usb@freebsd.org> Subject: Re: umodem0, Cisco USB serial console, and quirks Message-ID: <CALM2mEk4F4Bq_6t9eY=ZorymuK_K0OkSAjyyOZG-sTONi4NHPQ@mail.gmail.com> In-Reply-To: <CANCZdfoQdKXL4F88UckcbeMjPKa_FABU6QiHSVi9CTGETfMW8g@mail.gmail.com> 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> <CANCZdfqoC8QaDDRP0QoYO0C1WvT_EBmNC8UXAzG-GEbaoK0Xyg@mail.gmail.com> <0dd7b89f-6a82-1d6e-0d0a-4f2b9515bd5d@yandex.ru> <CANCZdfoQdKXL4F88UckcbeMjPKa_FABU6QiHSVi9CTGETfMW8g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 2, 2018, 22:11 Warner Losh <imp@bsdimp.com> wrote: > On Fri, Nov 2, 2018 at 8:04 AM Andrey V. Elsukov <bu7cher@yandex.ru> > wrote: > > > On 02.11.2018 16:59, Warner Losh wrote: > > > 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. > > > > So, when it "just work" under Linux, Windows and Mac OS, but doesn't > > work under FreeBSD, I suspect we need fix FreeBSD :) > > > > We need to add support for this device yes. However, my point is that the > other systems may have quirks and kinks in their drivers to cope with the > non-conformity of a device that doesn't quite conform to the standards. > This was to answer an earlier assertion that the device was standard, which > I don't believe to be supported by the facts. There's some quirk or special > driver needed for this odd-ball device. Since it can be almost impossible > to do this work from pure traces alone, the person with the device needs to > puzzle it out, or pay someone to puzzle it out... > > Warner > Lol > _______________________________________________ > freebsd-usb@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-usb > To unsubscribe, send any mail to "freebsd-usb-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALM2mEk4F4Bq_6t9eY=ZorymuK_K0OkSAjyyOZG-sTONi4NHPQ>