From: Linus Torvalds <torvalds@linux-foundation.org>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>, Tejun Heo <htejun@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
David Witbrodt <dawitbro@sbcglobal.net>,
Andrew Morton <akpm@linux-foundation.org>,
Kernel Testers <kernel-testers@vger.kernel.org>
Subject: Re: Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd
Date: Sat, 30 Aug 2008 12:41:04 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808301238390.3290@nehalem.linux-foundation.org> (raw)
In-Reply-To: <86802c440808301226h1e7a9bb6g721ecdb0f93c5220@mail.gmail.com>
On Sat, 30 Aug 2008, Yinghai Lu wrote:
>
> AMD CPU/NB (quad core aka fam 10h later) has MSR to state MMCONFIG, and
> the ATI bridge BAR that have same address for MMCONFIG not even have
> chance to decode that, because NB intercept that already.
Ok, so it's similar to the local APIC in that respect (and presumably IO
APIC too, I haven't checked).
But that still just implies that the BAR probably means something else
totally, and the fact that it happens to have the same value as the MCFG
is just random luck.
> it seems ATI chipset doesn't have public version of doc...like reg
> info and BIOS/Kernel porting guide.
Yeah, I'm not finding anything either. The 690G databook that Rafael
pointed to does mention the config registers in passing, but it's really
just about electricals (pin setup etc). No BIOS writers guide indeed..
Linus
next prev parent reply other threads:[~2008-08-30 19:42 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 23:26 Linux 2.6.27-rc5 Linus Torvalds
2008-08-29 15:42 ` cpu time oddity (was Re: Linux 2.6.27-rc5) Alistair John Strachan
2008-08-29 15:56 ` Alistair John Strachan
2008-08-29 17:13 ` Linux 2.6.27-rc5 Rafael J. Wysocki
2008-08-29 19:57 ` Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd Rafael J. Wysocki
2008-08-29 21:13 ` Yinghai Lu
2008-08-29 21:19 ` Yinghai Lu
2008-08-29 22:32 ` Rafael J. Wysocki
2008-08-29 22:31 ` Rafael J. Wysocki
2008-08-29 23:24 ` Yinghai Lu
2008-08-30 0:08 ` Linus Torvalds
2008-08-30 0:11 ` Yinghai Lu
2008-08-30 0:45 ` Linus Torvalds
2008-08-30 1:11 ` Linus Torvalds
2008-08-30 1:30 ` Yinghai Lu
2008-08-30 2:33 ` Linus Torvalds
2008-08-30 2:56 ` Linus Torvalds
2008-08-30 3:07 ` Yinghai Lu
2008-08-30 3:24 ` Linus Torvalds
2008-08-30 4:41 ` Yinghai Lu
2008-08-30 5:02 ` Yinghai Lu
2008-08-30 5:52 ` Linus Torvalds
2008-08-30 6:18 ` Linus Torvalds
2008-08-30 8:02 ` Yinghai Lu
2008-08-30 5:22 ` Yinghai Lu
2008-08-30 6:11 ` Linus Torvalds
2008-08-30 3:15 ` Linus Torvalds
2008-08-30 3:00 ` Yinghai Lu
2008-08-30 3:10 ` Linus Torvalds
2008-08-30 1:14 ` Yinghai Lu
2008-08-30 2:16 ` Linus Torvalds
2008-08-30 2:29 ` Yinghai Lu
2008-08-30 0:20 ` Yinghai Lu
2008-08-30 0:27 ` Yinghai Lu
2008-08-30 13:32 ` Rafael J. Wysocki
2008-08-30 16:05 ` Yinghai Lu
2008-08-30 17:14 ` Rafael J. Wysocki
2008-08-30 17:55 ` Yinghai Lu
2008-08-30 18:11 ` Yinghai Lu
2008-08-30 19:06 ` Yinghai Lu
2008-08-30 19:51 ` Rafael J. Wysocki
2008-08-30 20:10 ` Yinghai Lu
2008-08-29 21:44 ` Linus Torvalds
2008-08-29 22:30 ` Rafael J. Wysocki
2008-08-30 17:39 ` Linus Torvalds
2008-08-30 18:07 ` Yinghai Lu
2008-08-30 18:43 ` Linus Torvalds
2008-08-30 19:10 ` Yinghai Lu
2008-08-30 19:31 ` Linus Torvalds
2008-08-30 20:14 ` Yinghai Lu
2008-08-30 20:38 ` Yinghai Lu
2008-08-30 20:46 ` Rafael J. Wysocki
2008-08-30 21:12 ` Yinghai Lu
2008-08-30 21:13 ` Yinghai Lu
2008-08-30 21:34 ` Rafael J. Wysocki
2008-08-30 21:49 ` Yinghai Lu
2008-08-31 1:10 ` Yinghai Lu
2008-08-31 12:27 ` Rafael J. Wysocki
2008-08-31 17:42 ` Linus Torvalds
2008-08-31 17:54 ` Yinghai Lu
2008-08-31 18:03 ` Linus Torvalds
2008-08-31 21:03 ` Yinghai Lu
2008-09-01 17:53 ` Linus Torvalds
2008-08-30 22:41 ` Linus Torvalds
2008-08-30 22:50 ` Yinghai Lu
2008-08-30 23:28 ` Linus Torvalds
2008-08-30 23:39 ` Yinghai Lu
2008-08-31 0:27 ` Yinghai Lu
2008-08-31 0:50 ` Yinghai Lu
2008-08-31 3:00 ` Linus Torvalds
2008-08-31 3:53 ` Yinghai Lu
2008-08-31 3:58 ` Linus Torvalds
2008-08-31 4:12 ` Linus Torvalds
2008-08-30 19:14 ` Linus Torvalds
2008-08-30 19:26 ` Yinghai Lu
2008-08-30 19:41 ` Linus Torvalds [this message]
2008-08-30 19:48 ` Yinghai Lu
2008-08-30 19:29 ` Rafael J. Wysocki
2008-08-30 19:29 ` Yinghai Lu
2008-08-30 19:20 ` Rafael J. Wysocki
2008-08-29 22:34 ` Jeff Garzik
2008-08-29 22:47 ` Rafael J. Wysocki
2008-08-30 10:34 ` [PATCH] Re: Linux 2.6.27-rc5 Helge Deller
2008-08-30 20:21 ` Rafael J. Wysocki
2008-09-01 22:28 ` Al Viro
2008-08-31 23:27 ` J.A. Magallón
[not found] ` <328e43f00808311825r71164541pd4159a4a33b9b038@mail.gmail.com>
2008-09-01 7:12 ` Francois Romieu
-- strict thread matches above, loose matches on Subject: below --
2008-08-30 6:13 Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd David Witbrodt
2008-08-30 6:21 ` Linus Torvalds
2008-08-30 6:58 David Witbrodt
2008-08-30 23:29 David Witbrodt
2008-08-31 0:16 ` Yinghai Lu
2008-08-31 1:25 David Witbrodt
2008-08-31 2:17 ` Yinghai Lu
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=alpine.LFD.1.10.0808301238390.3290@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=dawitbro@sbcglobal.net \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=yhlu.kernel@gmail.com \
/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