On Tue, Mar 31, 2020 at 12:40:23AM +0200, Christian E. Jørgensen wrote:
> Am I correct in assuming that GRUB relies on something like a BIOS for
> support of NVMe devices? I'm running coreboot with GRUB as the payload
> (on amd64 hardware) and GRUB does not seem to detect my NVMe device.
>
> If I u
Am I correct in assuming that GRUB relies on something like a BIOS for
support of NVMe devices? I'm running coreboot with GRUB as the payload
(on amd64 hardware) and GRUB does not seem to detect my NVMe device.
If I use SeaBIOS instead of GRUB as the coreboot payload, then SeaBIOS
detects the NVMe
On 02/23/2018 11:02 PM, Daniel Kiper wrote:
> Applied!
Woohooo \o/. Debian on sparc64 with a working GRUB is getting closer :-).
> FYI, this is last time when I sent commit confirmation.
> If I send one in the future then this will be rather
> exception than rule. So, if you receive my reviewed-b
On Tue, Feb 20, 2018 at 09:01:05PM +0100, Daniel Kiper wrote:
> On Tue, Feb 20, 2018 at 09:57:14AM -0800, Eric Snowberg wrote:
> > Add NVMe support within ofpath.
> >
> > The Open Firmware text representation for a NVMe device contains the
> > Namespace ID. An invali
On Tue, Feb 20, 2018 at 09:57:14AM -0800, Eric Snowberg wrote:
> Add NVMe support within ofpath.
>
> The Open Firmware text representation for a NVMe device contains the
> Namespace ID. An invalid namespace ID is one whose value is zero or whose
> value is greater than the value
Add NVMe support within ofpath.
The Open Firmware text representation for a NVMe device contains the
Namespace ID. An invalid namespace ID is one whose value is zero or whose
value is greater than the value reported by the Number of Namespaces (NN)
field in the Identify Controller data structure
Add nvme support within ofpath
Signed-off-by: Eric Snowberg
---
grub-core/osdep/linux/ofpath.c | 46
1 files changed, 46 insertions(+), 0 deletions(-)
diff --git a/grub-core/osdep/linux/ofpath.c b/grub-core/osdep/linux/ofpath.c
index 0994e08..4c1c95b
