From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH] quiet MMCONFIG related printks
Date: Tue, 2 Jan 2007 08:37:44 -0800 [thread overview]
Message-ID: <200701020837.45016.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20070102103602.28a873ea@localhost.localdomain>
On Tuesday, January 2, 2007 2:36 am, 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.
Ok, I was mistaken then. However, I see this on several boxes, and the
broken BIOSen out in the wild are unlikely to be fixed. Maybe this
should really be a KERN_WARNING instead since it may indicate that some
devices will fail to work?
> 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).
Ok.
Jesse
next prev parent reply other threads:[~2007-01-02 16:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 5:01 [PATCH] quiet MMCONFIG related printks Jesse Barnes
2007-01-02 10:36 ` Alan
2007-01-02 16:37 ` Jesse Barnes [this message]
2007-01-03 13:52 ` Arjan van de Ven
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=200701020837.45016.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.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