From: Andi Kleen <ak@suse.de>
To: Jeff Garzik <jeff@garzik.org>
Cc: discuss@x86-64.org, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: Please pull x86-64 bug fixes
Date: Thu, 5 Oct 2006 22:10:39 +0200 [thread overview]
Message-ID: <200610052210.39930.ak@suse.de> (raw)
In-Reply-To: <452564B9.4010209@garzik.org>
On Thursday 05 October 2006 22:02, Jeff Garzik wrote:
> Andi Kleen wrote:
> > If the choice is between a secret NDA only card with dubious
> > functionality and booting on lots of modern boards I know what to
> > choose.
>
> That's a strawman argument. There is no need to choose. You can
> clearly boot on lots of modern boards with mmconfig just fine. We just
> need to narrow down which ones.
You want a huge white list or what? And you volunteer to maintain
it?
My current thinking is to just wait for Vista certified machines
and then use DMI year >= 2007 or so to enable it.
Most likely your secret card won't ship before that anyways and
maybe it can be even somehow used without MCFG. And if it can't
it is out of luck right now. Send blame to the BIOS writers
who are unable to get the MCFG tables right.
I don't think white list is the right answer though. If it
was only a small list of machines with broken BIOS it would
be possible to black list, but Intel pretty much sabotated that
by releasing a broken reference BIOS that is used in lots of different
boards.
I considered PCI ID checking for those chipsets instead of
SMBIOS checking, but that has other problems too.
-Andi
next prev parent reply other threads:[~2006-10-05 20:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 17:10 Please pull x86-64 bug fixes Andi Kleen
2006-10-05 17:17 ` Jeff Garzik
2006-10-05 17:31 ` [discuss] " Andi Kleen
2006-10-05 17:43 ` Jeff Garzik
2006-10-05 17:53 ` Andi Kleen
2006-10-05 19:29 ` Jeff Garzik
2006-10-05 19:42 ` Andi Kleen
2006-10-05 20:02 ` Jeff Garzik
2006-10-05 20:10 ` Andi Kleen [this message]
2006-10-05 22:45 ` Linus Torvalds
2006-10-05 22:52 ` Andi Kleen
2006-10-05 23:07 ` Linus Torvalds
2006-10-05 23:21 ` Andi Kleen
2006-10-05 23:36 ` Jeff Garzik
2006-10-06 0:57 ` Jeff Garzik
2006-10-06 1:29 ` Linus Torvalds
2006-10-06 11:03 ` Arjan van de Ven
2006-10-06 16:07 ` Linus Torvalds
2006-10-06 16:19 ` Arjan van de Ven
2006-10-06 22:01 ` Rafael J. Wysocki
2006-10-06 22:31 ` Duran, Leo
2006-10-06 23:06 ` Jeff Garzik
2006-10-07 5:23 ` Arjan van de Ven
2006-10-07 2:20 ` Linus Torvalds
2006-10-08 20:59 ` Duran, Leo
2006-10-08 22:42 ` Linus Torvalds
2006-10-05 22:00 ` Alan Cox
2006-10-05 21:44 ` Andi Kleen
2006-10-06 11:14 ` Alan Cox
2006-10-16 12:21 ` Andi Kleen
2006-10-05 17:21 ` Linus Torvalds
2006-10-05 17:27 ` [discuss] " Andi Kleen
2006-10-05 22:59 ` Linus Torvalds
2006-10-05 23:05 ` Andi Kleen
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=200610052210.39930.ak@suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox