From: "Markus Klotzbücher" <mk@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [patch 0/2] Some more USB-OHCI bugfixes
Date: Wed, 8 Oct 2008 12:12:00 +0200 [thread overview]
Message-ID: <20081008101200.GB24967@lisa> (raw)
In-Reply-To: <20081008085413.978543174@bohmer.net>
Hi Remy,
On Wed, Oct 08, 2008 at 10:54:13AM +0200, Remy Bohmer wrote:
> The USB OHCI init procedure sets the maximum message length the wrong way.
> A max of 64 bits should not be done by writing '64' in maxpacketsize, but '3'.
> While fixing this problem it turned out that there is more wrong here in this
> code it turned out that the wrong bits were checked to determine if the pipe
> was of type PIPE_INTERRUPT. This series fixes those errors also.
Ok, great!
> I made it 2 seperate patches. The 1st of this series is fully tested and correct
> on at least the AT91SAM9261 cores. I hope it fixes the known problems on
> AT91SAM9263 (and other) cores also, maybe Stelian can verify this.
> If it does not help on sam9263, it should not make it worse either...
Ok, looking forward to feedback...
> The 2nd patch, however, is created by search-for-the-same-errors-and-replace.
> I am not able to test that patch, I do not have the boards, so that needs to be
> done by others or by review. It is clear that code there is buggy in the
> first place.
Ok.
> These patches require my previous series called
> 'Improve stability USB memory sticks for the common OHCI USB layer.' to be
> applied before this series. So they should apply on the u-boot-usb git tree.
> --> git://git.denx.de/u-boot-usb.git
I'll test them here on sequoia and apply if they pass :-)
> I want to mention also, that everytime I look deeper into this code, I find new
> bugs. It appears that several parts of this code is written with interrupt
> handling in mind, while we have no interrupt handling at all.
> Assumptions are done that a interrupt handler does things asynchronous, causing
> long loops that have no real use at all...
> So, no guarantees that _all_ problems are solved by now...
Yes, this is ancient Linux code, but in contrast to the linux usb
stack wasn't rewritten several times. It was considered several times
to (re) import current Linux usb code, but it's obviously no small
job...
Thank you for the great work!
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")
next prev parent reply other threads:[~2008-10-08 10:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 8:54 [U-Boot] [patch 0/2] Some more USB-OHCI bugfixes Remy Bohmer
2008-10-08 8:54 ` [U-Boot] [patch 1/2] fix USB initialisation procedure Remy Bohmer
2008-10-09 12:10 ` Jean-Christophe PLAGNIOL-VILLARD
2008-10-09 13:19 ` Wolfgang Denk
2008-10-09 14:43 ` Markus Klotzbücher
2008-10-09 14:59 ` Stefan Roese
2008-10-09 15:09 ` Markus Klotzbücher
2008-10-09 15:22 ` Jerry Van Baren
2008-10-09 18:45 ` Wolfgang Denk
2008-10-09 19:52 ` Markus Klotzbücher
2008-10-10 7:30 ` Remy Bohmer
2008-10-09 18:42 ` Wolfgang Denk
2008-10-08 8:54 ` [U-Boot] [patch 2/2] The PIPE_INTERRUPT flag is used wrong Remy Bohmer
2008-10-08 10:12 ` Markus Klotzbücher [this message]
2008-10-08 10:41 ` [U-Boot] [patch 0/2] Some more USB-OHCI bugfixes Stelian Pop
2008-10-09 8:33 ` Stelian Pop
2008-10-09 9:51 ` Remy Bohmer
2008-10-09 15:01 ` Stelian Pop
2008-10-10 7:21 ` Remy Bohmer
2008-10-10 8:25 ` Stelian Pop
2008-10-10 8:33 ` 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=20081008101200.GB24967@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