From: "Li, Aubrey" <aubrey.li@linux.intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
"alan@linux.intel.com" <alan@linux.intel.com>,
linux-kernel@vger.kernel.org, Len.Brown@intel.com,
Adam Williamson <awilliam@redhat.com>
Subject: Re: [patch] x86: Introduce BOOT_EFI and BOOT_CF9 into the reboot sequence loop
Date: Mon, 03 Mar 2014 06:45:15 +0800 [thread overview]
Message-ID: <5313B47B.6020402@linux.intel.com> (raw)
In-Reply-To: <20140302222654.GA17838@srcf.ucam.org>
On 2014/3/3 6:26, Matthew Garrett wrote:
> On Mon, Mar 03, 2014 at 06:13:47AM +0800, Li, Aubrey wrote:
>
>> If you have a system can't be rebooted by all of the known methods, we
>> have to figure out how to make reboot work and add the new methods.
>
> The only methods used by Windows are the keyboard controller, the ACPI
> registers and (according to your results) the EFI reboot mechanism. If
> none of those work under Linux but Windows is able to reboot
> successfully then we don't need to add new methods, we need to find out
> why the existing methods don't work.
>
One example in my hand is, 32bit windows calls 32bit EFI firware, so
reboot works. However, I installed 64bit linux on this 32bit EFI
machine, so none of ACPI/KBD/EFI works.
Other cases even if we figured out why ACPI/KBD/EFI don't work, we still
have to make our change in the linux kernel, because we can't change
firmware.
So, if you are still suggesting we add EFI only, please let me know your
plan about adding dmidecode table and if it's acceptable to add new
tables, I have three waiting: ASUS-T100, Dell Venue 8 Pro, and Dell
Venue 11 Pro.
Or if you don't want to keep adding the dmidecode, please let me know
your plan so that I don't want to keep driving this patch.
Thanks,
-Aubrey
next prev parent reply other threads:[~2014-03-02 22:45 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 4:11 [patch] x86: Introduce BOOT_EFI and BOOT_CF9 into the reboot sequence loop Li, Aubrey
2014-02-28 4:56 ` Matthew Garrett
2014-02-28 5:22 ` Li, Aubrey
2014-02-28 5:56 ` Matthew Garrett
2014-02-28 6:07 ` Li, Aubrey
2014-02-28 6:12 ` Matthew Garrett
2014-02-28 6:20 ` Li, Aubrey
2014-02-28 6:23 ` Matthew Garrett
2014-02-28 6:39 ` Li, Aubrey
2014-02-28 6:44 ` Matthew Garrett
2014-02-28 6:54 ` Li, Aubrey
2014-02-28 17:47 ` H. Peter Anvin
2014-02-28 22:11 ` Li, Aubrey
2014-02-28 22:16 ` Adam Williamson
2014-03-01 17:10 ` Li, Aubrey
2014-03-01 17:22 ` Matthew Garrett
2014-03-01 17:31 ` Li, Aubrey
2014-03-01 18:19 ` Matthew Garrett
2014-03-01 19:01 ` Matthew Garrett
2014-03-02 0:15 ` Li, Aubrey
2014-03-01 20:06 ` H. Peter Anvin
2014-03-01 20:21 ` Matthew Garrett
2014-03-01 20:26 ` H. Peter Anvin
2014-03-02 0:26 ` Li, Aubrey
2014-03-02 0:33 ` H. Peter Anvin
2014-03-02 1:47 ` Li, Aubrey
2014-03-02 2:07 ` H. Peter Anvin
2014-03-02 2:20 ` Li, Aubrey
2014-03-02 2:23 ` Matthew Garrett
2014-03-02 2:35 ` H. Peter Anvin
2014-03-02 10:39 ` Li, Aubrey
2014-03-02 16:52 ` H. Peter Anvin
2014-03-02 22:13 ` Li, Aubrey
2014-03-02 22:26 ` Matthew Garrett
2014-03-02 22:45 ` Li, Aubrey [this message]
2014-03-02 23:11 ` Matthew Garrett
2014-03-02 23:23 ` Li, Aubrey
2014-03-03 0:07 ` Matthew Garrett
2014-03-03 0:18 ` H. Peter Anvin
2014-03-03 1:36 ` Li, Aubrey
2014-03-03 1:47 ` H. Peter Anvin
2014-03-03 1:49 ` Li, Aubrey
2014-03-03 22:11 ` Li, Aubrey
2014-03-02 23:57 ` H. Peter Anvin
2014-03-05 23:39 ` [tip:x86/reboot] x86, reboot: Add EFI and CF9 reboot methods into the default list tip-bot for Li, Aubrey
2014-03-05 23:45 ` [tip:x86/reboot] x86, reboot: Only use CF9_COND automatically, not CF9 tip-bot for H. Peter Anvin
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=5313B47B.6020402@linux.intel.com \
--to=aubrey.li@linux.intel.com \
--cc=Len.Brown@intel.com \
--cc=alan@linux.intel.com \
--cc=awilliam@redhat.com \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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