Date: Fri, 23 Sep 2005 00:25:48 +0900 (JST)
Message-Id: <20050923.002548.126141978.anemo@mba.ocn.ne.jp>
To: thockin@hockin.org
Cc: scampbell@malone.edu, linux-kernel@vger.kernel.org
Subject: Re: PCI Express or TG3 issue
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
In-Reply-To: <20050921181151.GA809@hockin.org>
References: <15F23A40330F5742B268A041F003055705D2A3@srv-elijah1.malone.int>
	<20050921181151.GA809@hockin.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1058
Lines: 25

>>>>> 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.

---
Atsushi Nemoto
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/