summaryrefslogtreecommitdiffstats
path: root/usr.sbin/bsdinstall/partedit/partedit_x86.c
Commit message (Collapse)AuthorAgeFilesLines
* Merge remote-tracking branch 'origin/releng/11.1' into RELENG_2_5Renato Botelho2017-07-031-2/+6
|\
| * bsdinstall: use consistent EFI configuration across platformsemaste2017-06-191-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | MFC r320007: - increase arm64 EFI partition to 200M, as x86 - use EFI_BOOTPART_SIZE and EFI_BOOTPART_PATH macros on x86 - increase ZFS EFI partition to 200M MFC r320008: bsdinstall: correct comment after r320007 PR: 201898 Approved by: re (kib) Relnotes: Yes Sponsored by: The FreeBSD Foundation
* | Revert "Use MBR by default on BIOS systems. An increasing number of ↵Renato Botelho2016-11-181-4/+1
|/ | | | | | motherboards" This reverts commit 30a42c280eec3a4e23e3eab91b7e04cff697d312.
* bsdinstall: increase EFI partition size to 200MBemaste2016-06-231-1/+1
| | | | | | | | | | | | | | | | | A larger EFI file system size will facilitate multi-boot configurations and the installation other EFI applications like firmware update tools. 200MB matches OS X. Note that this changes only the partition size, not the file system that bsdinstall places there. We need to do both, but as the partition size is difficult to adjust later make this change for now so that at least systems installed with FreeBSD 11.0 have a partition layout with room to grow. Reviewed by: allanjude, imp Approved by: re (gjb) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D6935
* Use MBR by default on BIOS systems. An increasing number of motherboardsnwhitehorn2015-01-301-1/+4
| | | | | | | assume that GPT means UEFI boot, resulting in the installation of uninstallable systems. This needs a little more work before MFC, in particular based on disk size (> 2 TB + BIOS + MBR is not workable). That will come soon.
* Only allow ZFS boot on GPT; the MBR ZFS bootblocks cannot be installed usingnwhitehorn2014-10-121-1/+3
| | | | | gpart bootcode as /boot/zfsboot needs to be split into multiple pieces by hand and copied to different areas of the partition.
* Centralize determination of boot firmware (UEFI vs. BIOS/CSM) into anwhitehorn2014-10-121-32/+35
| | | | function x86_bootmethod() and fix deviations from style(9).
* Add ZFS support to the bsdinstall partition editor and sade.nwhitehorn2014-09-131-1/+18
| | | | | Submitted by: Kurt Lidl (original version) MFC after: 6 weeks
* Allow up to 512K for boot code on GPT with BIOS. As pmbr.s says in a comment,nwhitehorn2014-07-111-1/+1
| | | | | | | "545K should be enough for any boot code". This rounds down slightly. Reported by: Matthew Fuller MFC after: 2 weeks
* Finish connecting up installer UEFI support. If the kernel was booted usingnwhitehorn2014-04-271-5/+5
| | | | | EFI, set up the disks for an EFI system. If booted from BIOS/CSM, set up for BIOS.
* Add EFI support to the installer. This requires that the kernel providenwhitehorn2014-04-261-9/+55
| | | | | | | | | | | | a sysctl to determine what firmware is in use. This sysctl does not exist yet, so the following blocks are in front of the wheels: - I've provisionally called this "hw.platform" after the equivalent thing on PPC - The logic to check the sysctl is short-circuited to always choose BIOS. There's a comment in the top of the file about how to turn this off. If IA64 acquired a boot1.efifat-like thing (probably with very few modifications), the same code could be adapted there.
* Import bsdinstall. This is meant to be (eventually in conjunction withnwhitehorn2011-02-181-0/+79
pc-sysinstall) a replacement for sysinstall in the 9.0 release and beyond. Currently supported platforms are sparc64, pc98, i386, amd64, powerpc, and powerpc64. Integration into the build system will occur in the coming weeks. Merging with pc-sysinstall will use this code as a frontend, while temporarily retaining the interactive partition editor here. This work will be done in parallel with improvements on this code and release integration. Thanks to all who have provided testing and comments!
OpenPOWER on IntegriCloud