Re:Pre-Prod HoneyComb LX2K 16-Core Mini ITX Arm Workstation ...
by zamadatix on Saturday July 06, 2019 @06:46PM
(#20372497)
Between the official boot firmware not being UEFI compatible and not being onboard it means you have to create a custom installation image and apply it to the disk rather than grabbing a generic installer and going. Also you need to do this for each bootable media you wish to create rather than once (and update each).
[ Parent
| on HN ]
Re:Pre-Prod HoneyComb LX2K 16-Core Mini ITX Arm Workstation ...
by monocasa on Saturday July 06, 2019 @09:51PM
(#20373142)
Philosophically, I actually like the RPi approach (ie. a simple image with device tree) a lot more than ACPI/UEFI. ACPI involves a whole super privileged virtual machine with byte code from god knows where, whereas device tree gives more or less complete control over to the kernel image (sure PSCI is a thing, but that's a lot more defined WRT boundaries to me than ACPI).
Basically an ACPI system is a lot easier to bootstrap because you don't need to support all of the little subcomponents of the board explicitly, but once you supprt devoce tree, you support the board in a much more complete and meaningful way, and it's truly your kernel running the show.