summaryrefslogtreecommitdiff
path: root/config/submodule/grub/nvme/gnulib/module.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/submodule/grub/nvme/gnulib/module.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/submodule/grub/nvme/gnulib/module.cfg')
-rw-r--r--config/submodule/grub/nvme/gnulib/module.cfg3
1 files changed, 3 insertions, 0 deletions
diff --git a/config/submodule/grub/nvme/gnulib/module.cfg b/config/submodule/grub/nvme/gnulib/module.cfg
new file mode 100644
index 00000000..6fd77871
--- /dev/null
+++ b/config/submodule/grub/nvme/gnulib/module.cfg
@@ -0,0 +1,3 @@
+subrepo="git://git.sv.gnu.org/gnulib"
+subrepo_bkup="https://codeberg.org/libreboot/gnulib"
+subhash="9f48fb992a3d7e96610c4ce8be969cff2d61a01b"