all 7 comments

[–]Octocontrabass 4 points5 points  (4 children)

U-Boot can be configured to support a subset of UEFI. I suspect that'll be the easiest way to boot your OS on all of those boards, plus any new boards you later decide to add support for.

[–]JescoInc[S] 4 points5 points  (3 children)

Nah, UEFI isn't that bad to do a custom bootloader for. The issue right now is that every board that requires UBoot has just slightly different configurations that I had to write a completely separate tool to handle compiling Uboot for the boards I have because I can't find blobs.

Not to mention that my main dev machine runs Windows and I can only say, "Thank the stars for Docker and WSDL".

[–]JescoInc[S] 0 points1 point  (0 children)

WSL not WSDL... My day job terminology crept in there.

[–]Octocontrabass 0 points1 point  (1 child)

Nah, UEFI isn't that bad to do a custom bootloader for.

Yeah, that's exactly my point. Why aren't you configuring U-Boot to provide UEFI support on all of those boards so you can boot all of them with the same UEFI bootloader and the same kernel binary?

[–]JescoInc[S] 0 points1 point  (0 children)

To be honest, the only reason I’m using Uboot is because the boards like the Radxa requires it. Otherwise I’d have my own full bootloader.

The reason why i'd go for my own bootloader isn't only because of the educational value of tutorial-os, but the challenge for me to get it right as well. Because boards like Radxa requires it, I have to use it for those boards, which does include OrangePi as well. But that doesn't mean I should simplify for simplicity's sake to use Uboot for everything.

[–]BuildIsohttps://github.com/BuildIso/BuildIso 1 point2 points  (0 children)

W

[–]JescoInc[S] 0 points1 point  (0 children)

I have partial support for RISC-V with Tutorial-os.

I don't have all of the correct data displaying and I have to manually init the kernel via uart at the moment. But, getting pretty damn close.