From: Tim Hockin <thockin@google.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: small PCI probe patch for odd 64 bit BARs
Date: Thu, 11 Nov 2004 09:42:17 -0800 [thread overview]
Message-ID: <20041111174217.GI19615@google.com> (raw)
In-Reply-To: <20041111172221.GB18538@kroah.com>
On Thu, Nov 11, 2004 at 09:22:21AM -0800, Greg KH wrote:
> On Wed, Nov 10, 2004 at 08:48:09PM -0800, Tim Hockin wrote:
> > The current PCI probe code breaks for 64 bit BARs that do not decode a
> > full 64 bits. Example:
> >
> > We have a device that uses a 64 bit BAR. When you write all Fs to the
> > BARs, you get:
> >
> > 000000ff ffff0000
> >
> > It wants 64k, in the first TB of RAM. The current code totally borks on
> > this.
> >
> > Simple patch against 2.6.9:
>
> As Andrew pointed out, you didn't even compile test this patch, not nice.
Yeah, I sent the 2.4 patch and called it 2.6, bny mistake. The one that
actually came out of the 2.6.9 tree here was sent a few minutes ago, and
here again.
I was in a rush, I screwed up. This version has been compile tested,
and run tested under 2.4.
Sorry, again.
--- linux-2.6.9/drivers/pci/probe.c.orig 2004-11-10 20:42:03.000000000 -0800
+++ linux-2.6.9/drivers/pci/probe.c 2004-11-11 09:30:07.000000000 -0800
@@ -144,9 +144,11 @@
pci_write_config_dword(dev, reg+4, ~0);
pci_read_config_dword(dev, reg+4, &sz);
pci_write_config_dword(dev, reg+4, l);
- if (~sz)
- res->end = res->start + 0xffffffff +
- (((unsigned long) ~sz) << 32);
+ sz = pci_size(l, sz, 0xffffffff);
+ if (sz) {
+ /* This BAR needs > 4GB? Wow. */
+ res->end |= (unsigned long)sz<<32;
+ }
#else
if (l) {
printk(KERN_ERR "PCI: Unable to handle 64-bit address for device %s\n", pci_name(dev));
prev parent reply other threads:[~2004-11-11 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 4:48 small PCI probe patch for odd 64 bit BARs Tim Hockin
2004-11-11 5:51 ` Andrew Morton
2004-11-11 17:39 ` Tim Hockin
2004-11-11 17:54 ` Greg KH
2004-11-11 20:58 ` Tim Hockin
2004-11-12 22:02 ` Greg KH
2004-11-11 17:22 ` Greg KH
2004-11-11 17:42 ` Tim Hockin [this message]
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=20041111174217.GI19615@google.com \
--to=thockin@google.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--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 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.