Path: csiph.com!feeder.erje.net!1.eu.feeder.erje.net!weretis.net!feeder4.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: Richard Owlett <rowlett@cloud85.net>
Newsgroups: linux.debian.user
Subject: Re: USB "null modem" cables and related Linux driver questions
Date: Fri, 01 Jun 2018 16:10:02 +0200
Message-ID: <vVSUG-2o7-13@gated-at.bofh.it>
References: <vVwKt-6hp-9@gated-at.bofh.it> <vVFE5-2U0-9@gated-at.bofh.it> <vVP0K-8nG-19@gated-at.bofh.it> <vVPtL-kr-5@gated-at.bofh.it> <vVRlT-1pK-1@gated-at.bofh.it> <vVShX-1WQ-9@gated-at.bofh.it>
X-Mailbox-Line: From debian-user-request@lists.debian.org  Fri Jun  1 14:09:24 2018
Old-Return-Path: <rowlett@cloud85.net>
X-Amavis-Spam-Status: No, score=-6.5 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, MDO_CABLE_TV3=0.5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate: -5
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailing-List: <debian-user@lists.debian.org> archive/latest/736188
List-ID: <debian-user.lists.debian.org>
List-URL: <https://lists.debian.org/debian-user/>
List-Archive: https://lists.debian.org/msgid-search/600a3615-96cb-e380-d009-c6a81dcc3f1b@cloud85.net
Approved: robomod@news.nic.it
Lines: 34
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Fri, 1 Jun 2018 09:08:53 -0500
X-Original-Message-ID: <600a3615-96cb-e380-d009-c6a81dcc3f1b@cloud85.net>
X-Original-References: <56f43cee-aef1-e8f0-8cbb-8e5acd8188e3@cloud85.net> <20180531235819.GA14575@alum> <72bd206e-d68c-2dd5-0098-f89a6ec6b1ed@cloud85.net> <20180601102338.GE5669@tuxteam.de> <jwvefhqu285.fsf-monnier+gmane.linux.debian.user@gnu.org> <20180601132158.GA15547@tuxteam.de>
Xref: csiph.com linux.debian.user:196328

On 06/01/2018 08:21 AM, tomas@tuxteam.de wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Fri, Jun 01, 2018 at 08:23:42AM -0400, Stefan Monnier wrote:
>>> The one choice you have is that one of both sides takes a step
>>> back and plays "gadget" [...]
> 
>> The gadget API is the programming API offered by the kernel for the OTG
>> ports: no OTG => no gadget!
>>
>>> [OTG]
> 
>> More importantly, the USB ports which support OTG are driven by
>> different hardware.
> 
> Ah, so the hardware has to play along...
> 
>> Right, you need both your hardware's USB port to support OTG and you
>> need your kernel to have a driver that supports this hardware.
>> AFAIK the driver is usually available.
> 
> Did I say I was handwaving?
> 
> Thanks for the clarifications!
> 

It also suggests that I frequently grasp some of the implications of 
what I read. Thank you.
As an illustration of my mindset:
If they had really intended USB to be *UNIVERSAL* serial bus, then it 
should have been OTG from the get go.
P.S. I know of thousands of reasons they did not.
      Vast majority preceded by $ ;/