From: thockin@hockin.org
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: scampbell@malone.edu, linux-kernel@vger.kernel.org
Subject: Re: PCI Express or TG3 issue
Date: Thu, 22 Sep 2005 08:58:54 -0700 [thread overview]
Message-ID: <20050922155854.GA31157@hockin.org> (raw)
In-Reply-To: <20050923.002548.126141978.anemo@mba.ocn.ne.jp>
On Fri, Sep 23, 2005 at 12:25:48AM +0900, Atsushi Nemoto wrote:
> >>>>> On Wed, 21 Sep 2005 11:11:51 -0700, thockin@hockin.org said:
>
> thockin> This device is claiming that it has a 64-bit base-address
> thockin> which has been programmed by BIOS to be at
> thockin> 0x80000001d0000000.
>
> thockin> I suspect that the 4 bytes at offset 0x14 want to be 0. The
> thockin> address 0xd0000000 jives with the rest of your PCI listing.
>
> thockin> I don't know where that extra 0x80000001 comes from, but it's
> thockin> pretty clearly wrong. BIOS bug? I can't see where kernel
> thockin> would have boned that up *that* badly.
>
> I also have seen same problem on some custom MIPS-based boards which
> do not have BIOS. Broadcom BCM5751 had garbage in its 64-bit BAR on
> power-up. So it should not be a BIOS bug. And I also could not find
> any good place to fixup it at that time.
Well, on a PC (i386 or x86_64) system, that address is almost certainly
going to be below 4G. You could reguister a quirk to zero the upper half
of that BAR...
next prev parent reply other threads:[~2005-09-22 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 17:34 FW: PCI Express or TG3 issue Campbell, Shawn
2005-09-21 18:11 ` thockin
2005-09-22 15:25 ` Atsushi Nemoto
2005-09-22 15:58 ` thockin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-21 15:56 Shawn M. Campbell
2005-09-21 17:21 ` thockin
2005-09-21 17:18 ` Martin Mares
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=20050922155854.GA31157@hockin.org \
--to=thockin@hockin.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=scampbell@malone.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).