public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Alan Stern <stern@rowland.harvard.edu>,
	linux-kernel@vger.kernel.org, gregkh@suse.de,
	Mike Frysinger <vapier.adi@gmail.com>,
	Robin Getz <rgetz@blackfin.uclinux.org>
Subject: Re: [linux-usb-devel] [PATCH] : Allow embedded developers USB options normally reserved for OTG
Date: Wed, 2 Jan 2008 19:50:36 -0800	[thread overview]
Message-ID: <200801021950.36677.david-b@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0801021556070.2990-100000@iolanthe.rowland.org>

On Wednesday 02 January 2008, Alan Stern wrote:
> 
> > The transaction translators in external high speed hubs require
> > hosts to issue particular USB transactions.  If the host controller
> > doesn't implement the that split transaction support, then it won't
> > be supporting external hubs.
> 
> So in theory one could connect a high-speed hub to such a host
> controller and expect it to communicate with high-speed devices.  So
> long as no full- or low-speed devices are added there wouldn't be any
> split transactions.  It wouldn't be USB-2.0 compliant but it should
> still work.

Yes ...

But that would be a nightmare in terms of support calls.  Take
two USB trees, and swap the hub ... suddenly one of the downstream
devices (the full speed one) starts (or stops!) working!  That's
not the sort of issue any support line wants to cope with on a
day-to-day basis.

The accounting for those products is often along the lines of:
if you got a support call, you didn't profit from that sale.
(And from the user perspective it's just a PITA and waste of
time.)  So *every* confusion like that one gets removed.

- Dave

  reply	other threads:[~2008-01-03  3:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 14:48 [PATCH] : Allow embedded developers USB options normally reserved for OTG Robin Getz
2008-01-02 18:47 ` [linux-usb-devel] " David Brownell
2008-01-02 18:57   ` Felipe Balbi
2008-01-02 19:14     ` David Brownell
2008-01-02 18:58   ` Mike Frysinger
2008-01-02 19:16     ` David Brownell
2008-01-02 19:46     ` Alan Stern
2008-01-02 20:25       ` David Brownell
2008-01-02 20:58         ` Alan Stern
2008-01-03  3:50           ` David Brownell [this message]
2008-01-03  3:52           ` Bryan Wu
2008-01-03 17:01           ` Richard D
2008-01-03  3:03   ` Robin Getz
2008-01-03  3:43     ` David Brownell
2008-01-03  4:40       ` Bryan Wu
2008-01-03  7:36         ` David Brownell
2008-01-03  8:05           ` Bryan Wu
2008-01-03 17:04             ` Richard D
2008-01-04  1:20               ` Robin Getz
2008-01-03  7:58       ` Robin Getz
2008-01-03  3:47   ` Bryan Wu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200801021950.36677.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=rgetz@blackfin.uclinux.org \
    --cc=stern@rowland.harvard.edu \
    --cc=vapier.adi@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox