From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: trenn@suse.de, linux-acpi <linux-acpi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Len Brown <lenb@kernel.org>, Andrew Morton <akpm@osdl.org>,
Jean Delvare <khali@linux-fr.org>
Subject: Re: [PATCH 0/5] Detect hwmon and i2c bus drivers interfering with ACPI Operation Region resources
Date: Mon, 29 Oct 2007 13:11:59 +0000 [thread overview]
Message-ID: <20071029131159.GA27283@srcf.ucam.org> (raw)
In-Reply-To: <200710282050.34166.bjorn.helgaas@hp.com>
On Sun, Oct 28, 2007 at 08:50:33PM -0600, Bjorn Helgaas wrote:
> On Saturday 27 October 2007 9:09:47 am Matthew Garrett wrote:
> > On Thu, Oct 25, 2007 at 09:06:22AM -0600, Bjorn Helgaas wrote:
> > > But we really *should* reserve things used by opregions, shouldn't
> > > we? After all, the whole point of resource reservation is to prevent
> > > conflicts.
> >
> > Only if you're happy to lose functionality like IDE, sadly.
>
> That's a simplistic answer to a complex problem. I don't think
> we should just ignore the whole problem, cross our fingers, and
> hope that firmware stays out of our way.
Right now, there's not really any other way of handling it. The firmware
may screw with pretty much everything, and it might even be safe for it
to do so in many cases. In any case, you don't necessarily win that much
by registering all the opregions, since SMI can go behind your back and
write to stuff that's not declared in the DSDT anyway.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2007-10-29 13:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 14:31 [PATCH 0/5] Detect hwmon and i2c bus drivers interfering with ACPI Operation Region resources Thomas Renninger
2007-10-25 3:57 ` Andrew Morton
2007-10-25 13:51 ` Jean Delvare
2007-10-25 20:24 ` Andrew Morton
2007-10-26 19:23 ` Jean Delvare
2007-10-25 12:04 ` Mark M. Hoffman
2007-10-25 15:54 ` Jean Delvare
2007-10-25 15:06 ` Bjorn Helgaas
2007-10-25 22:55 ` Thomas Renninger
2007-10-26 3:59 ` Bjorn Helgaas
2007-10-26 10:45 ` Thomas Renninger
2007-10-26 13:09 ` Bjorn Helgaas
2007-10-26 20:39 ` Jean Delvare
2007-10-27 15:09 ` Matthew Garrett
2007-10-29 2:50 ` Bjorn Helgaas
2007-10-29 13:11 ` Matthew Garrett [this message]
2007-10-30 18:43 ` Jean Delvare
2007-10-25 21:36 ` Len Brown
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=20071029131159.GA27283@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=khali@linux-fr.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
/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