x86_64 EFI boot support
cover x86_64 EFI boot support
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
Can this patchset be merged into mainline kernel? This patchset has been in -mm tree from 2.6.23-rc2-mm2 on. Andrew Moton has suggested it to be merged into 2.6.24 during early merge window of 2.6.24. It was not merged into mainline because the 32-bit boot protocol has not been done.
But now, the 32-bit boot protocol has been merged into mainline. So can this patchset be merged into mainline kernel now?
Best Regards,
Huang Ying
Quoted 8 lines · Ying
Can this patchset be merged into mainline kernel? This patchset has been in -mm tree from 2.6.23-rc2-mm2 on. Andrew Moton has suggested it to be merged into 2.6.24 during early merge window of 2.6.24. It was not merged into mainline because the 32-bit boot protocol has not been done.
But now, the 32-bit boot protocol has been merged into mainline. So can this patchset be merged into mainline kernel now?
I stopped paying attention, sorry. Have all the outstanding issues been addressed?
Quoted 2 lines · Andrew Morton
I stopped paying attention, sorry. Have all the outstanding issues been addressed?
The "EFI boot" patchset looks fairly unobtrusive to me. One objection: the VIDEO_TYPE_ numbers appear split up into groups; and the EFI one probably should be 0x70 instead of 0x24.
Other than that, I just need to verify it doesn't break anything.
"EFI runtime" I have not had time to review yet.
-hpa
Quoted 5 lines
From: Andrew Morton [mailto:[email protected]]
Quoted 1 line · Ying
Can this patchset be merged into mainline kernel? This patchset has
been
Quoted 1 line
Quoted 1 line
in -mm tree from 2.6.23-rc2-mm2 on. Andrew Moton has suggested it to
be
Quoted 2 lines
Quoted 2 lines
merged into 2.6.24 during early merge window of 2.6.24. It was not merged into mainline because the 32-bit boot protocol has not been
done.
Quoted 2 lines
Quoted 2 lines
But now, the 32-bit boot protocol has been merged into mainline. So
can
Quoted 4 lines
Quoted 2 lines
this patchset be merged into mainline kernel now?
I stopped paying attention, sorry. Have all the outstanding issues
been
Quoted 1 line
addressed?
That's all right. I think there is no big issue with this patchset, just a framebuffer driver and the document.
Best Regards,
Huang Ying
Quoted 4 lines
From: H. Peter Anvin [mailto:[email protected]]
The "EFI boot" patchset looks fairly unobtrusive to me. One objection:
theVIDEO_TYPE_numbers appear split up into groups; and the EFI one probably should be0x70instead of0x24.
Should I change this and resend the patchset? Or you modify it before merging?
Best Regards,
Huang Ying
Quoted 8 lines · Ying
Quoted 4 lines
From: H. Peter Anvin [mailto:[email protected]]
The "EFI boot" patchset looks fairly unobtrusive to me. One objection:
theVIDEO_TYPE_numbers appear split up into groups; and the EFI one probably should be0x70instead of0x24.Should I change this and resend the patchset? Or you modify it before merging?
I'd be easier if you could change and resend.
-hpa