summaryrefslogtreecommitdiff
path: root/config/coreboot/e6420_10mb/target.cfg
diff options
context:
space:
mode:
authorLeah Rowe <leah@libreboot.org>2024-05-27 20:16:49 +0100
committerLeah Rowe <leah@libreboot.org>2024-05-27 20:36:58 +0100
commite1883f1d5a1722a2ab088c0dd4906bbdf860c003 (patch)
treeb849557be8e7161aeffcbd353e3676e44dfbc7a3 /config/coreboot/e6420_10mb/target.cfg
parentc94cecd83751d2df26314a90852f7df306256fb0 (diff)
grub.cfg: use grub_scan_disk to set boot order
Previously, grub_scan_disk could set ata, ahci or "both", which would make both be tried (ahci first). This worked when we only dealt with ata and ahci devices, but now we support nvme devices so the logic is inherently flawed. Instead, use grub_scan_disk to store the boot order, e.g.: grub_scan_disk="ahci nvme ata" grub_scan_disk="nvme ata" In the first example, it would make GRUB scan ahci first, then nvme and then ata. In the secontd example, it would make GRUB scan nvme first, and then ata. If "both" is set, or anything other than ahci/ata/nvme, grub_scan_disk is now changed to "nvme ahci ata". Actual grub_scan_disk entries in target.cfg files will now be modified, to match each machine. Signed-off-by: Leah Rowe <leah@libreboot.org>
Diffstat (limited to 'config/coreboot/e6420_10mb/target.cfg')
0 files changed, 0 insertions, 0 deletions