public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Will Beers <whbeers@mbio.ncsu.edu>
To: linux-kernel@vger.kernel.org
Cc: Anders Johansson <andjoh@rydsbo.net>
Subject: Re: [PATCH] proper bios handoff in ehci-hcd
Date: Tue, 13 Jul 2004 02:16:32 -0400	[thread overview]
Message-ID: <40F37E40.7070107@mbio.ncsu.edu> (raw)
In-Reply-To: <200407130744.22920.andjoh@rydsbo.net>

[-- Attachment #1: Type: text/plain, Size: 741 bytes --]

As Anders Johansson pointed out to me, the original patch is necessary - 
reversing it makes the loop

do {
                         msleep(10);
                         msec -= 10;
                         pci_read_config_dword 
(to_pci_dev(ehci->hcd.self.controller), where, &cap);
                 } while ((cap & (1 << 16)) && msec);

only execute once and makes the if block inaccessible.  Thanks for pointing 
that out...guess I was overly excited when it worked again and didn't think 
much into it.

I'm confused as to how bypassing all that via my (bad) patch allows it to 
work though.  I'd like to know more about this bit of code, if anyone have 
more general info on it, so I can keep trying to help find the culprit.

-Will




[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3186 bytes --]

  parent reply	other threads:[~2004-07-13  6:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-14 20:30 [PATCH] proper bios handoff in ehci-hcd Gary_Lerhaupt
2004-06-15 13:57 ` [linux-usb-devel] " David Brownell
2004-07-13  5:30   ` Will Beers
     [not found]     ` <200407130744.22920.andjoh@rydsbo.net>
2004-07-13  6:16       ` Will Beers [this message]
2004-07-13 18:07   ` [linux-usb-devel] " Olaf Hering
2004-07-13 20:26     ` David Brownell
2004-07-13 20:44       ` Will Beers
2004-07-13 21:11         ` David Brownell
2004-07-13 21:24           ` Will Beers
2004-07-13 21:35             ` David Brownell
2004-07-13 21:43               ` Will Beers
2004-07-13 21:31           ` Will Beers

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=40F37E40.7070107@mbio.ncsu.edu \
    --to=whbeers@mbio.ncsu.edu \
    --cc=andjoh@rydsbo.net \
    --cc=linux-kernel@vger.kernel.org \
    /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