From owner-freebsd-usb@freebsd.org Fri Nov 2 14:10:55 2018 Return-Path: Delivered-To: freebsd-usb@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18EC810F82FB for ; Fri, 2 Nov 2018 14:10:55 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it1-x12e.google.com (mail-it1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9BA186C938 for ; Fri, 2 Nov 2018 14:10:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it1-x12e.google.com with SMTP id e74-v6so3326090ita.2 for ; Fri, 02 Nov 2018 07:10:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kr4XGdEz5uyos+jsGF/WR/1qU15PkjA+Fk02FVs+z9s=; b=tLGpL/m07pozFDBir2myDrizlbWikVytSvuBxPObiF2EX3tUptrRb6h0H4tlf1J5KT Ov0PMSZ0dU/FtS6Fe5eWlQ/yeF6Vj8krStBCwXqZlxzb6IL8TpqaPaOSht4ua5v1i7Dw +BEO+RrSCvW33nZxt7LlACn9go/tLUcEUYxrQY+oc1G6D3hSfucPsTB/85c2sYymJX4G a6NmV81Rul4KizMjkT4MK0y9o6A0YQgQxhKWIJlGz4C9XJsejEvAeZNPW/dCd2kAm1yi E55nCoGtUyJ86eL2UWGAIooYwbjnO46//GBqQq2JdQuhRBy8GNoAaXhsCas+Ya+KwP35 FRZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kr4XGdEz5uyos+jsGF/WR/1qU15PkjA+Fk02FVs+z9s=; b=pYbyGLtnXsuWXYrkoJBRn8HH6RU8jczh2XCajzuRlW7Ng4AJvo+CjWN7xnOzYlqjyb 7dKEMSlyQLaBjvXOQ3ESj8weeXey1eithGP98M5m+Jw/CD/RXVlSnZ6J4yggLPZwkNca F0b2KPvgIg6oh7hGkGFW0hYmKUD0juTje9+wBlwG0eSmqegcapZDfkZ7PQp58DifK1pQ X39ut4CFi2Oe+4TUsEU/IFmQThpQvjzGXHdal2MnOpPF0fIaozRhnDQbKprEA55LmKdc HgzI6rXMxZE0mQUjBkoe2yU6oxfh90hLaJzX30vnY47c89MXnWCjorVDvGKZLIExnQLa L2Jg== X-Gm-Message-State: AGRZ1gKihSQ4VKbRMdNrhbSpP+6AEKYFPVBIGaZDaLq+VfYge3hu1Tza 613y4JBkT+qvgDeGvfCbYvatvWDNc2aXYjOS+KQdxA== X-Google-Smtp-Source: AJdET5d5INVsPaIsKtENHcaUZWLRkFKlQ1B9gnK1vyOmSG2QyS0sfWveWg38iEO58Wt5bIHJG/wSeUJE2p94/bIQOJA= X-Received: by 2002:a02:31d:: with SMTP id y29-v6mr10481373jad.98.1541167853790; Fri, 02 Nov 2018 07:10:53 -0700 (PDT) MIME-Version: 1.0 References: <0c4022f3-bd21-49b5-cadd-daeb9f1f3081@selasky.org> <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> <0dd7b89f-6a82-1d6e-0d0a-4f2b9515bd5d@yandex.ru> In-Reply-To: <0dd7b89f-6a82-1d6e-0d0a-4f2b9515bd5d@yandex.ru> From: Warner Losh Date: Fri, 2 Nov 2018 08:10:42 -0600 Message-ID: Subject: Re: umodem0, Cisco USB serial console, and quirks To: "Andrey V. Elsukov" Cc: Hans Petter Selasky , mandrews@bit0.com, "freebsd-usb@FreeBSD.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2018 14:10:55 -0000 On Fri, Nov 2, 2018 at 8:04 AM Andrey V. Elsukov 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