04-20-2024, 08:09 AM
Lack of UEFI is one of the main reasons I won't buy anymore ARM boards for general purpose computing, like wherever I'd use a PC, because making it do something it wasn't designed to do requires systems engineering. Without UEFI, you hope the people producing the device do it for you, but they still won't do it for too long.
UEFI is supported on ARM, is available in u-boot, and could be used on embedded systems right away. Distros would need to deal with an arm board that acted more like a PC, but it means less work for them in the long run. The new standards do UEFI with DeviceTree, the latter is undeniably crappier than ACPI, but clearly producers of arm boards aren't capable of doing ACPI, they like pushing as much work as possible to device sellers, distros, and end users. In their defense, it might raise the cost too much, but baby steps...
Even still, I'd buy boards right away if I didn't have to engage in custom systems engineering constantly.
I want an SystemReady IR certified board, that follows the EBBR boot standard. In fact I want one right now, for an embedded project.
UEFI is supported on ARM, is available in u-boot, and could be used on embedded systems right away. Distros would need to deal with an arm board that acted more like a PC, but it means less work for them in the long run. The new standards do UEFI with DeviceTree, the latter is undeniably crappier than ACPI, but clearly producers of arm boards aren't capable of doing ACPI, they like pushing as much work as possible to device sellers, distros, and end users. In their defense, it might raise the cost too much, but baby steps...
Even still, I'd buy boards right away if I didn't have to engage in custom systems engineering constantly.
I want an SystemReady IR certified board, that follows the EBBR boot standard. In fact I want one right now, for an embedded project.