summaryrefslogtreecommitdiff
path: root/config/coreboot/t1650_12mb/target.cfg
diff options
context:
space:
mode:
authorLeah Rowe <leah@libreboot.org>2024-06-12 00:58:22 +0100
committerLeah Rowe <leah@libreboot.org>2024-06-12 00:58:22 +0100
commit0b37653ab908093a108cfe3cbcb4e8d378428d26 (patch)
tree4fd3b33c728b8c8aed5b6b3df7867c02b8887b71 /config/coreboot/t1650_12mb/target.cfg
parent1952db55540606b2fb00ddd4be9e358dbc99ef8b (diff)
grub: only enable nvme if needed on a board
remove nvme support from the "default" grub tree now there are three trees: * default: no xhci or nvme patches * nvme: contains nvme support * xhci: contains xhci and nvme support this is in case a bug like lbmk issue #216 ever occurs again, as referenced before during lbmk audit 5 there is no indication that the nvme patch causes any issues, but after previous experience i want to be sure Signed-off-by: Leah Rowe <leah@libreboot.org>
Diffstat (limited to 'config/coreboot/t1650_12mb/target.cfg')
-rw-r--r--config/coreboot/t1650_12mb/target.cfg1
1 files changed, 1 insertions, 0 deletions
diff --git a/config/coreboot/t1650_12mb/target.cfg b/config/coreboot/t1650_12mb/target.cfg
index ebf3fca1..a2b3d31f 100644
--- a/config/coreboot/t1650_12mb/target.cfg
+++ b/config/coreboot/t1650_12mb/target.cfg
@@ -4,3 +4,4 @@ payload_seabios="y"
payload_seabios_withgrub="y"
payload_memtest="y"
grub_scan_disk="nvme ahci"
+grubtree="nvme"