diff options
| author | Daniel Golle <daniel@makrotopia.org> | 2022-07-26 10:17:07 +0200 |
|---|---|---|
| committer | Hauke Mehrtens <hauke@hauke-m.de> | 2022-10-23 13:20:32 +0200 |
| commit | 08969f61b0ef622f89f96e28a9a094ac8c0e8245 (patch) | |
| tree | aff9538485283416a28c6819ce7ab8f0e6116853 /tools/cbootimage | |
| parent | c1c85629b98374639baa7e0d6033bfb068d6d4d8 (diff) | |
| download | upstream-08969f61b0ef622f89f96e28a9a094ac8c0e8245.tar.gz upstream-08969f61b0ef622f89f96e28a9a094ac8c0e8245.tar.bz2 upstream-08969f61b0ef622f89f96e28a9a094ac8c0e8245.zip | |
kernel: add kmod-nvme package
Add driver for NVM Express block devices, ie. PCIe connected SSDs.
Targets which allow booting from NVMe (x86, maybe some mvebu boards come
to mind) should have it built-in, so rootfs can be mounted from there.
For targets without NVMe support in bootloader or BIOS/firmware it's
sufficient to provide the kernel module package.
On targets having the NVMe driver built-in the resulting kmod package
is an empty dummy. In any case, depending on or installing kmod-nvme
results in driver support being available (either because it was already
built-in or because the relevant kernel modules are added and loaded).
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
(cherry picked from commit dbe53352e38d20bb5245158b19d4ff810c209548)
Diffstat (limited to 'tools/cbootimage')
0 files changed, 0 insertions, 0 deletions