From: Thomas Renninger <trenn@suse.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Len Brown <lenb@kernel.org>,
linux-acpi <linux-acpi@vger.kernel.org>,
Zhao Yakui <yakui.zhao@intel.com>,
me@markdoughty.co.uk,
linux-thinkpad <linux-thinkpad@linux-thinkpad.org>,
"devel@acpica.org" <devel@acpica.org>
Subject: Re: [RESEND] [PATCH 2/3] Introduce acpi_root_table=rsdt boot param and dmi list to force rsdt
Date: Tue, 21 Oct 2008 16:12:14 +0200 [thread overview]
Message-ID: <200810211612.15776.trenn@suse.de> (raw)
In-Reply-To: <20081021140014.GA29330@srcf.ucam.org>
On Tuesday 21 October 2008 16:00:14 Matthew Garrett wrote:
> On Tue, Oct 21, 2008 at 04:01:55PM +0200, Rafael J. Wysocki wrote:
> > Moreover, as soon as the real fix is developed we can remove the DMI
> > list. Quite frankly, I don't see any downsides.
>
> The downside is that with the DMI list there's significantly less
> incentive to produce a "real" fix (assuming there is one). We've no idea
> how many other systems may be affected in one way or another.
With the boot param you at least get an idea how many other sytems are
affected.
If you run the linuxfirmwarekit, AFAIK there is a test: it extracts both FADTs
and compares the 32 and 64 bit addresses in case both are not 0 and throws a
warning it they differ.
If people see this and they have some mysterious problem, they should give
this: acpi_root_table=rsdt boot param a try (after applying the patches) and
report back.
Thanks,
Thomas
next prev parent reply other threads:[~2008-10-21 14:12 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 21:50 [RESEND] [PATCH 2/3] Introduce acpi_root_table=rsdt boot param and dmi list to force rsdt Thomas Renninger
2008-10-20 1:01 ` Matthew Garrett
2008-10-20 15:31 ` Henrique de Moraes Holschuh
2008-10-20 16:23 ` Thomas Renninger
2008-10-20 16:27 ` Matthew Garrett
2008-10-20 16:48 ` Thomas Renninger
2008-10-20 16:54 ` Matthew Garrett
2008-10-20 17:51 ` Henrique de Moraes Holschuh
2008-10-20 17:58 ` Matthew Garrett
2008-10-20 18:16 ` Henrique de Moraes Holschuh
2008-10-20 18:24 ` Matthew Garrett
2008-10-20 18:47 ` Henrique de Moraes Holschuh
2008-10-20 18:52 ` Matthew Garrett
2008-10-20 19:25 ` Henrique de Moraes Holschuh
2008-10-21 8:14 ` Thomas Renninger
2008-10-21 9:53 ` Thomas Renninger
2008-10-21 9:57 ` Thomas Renninger
2008-10-21 12:46 ` Matthew Garrett
2008-10-21 13:05 ` Thomas Renninger
2008-10-21 13:08 ` Matthew Garrett
2008-10-21 13:34 ` Thomas Renninger
2008-10-21 14:01 ` Rafael J. Wysocki
2008-10-21 14:00 ` Matthew Garrett
2008-10-21 14:12 ` Thomas Renninger [this message]
2008-10-21 14:19 ` Matthew Garrett
2008-10-21 14:25 ` Rafael J. Wysocki
2008-10-21 14:29 ` Matthew Garrett
2008-10-21 14:45 ` Thomas Renninger
2008-10-21 14:49 ` Matthew Garrett
2008-10-21 15:10 ` Rafael J. Wysocki
2008-10-21 15:27 ` Matthew Garrett
2008-10-21 15:46 ` Henrique de Moraes Holschuh
2008-10-21 15:50 ` Matthew Garrett
2008-10-21 16:58 ` [ltp] " Henrique de Moraes Holschuh
2008-10-21 17:02 ` Matthew Garrett
2008-10-21 19:04 ` Rafael J. Wysocki
2008-10-20 16:43 ` Thomas Renninger
2008-10-20 18:05 ` Henrique de Moraes Holschuh
2008-10-20 15:46 ` Henrique de Moraes Holschuh
2008-10-21 11:07 ` Thomas Renninger
2008-11-11 0:58 ` Matthew Garrett
2008-11-12 23:58 ` Thomas Renninger
2008-11-13 0:56 ` Matthew Garrett
2008-11-13 2:21 ` [Devel] " Zhang Rui
2008-11-13 2:24 ` Matthew Garrett
2008-11-13 8:27 ` Zhang Rui
2008-11-13 11:13 ` Matthew Garrett
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=200810211612.15776.trenn@suse.de \
--to=trenn@suse.de \
--cc=devel@acpica.org \
--cc=hmh@hmh.eng.br \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-thinkpad@linux-thinkpad.org \
--cc=me@markdoughty.co.uk \
--cc=mjg59@srcf.ucam.org \
--cc=rjw@sisk.pl \
--cc=yakui.zhao@intel.com \
/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