public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Markus Klotzbücher" <mk@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [patch 0/3] Improve stability USB memory sticks for the common	OHCI USB layer.
Date: Tue, 16 Sep 2008 16:10:47 +0200	[thread overview]
Message-ID: <20080916141047.GA11431@lisa> (raw)
In-Reply-To: <20080916125541.347606297@bohmer.net>

Dear Remy,

On Tue, Sep 16, 2008 at 02:55:41PM +0200, Remy Bohmer wrote:
> This series is a set of patches that are required to make USB sticks behave 
> robust while using U-Boot on a OHCI host.
> 
> Several users complain about ERROR: CTL:TIMEOUT errors while using USB sticks,
> and while testing many different USB sticks it showed that some were working
> and many don't. It even showed a compiler dependency while debugging this, where
> GCC 3.x compilers seemed to work (but not always) and GCC 4.x compilers usually
> don't. While debugging this (with a USB analyser of course) it turned out that
> U-boot also made several protocol violations that needed to be solved, these
> resulted in hanging USB devices and so on.
> 
> In a mail thread with Stelian Pop on 28 July it was reported of a known error
> on Atmel cores that it did not work.
> 
> I tested these series on Atmel AT91SAM9261 Core, with the common OHCI driver,
> GCC 4.2.3 (Code Sourcery G++ Lite 2008q1-126)
> 
> REMEMBER: U-boot still supports 1 single USB stick at a time...

Nice work! I'll test and push your patches to the USB repo ASAP
(within the next couple of days). I'd welcome any feedback especially
from the people who reported the problems you describe.

Thanks for chasing this down!

Best regards

Markus

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de")

  parent reply	other threads:[~2008-09-16 14:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-16 12:55 [U-Boot] [patch 0/3] Improve stability USB memory sticks for the common OHCI USB layer Remy Bohmer
2008-09-16 12:55 ` [U-Boot] [patch 1/3] Fix for USB sticks not working on ARM while using GCC 4.x compilers Remy Bohmer
2008-09-16 12:55 ` [U-Boot] [patch 2/3] Refactoring parts of the common USB OHCI code Remy Bohmer
2008-09-16 12:55 ` [U-Boot] [patch 3/3] USB layer of U-Boot causes USB protocol errors while using USB memory sticks Remy Bohmer
2008-09-16 14:10 ` Markus Klotzbücher [this message]
2008-09-17  3:09   ` [U-Boot] [patch 0/3] Improve stability USB memory sticks for the commonOHCI USB layer Thao To Hieu
2008-09-17 20:31 ` [U-Boot] [patch 0/3] Improve stability USB memory sticks for the common OHCI " Markus Klotzbücher
2008-09-18 12:00 ` Stelian Pop
2008-09-18 14:54   ` Remy Bohmer
2008-09-19  8:46     ` Stelian Pop
2008-09-19  9:16       ` Remy Bohmer
2008-09-19 14:42         ` Stelian Pop
2008-09-20  9:38           ` Remy Bohmer
2008-09-20 20:14             ` Stelian Pop
2008-10-02 15:51               ` Stelian Pop
2008-10-02 18:45                 ` Remy Bohmer
2008-09-21 18:24         ` Wolfgang Denk
2008-09-22  8:26           ` Remy Bohmer
2008-09-19  9:45       ` Remy Bohmer
2008-09-19 10:05         ` Markus Klotzbücher
2008-09-19 10:19           ` Remy Bohmer
2008-09-18 15:01   ` Remy Bohmer

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=20080916141047.GA11431@lisa \
    --to=mk@denx.de \
    --cc=u-boot@lists.denx.de \
    /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