public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: "Kok, Auke" <sofar@foo-projects.org>
Cc: Nicolas Mailhot <nicolas.mailhot@laposte.net>,
	video4linux-list@redhat.com, Michael Bueker <m.bueker@berlin.de>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net, zaitcev@redhat.com
Subject: Re: OHCI: USB webcam works, but not on USB Hub
Date: Tue, 3 Apr 2007 08:48:03 -0700	[thread overview]
Message-ID: <20070403084803.e578260d.zaitcev@redhat.com> (raw)
In-Reply-To: <46127134.7000108@foo-projects.org>

On Tue, 03 Apr 2007 08:22:28 -0700, "Kok, Auke" <sofar@foo-projects.org> wrote:

> Having the gspca driver move into the main tree would help a lot though.

I think we need to articulate better why this is an issue and not just
an excuse. We know that scheduling issues with ISO transfers exist, but
with the driver outside we can't find a specific issue let alone fix it.
These things are hard to fix as it is.

For example, an external 2.0 hub with TT moves all transactions from OHCI
to EHCI, and adds an interrupt transfer which eats into your schedule.
I'm completely unsurprised that this fails. Wanna bet that Michael's
issue is something like that?

Another thing, requiring them to make the effort comes with an implicit
promise to fix whatever the user's problem is once they have moved gspca
in-tree. I'm not ready to tackle Michael's case, so I pretended not to
see his original mail.

-- Pete

  reply	other threads:[~2007-04-03 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-03 14:41 OHCI: USB webcam works, but not on USB Hub Nicolas Mailhot
2007-04-03 15:22 ` Kok, Auke
2007-04-03 15:48   ` Pete Zaitcev [this message]
     [not found] <fa.R4OJEk76c3blNmi9oUs1xDRZGis@ifi.uio.no>
2007-04-03 14:33 ` Robert Hancock
  -- strict thread matches above, loose matches on Subject: below --
2007-04-03 12:02 Michael Bueker

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=20070403084803.e578260d.zaitcev@redhat.com \
    --to=zaitcev@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=m.bueker@berlin.de \
    --cc=nicolas.mailhot@laposte.net \
    --cc=sofar@foo-projects.org \
    --cc=video4linux-list@redhat.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