Revert my accidental changes to this file: r45769, r45770, r45771

This commit is contained in:
Ed Maste 2014-10-10 20:45:47 +00:00
parent 509829689f
commit 31d3afdca6
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=45774

View file

@ -553,6 +553,77 @@
</help>
</project>
<project cat='kern'>
<title>UEFI Boot</title>
<contact>
<person>
<name>
<given>Ed</given>
<common>Maste</common>
</name>
<email>emaste@FreeBSD.org</email>
</person>
<person>
<name>
<given>Nathan</given>
<common>Whitehorn</common>
</name>
<email>nwhitehorn@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="https://wiki.freebsd.org/UEFI">&os; UEFI wiki page</url>
<url href="http://www.freebsd.org/snapshots/">&os;&nbsp;snapshots</url>
</links>
<body>
<p>The Unified Extensible Firmware Interface (UEFI) provides
boot- and run-time services for x86 and other computers. For
the x86 architecture it replaces the legacy BIOS. This
project will adapt the &os; loader and kernel boot process for
compatibility with UEFI firmware, found on contemporary
servers, desktops, and laptops.</p>
<p>Ed and Nathan completed a number of integration tasks over
the past three months. Nathan added a first-stage loader,
boot1.efi, to support chain-loading the rest of the system
from a UFS filesystem. This allows the UEFI boot process to
proceed in a similar fashion as with BIOS boot. Nathan also
added UEFI support to the &os; installer and release image
creation script.</p>
<p>The EFI framebuffer requires the <tt>vt(4)</tt> system
console &mdash; a framebuffer driver is not implemented for
the legacy <tt>syscons(4)</tt> console. Ed added automatic
<tt>vt(4)</tt> selection to the UEFI boot path.</p>
<p>Snapshots are now built as dual-mode images, and should boot
via both BIOS and UEFI. Our plan is to merge the UEFI and
<tt>vt(4)</tt> work to stable/10 to appear in &os;
10.1-RELEASE.</p>
</body>
<sponsor>The &os; Foundation</sponsor>
<help>
<task>Document manual installation, including dual-boot
configurations.</task>
<task>Implement boot1.efi for ZFS file systems.</task>
<task>Add support for UEFI variables stored in non-volatile
memory (NVRAM).</task>
<task>Debug boot failures with certain UEFI firmware
implementations.</task>
<task>Support secure boot.</task>
</help>
</project>
<project cat='team'>
<title>&os; Core Team</title>
@ -1583,66 +1654,4 @@
</help>
</project>
<project cat='kern'>
<title>UEFI Boot</title>
<contact>
<person>
<name>
<given>Ed</given>
<common>Maste</common>
</name>
<email>emaste@FreeBSD.org</email>
</person>
<person>
<name>
<given>Nathan</given>
<common>Whitehorn</common>
</name>
<email>nwhitehorn@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="https://wiki.freebsd.org/UEFI">&os; UEFI wiki page</url>
<url href="http://www.freebsd.org/snapshots/">&os;&nbsp;snapshots</url>
</links>
<body>
<p>The Unified Extensible Firmware Interface (UEFI) provides
boot- and run-time services for x86 and other computers. For
the x86 architecture it replaces the legacy BIOS. This
project will adapt the &os; loader and kernel boot process for
compatibility with UEFI firmware, found on contemporary
servers, desktops, and laptops.</p>
<p>Over the last three months Ed and others refined the existing
UEFI support, and merged it to the stable/10 branch for the
upcoming FreeBSD 10.1 release.</p>
<p>To avoid the risk of a regression, the standard FreeBSD 10.1
install images continue to use the existing partitioning scheme
and support only legacy BIOS boot. Separate UEFI-enabled
installer images will be included with 10.1.</p>
<sponsor>The &os; Foundation</sponsor>
<help>
<task>Document manual installation, including dual-boot
configurations.</task>
<task>Implement boot1.efi for ZFS file systems.</task>
<task>Add support for UEFI variables stored in non-volatile
memory (NVRAM).</task>
<task>Debug boot failures with certain UEFI firmware
implementations.</task>
<task>Support secure boot.</task>
</help>
</body>
</project>
</report>