All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Will Beers <whbeers@mbio.ncsu.edu>
Cc: Olaf Hering <olh@suse.de>,
	Gary_Lerhaupt@Dell.com, linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, Stuart_Hayes@Dell.com
Subject: Re: [linux-usb-devel] [PATCH] proper bios handoff in ehci-hcd
Date: Tue, 13 Jul 2004 14:35:44 -0700	[thread overview]
Message-ID: <40F455B0.2090008@pacbell.net> (raw)
In-Reply-To: <40F45327.1080703@mbio.ncsu.edu>

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

Will Beers wrote:
>  > Sounds to me like your BIOS may be broken.  But if you're
>  > up for it, you could try using byte access to write that one
> 
> Changing the pci_read_config to a byte access fixes it, thanks!

You're reading byte 0 not byte 2 of that field ... I meant
more like the attached patch to _write_ the flag (untested).


> -                       pci_read_config_dword(pdev, where, &cap);
> +                       pci_read_config_byte(pdev, where, &cap);

[-- Attachment #2: Diff --]
[-- Type: text/plain, Size: 407 bytes --]

--- 1.89/drivers/usb/host/ehci-hcd.c	Wed Jun 30 19:10:04 2004
+++ edited/drivers/usb/host/ehci-hcd.c	Tue Jul 13 14:33:41 2004
@@ -293,8 +293,7 @@
 		struct pci_dev *pdev = to_pci_dev(ehci->hcd.self.controller);
 
 		/* request handoff to OS */
-		cap |= 1 << 24;
-		pci_write_config_dword(pdev, where, cap);
+		pci_write_config_byte(pdev, where + 3, 1);
 
 		/* and wait a while for it to happen */
 		do {

  reply	other threads:[~2004-07-13 21:37 UTC|newest]

Thread overview: 18+ 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
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 [this message]
2004-07-13 21:43               ` Will Beers
2004-07-13 21:31           ` Will Beers
  -- strict thread matches above, loose matches on Subject: below --
2004-07-13 20:52 Stuart_Hayes
2004-07-13 21:56 ` Pete Zaitcev
2004-07-13 23:04   ` David Brownell
2004-07-15  9:37     ` Olaf Hering
2004-08-05 13:39       ` Olaf Hering
2004-08-05 15:49         ` David Brownell

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=40F455B0.2090008@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=Gary_Lerhaupt@Dell.com \
    --cc=Stuart_Hayes@Dell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=olh@suse.de \
    --cc=whbeers@mbio.ncsu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.