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/2] Some more USB-OHCI bugfixes [V2]
Date: Tue, 14 Oct 2008 17:13:40 +0200	[thread overview]
Message-ID: <20081014151340.GA26504@lisa> (raw)
In-Reply-To: <20081010082320.721548688@bohmer.net>

Dear Remy,

On Fri, Oct 10, 2008 at 10:23:20AM +0200, Remy Bohmer wrote:
> This is version 2 of these series!
> Only patch 1 of 2 has changed, some pedantic Coding Style issues updated that
> were not detected by Linux/scripts/checkpatch.pl.
> 
> 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.
> 
> I made it 2 seperate patches. The 1st of this series is fully tested and correct
> on at least the AT91SAM9261 cores.
> 
> 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.
> 
> 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 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...

Both patches passed my usual sequoia regression test, so I added both
to the USB custodian repository.

If nobody reports any regressions I intend to send Wolfgang a pull
request in upcoming merge window.

Thanks!

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-10-14 15:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10  8:23 [U-Boot] [patch 0/2] Some more USB-OHCI bugfixes [V2] Remy Bohmer
2008-10-10  8:23 ` [U-Boot] [patch 1/2 V2] fix USB initialisation procedure Remy Bohmer
2010-01-29  8:29   ` Daniel Hellstrom
2010-01-29 14:57     ` Remy Bohmer
2010-02-01 10:09       ` Daniel Hellstrom
2008-10-10  8:23 ` [U-Boot] [patch 2/2] The PIPE_INTERRUPT flag is used wrong Remy Bohmer
2008-10-14 15:13 ` Markus Klotzbücher [this message]
2008-10-28 23:07   ` [U-Boot] [patch 0/2] Some more USB-OHCI bugfixes [V2] Wolfgang Denk
2008-10-29  8:49     ` Markus Klotzbücher

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=20081014151340.GA26504@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