From: "Huang, Ying" <ying.huang@intel.com>
To: akpm@linux-foundation.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Andi Kleen <ak@suse.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Chandramouli Narayanan <mouli@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Antonino A. Daplas" <adaplas@pol.net>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/2 -v2 resend] x86_64 EFI boot support
Date: Wed, 24 Oct 2007 17:32:22 +0800 [thread overview]
Message-ID: <1193218342.23935.147.camel@caritas-dev.intel.com> (raw)
This patch set has been dropped because the 32-bit boot protocol is
not ready. Now, the 32-bit boot protocol has been merged, so I resend
this patch set.
Can this patch set and 32-bit boot protocol document patch catch up
with the merge window of 2.6.24?
Following sets of patches add EFI/UEFI (Unified Extensible Firmware
Interface) boot support to x86_64 architecture.
The patches have been tested against 2.6.24-rc1 kernel on Intel
platforms with EFI1.10 and UEFI2.0 firmware. With this set of patches
applied, the 64 bit and 32 bit x86 kernel can be booted on x86_64
machine with UEFI64 firmware.
Because the EFI memory map is converted to E820 map in bootloader, now
the only needed code for booting Linux kernel on x86_64 UEFI platform
is the framebuffer driver.
UEFI specification can be found here: http://www.uefi.org
For booting the UEFI x86_64 enabled kernel, the machine with EFI/UEFI
firmware and the support of bootloader is required. Detailed usage
guide can be found in Documentation/x86_64/uefi.txt, which is added in
the patch: EFI boot document
v2:
- The include files of efifb.c is cleaned up.
- Make CONFIG_FB_EFI not depend on CONFIG_EFI.
Best Regards,
Huang Ying
next reply other threads:[~2007-10-24 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 9:32 Huang, Ying [this message]
2007-10-31 1:21 ` [PATCH 0/2 -v2 resend] x86_64 EFI boot support Huang, Ying
2007-10-31 19:59 ` Andrew Morton
2007-10-31 20:09 ` H. Peter Anvin
2007-11-02 1:02 ` Huang, Ying
2007-11-02 1:25 ` H. Peter Anvin
2007-11-02 1:01 ` Huang, Ying
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=1193218342.23935.147.camel@caritas-dev.intel.com \
--to=ying.huang@intel.com \
--cc=adaplas@pol.net \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mouli@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.