From: Mitch Bradley <wmb@firmworks.com>
To: jg@laptop.org
Cc: Pavel Machek <pavel@ucw.cz>, "Brown, Len" <len.brown@intel.com>,
ACPI ML <linux-acpi@vger.kernel.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Adam Belay <abelay@novell.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Arjan van de Ven <arjan@linux.intel.com>,
devel@laptop.org, Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: ACPI: Idle Processor PM Improvements
Date: Tue, 12 Sep 2006 08:27:51 -1000 [thread overview]
Message-ID: <4506FC27.70507@firmworks.com> (raw)
In-Reply-To: <1158084871.28991.489.camel@localhost.localdomain>
Jim Gettys wrote:
>
> I haven't checked if there are any write-only
> registers in the Geode (though, thankfully, this kind of brain damage is
> rarer than it once was).
I've been going through the Geode and 5536 specs with a fine-toothed
comb, and so far haven't seen any write-only registers apart from the
ones in the ISA legacy devices.
next prev parent reply other threads:[~2006-09-12 18:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 18:40 [RFC][PATCH 1/2] ACPI: Idle Processor PM Improvements Pallipadi, Venkatesh
2006-08-30 19:43 ` Matthew Garrett
2006-08-31 23:13 ` Bjorn Helgaas
2006-09-01 0:30 ` [OLPC-devel] " Jim Gettys
2006-09-01 3:53 ` Len Brown
2006-09-01 4:12 ` Matthew Garrett
2006-09-01 15:51 ` Jordan Crouse
2006-09-01 13:14 ` [OLPC-devel] Re: [RFC][PATCH 1/2] " Carl-Daniel Hailfinger
2006-09-01 21:52 ` Andi Kleen
2006-09-01 22:57 ` Alan Cox
2006-09-04 13:13 ` Pavel Machek
2006-09-04 13:09 ` Pavel Machek
2006-09-05 14:31 ` Jim Gettys
2006-09-06 10:37 ` Pavel Machek
2006-09-06 14:58 ` Jordan Crouse
2006-09-12 9:21 ` Pavel Machek
2006-09-12 18:14 ` Jim Gettys
2006-09-12 18:27 ` Mitch Bradley [this message]
2006-09-12 20:18 ` Jordan Crouse
2006-09-14 9:20 ` Pavel Machek
2006-09-14 9:18 ` Pavel Machek
2006-09-14 11:29 ` Jim Gettys
2006-09-06 15:19 ` [OLPC-devel] Re: [RFC][PATCH 1/2] " Jim Gettys
2006-09-12 9:21 ` Pavel Machek
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=4506FC27.70507@firmworks.com \
--to=wmb@firmworks.com \
--cc=abelay@novell.com \
--cc=arjan@linux.intel.com \
--cc=bjorn.helgaas@hp.com \
--cc=devel@laptop.org \
--cc=jg@laptop.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=pavel@ucw.cz \
--cc=venkatesh.pallipadi@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