From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Thomas Renninger <trenn@suse.de>, 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: Mon, 20 Oct 2008 19:24:16 +0100 [thread overview]
Message-ID: <20081020182416.GA13676@srcf.ucam.org> (raw)
In-Reply-To: <20081020181622.GJ18277@khazad-dum.debian.net>
On Mon, Oct 20, 2008 at 04:16:22PM -0200, Henrique de Moraes Holschuh wrote:
> On Mon, 20 Oct 2008, Matthew Garrett wrote:
> > I'd be surprised if nobody has done it. The hardware is above the
> > minimum spec.
>
> I'd ask someone that did before I assume it worked fine (i.e. "does it
> suspend and resume to RAM properly when running XP? when running
> Vista?")...
C state transitions, not S state. Working properly here means not
hanging the moment ACPI processor power management starts.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-10-20 18:24 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 [this message]
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
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=20081020182416.GA13676@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--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=trenn@suse.de \
--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