Hey I’m looking at grabbing a Jupiter to run my home server which does just basic file sharing and a couple other simple things. However, from what I can tell the Jupiter doesn’t use UEFI and I have a SAS controller that initializes with its UEFI Expansion ROM, I’m guessing there’s really no way to use it on the Jupiter?
Probably a silly question but does this UEFI Expansion ROM (Legacy Option ROM image) contain a “RISCV32 UEFI driver” or a “RISCV64 UEFI driver” ?
That might be a safer starting point, than to find out later on that your SAS controller only supports IA32/x64/Itanium Processor Family.
I’m sure it doesn’t have any RISC-V specific stuff, it predates any physical RISC-V hardware lol. But AFAIK UEFI Expansion ROMs are usually in EFI Bytecode no?
The Jupiter doesn’t have EFI firmware, so it can’t load EFI expansion ROMs from devices. It is only able to boot from devices which U-Boot has native drivers for.
But this only affects boot! If you boot from a supported device - e.g. NVMe, SD, eMMC - then your SAS controller should work fine after it gets initialized by the Linux kernel.
You will probably need to build your own kernel to add the SAS controller driver module.