From: David Woodhouse <dwmw2@infradead.org>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Ray Lee <ray-lk@madrabbit.org>,
torvalds@linux-foundation.org,
Andrew Morton <akpm@linux-foundation.org>,
Faidon Liambotis <paravoid@debian.org>,
Matt Domsch <Matt_Domsch@dell.com>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, bero@arklinux.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] intel-iommu: Work around yet another BIOS bug
Date: Thu, 20 Aug 2009 22:54:58 +0100 [thread overview]
Message-ID: <1250805298.3311.62.camel@macbook.infradead.org> (raw)
In-Reply-To: <20090820214712.GA26360@lackof.org>
On Thu, 2009-08-20 at 15:47 -0600, Grant Grundler wrote:
>
> Could that be to reserve address space that the "disabled" IOMMU
> might still be responding to?
>
> Ie the BIOS hides the control registers so the OS won't talk to the
> device but the IOMMU might still attempt to lookup certain address
> ranges.
>
> I'm more inclined to believe it's sloppiness on the part of the BIOS
> writers but thought this might be an alternative explanation.
Nah, this is just the normal story: "We smoked too much crack and fried
our brains, and we don't do any QA on the crap we write because that
would leave fewer hours in the day for us to service our crack habit".
We _really_ need open source firmware.
Or at _least_ firmware written by competent engineers -- but I think
we've all fairly much given up on that happening by now?
--
dwmw2
next prev parent reply other threads:[~2009-08-20 21:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14003-10286@http.bugzilla.kernel.org/>
2009-08-19 21:26 ` [Bugme-new] [Bug 14003] New: Infinite loop on bootup while handling DMAR Andrew Morton
2009-08-20 1:15 ` Suresh Siddha
2009-08-20 7:52 ` David Woodhouse
2009-08-20 8:01 ` [PATCH] intel-iommu: Work around yet another BIOS bug David Woodhouse
2009-08-20 9:44 ` Andrew Morton
2009-08-20 11:14 ` David Woodhouse
2009-08-20 18:48 ` Andrew Morton
2009-08-20 12:36 ` Matthew Wilcox
2009-08-20 19:29 ` Ray Lee
2009-08-20 19:32 ` David Woodhouse
2009-08-20 21:47 ` Grant Grundler
2009-08-20 21:54 ` David Woodhouse [this message]
2009-08-31 13:15 ` Carl-Daniel Hailfinger
2009-08-20 8:40 ` [Bugme-new] [Bug 14003] New: Infinite loop on bootup while handling DMAR Faidon Liambotis
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=1250805298.3311.62.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=Matt_Domsch@dell.com \
--cc=akpm@linux-foundation.org \
--cc=bero@arklinux.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=grundler@parisc-linux.org \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=paravoid@debian.org \
--cc=ray-lk@madrabbit.org \
--cc=suresh.b.siddha@intel.com \
--cc=torvalds@linux-foundation.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®