lbmk/config/grub/nvme/target.cfg

tree="nvme"
rev="8719cc2040368d43ab2de0b6e1b850b2c9cfc5b7"
bootstrapargs="--gnulib-srcdir=gnulib/ --no-git"
autoconfargs="--with-platform=coreboot --disable-werror"
makeargs="FS_PAYLOAD_MODULES=\"\""
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> 2024-06-11 23:58:22 +00:00			`tree="nvme"`
			`rev="8719cc2040368d43ab2de0b6e1b850b2c9cfc5b7"`
			`bootstrapargs="--gnulib-srcdir=gnulib/ --no-git"`
			`autoconfargs="--with-platform=coreboot --disable-werror"`
			`makeargs="FS_PAYLOAD_MODULES=\"\""`