From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
x86@kernel.org, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]X86:reboot.c Add some dmi entries to pci_reboot_dmi_table.
Date: Thu, 3 Jun 2010 02:37:58 +0100 [thread overview]
Message-ID: <20100603013758.GA18755@srcf.ucam.org> (raw)
In-Reply-To: <4C06F6EA.6090701@gmail.com>
On Wed, Jun 02, 2010 at 05:27:22PM -0700, Justin P. Mattock wrote:
> On 06/02/2010 05:20 PM, Robert Hancock wrote:
>> #include<unistd.h>
>>
>> int main() {
>> iopl(3);
>> outb(2, 0xcf9);
>> sleep(1);
>> outb(6, 0xcf9);
>> return 0;
>> }
>>
>> That's basically what PCI reboot does.
>
> the above code reboot's the machine as it should..
> I can look at that(need to take a break first though)
> and see..
That's pretty infuriating. The ACPI-provided definition doesn't work,
and there's no ACPI mechanism for expressing the more complex cf9
behaviour. Windows doesn't appear to special case this, so we're
probably left trying to figure out why the keyboard controller method
doesn't work. Sigh.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-06-03 1:38 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 6:26 [PATCH]X86:reboot.c Add some dmi entries to pci_reboot_dmi_table Justin P. Mattock
2010-05-31 17:07 ` Matthew Garrett
2010-05-31 17:46 ` Justin P. Mattock
2010-06-01 19:00 ` Matthew Garrett
2010-06-01 19:14 ` Justin P. Mattock
2010-06-01 19:21 ` Matthew Garrett
2010-06-01 20:06 ` Justin P. Mattock
2010-06-01 20:07 ` Matthew Garrett
2010-06-01 20:17 ` Justin P. Mattock
2010-06-01 20:21 ` Matthew Garrett
2010-06-01 20:31 ` Justin P. Mattock
2010-06-01 20:33 ` Matthew Garrett
2010-06-01 20:51 ` Justin P. Mattock
2010-06-01 21:12 ` Matthew Garrett
2010-06-01 21:26 ` Justin P. Mattock
2010-06-01 21:29 ` Matthew Garrett
2010-06-01 21:43 ` Justin P. Mattock
2010-06-01 21:48 ` Matthew Garrett
2010-06-01 21:56 ` Justin P. Mattock
2010-06-02 12:08 ` Alan Cox
2010-06-02 13:32 ` Justin P. Mattock
2010-06-02 5:11 ` Robert Hancock
2010-06-02 6:01 ` Justin P. Mattock
2010-06-02 23:18 ` Robert Hancock
2010-06-02 23:43 ` Justin P. Mattock
2010-06-02 23:45 ` Robert Hancock
2010-06-03 0:05 ` Justin P. Mattock
2010-06-03 0:20 ` Robert Hancock
2010-06-03 0:27 ` Justin P. Mattock
2010-06-03 0:34 ` Robert Hancock
2010-06-03 0:51 ` Justin P. Mattock
2010-06-03 1:37 ` Matthew Garrett [this message]
2010-06-03 1:46 ` Justin P. Mattock
2010-06-03 1:47 ` Robert Hancock
2010-06-03 1:56 ` Matthew Garrett
2010-06-03 2:06 ` Justin P. Mattock
2010-06-03 2:06 ` Robert Hancock
2010-06-03 2:00 ` Justin P. Mattock
2010-06-03 2:05 ` Robert Hancock
2010-06-03 2:16 ` Justin P. Mattock
2010-06-03 2:15 ` Justin P. Mattock
2010-06-03 2:18 ` Matthew Garrett
2010-06-03 2:22 ` Justin P. Mattock
2010-06-03 9:54 ` Alan Cox
2010-06-03 10:11 ` Justin P. Mattock
2010-06-03 11:46 ` Matthew Garrett
2010-06-03 14:43 ` Robert Hancock
2010-06-03 2:19 ` Justin P. Mattock
2010-07-31 19:00 ` Justin Mattock
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=20100603013758.GA18755@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=hancockrwd@gmail.com \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).