From: Arjan van de Ven <arjan@infradead.org>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] quiet MMCONFIG related printks
Date: Wed, 03 Jan 2007 05:52:33 -0800 [thread overview]
Message-ID: <1167832353.3095.18.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20070102103602.28a873ea@localhost.localdomain>
On Tue, 2007-01-02 at 10:36 +0000, Alan wrote:
> On Mon, 1 Jan 2007 21:01:38 -0800
> Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>
> > Using MMCONFIG for PCI config space access is simply an optimization, not
> > a requirement. Therefore, when it can't be used, there's no need for
>
> Some hardware reqires MCFG. In addition this is an error, a real error on
> the vendors part or ours and could indicate there are many other BIOS
> problems outstanding.
>
> We shouldn't keep quiet about serious errors in tables, we need people to
> know and be able to take appropriate action (eg new BIOSen, refusing
> certifications etc).
to some degree that is what the firmware kit is for ;)
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
next prev parent reply other threads:[~2007-01-03 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 5:01 Jesse Barnes
2007-01-02 10:36 ` Alan
2007-01-02 16:37 ` Jesse Barnes
2007-01-03 13:52 ` Arjan van de Ven [this message]
2007-01-03 13:53 ` Arjan van de Ven
2007-01-03 16:49 ` Jesse Barnes
2007-01-03 17:01 ` Arjan van de Ven
2007-01-03 19:29 ` Stephen Clark
2007-01-03 17:20 ` Jesse Barnes
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=1167832353.3095.18.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jbarnes@virtuousgeek.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®