4 ms·
AArch64 Boards and Perception
- zokier 6y agoI'm glad there is finally some standardization. The previous "Standards in Arm space" articles[1] are good illustration why this was needed. The LBBR spec seems nice, the article does mention that its for some hyperscale datacenter stuff but to me it seems like it could work well for sbcs too, but I don't know if I'm missing something. [1] https://marcin.juszkiewicz.com.pl/2020/10/12/standards-in-arm-space-part-i/ https://marcin.juszkiewicz.com.pl/2020/10/12/standards-in-ar...
- tyingq 6y agoI think the Rpi is perhaps the best example of the craziness. It's the GPU that actually controls the first few stages of booting.
- monocasa 6y agoSort of... There's two main architectures in the VideoCore. The QPUs are different than the main VideoCore, and the main videocore (which is also what runs the boot code) isn't really the GPU. For a long time neither were documented so people just sort of assumed they were the same thing.
- tyingq 6y agoWell, yes, but changing how the initial boot code works still means changes in the thing we call the "videocore firmware", right?
- monocasa 6y agoYeah, but lots of SoCs have special boot and SoC management cores with a different ISA. The Tegra X1 in the switch uses an ARM7, CortexMs are in vogue in a lot of designs, AMD and Intel have the PSP and ME respectively, and even the SiFive SoCs have a E core that boots the main core complex of U cores. In none of these cases (including the RPi) is this core the GPU.
- tyingq 6y agoAppreciate the clarification, but your paragraph above is exactly what I was getting at. Roughly that "the article is right...ARM booting on dev boards is a crazy world". As crappy as legacy BIOS and UEFI is, booting on x86/x64 is more standardized, despite things like PSP and ME.
- monocasa 6y agoThe point I'm getting at is that sub cores to boot a main core isn't a crazy world, and you're stuck with the same thing on almost all x86 designs as well. It's not where you should be looking at if you want to make the ARM booting space any better.
- deleted 6y ago[deleted]
- egil 6y agoImho the most important part of the x86 standardization is the IBM pc platform. Arm boards doesn't have an equivalent platform to standardize on, so everybody does their own thing.
- als0 6y agoBSA and BBR specs from Arm fix that. They also have a certification program https://developer.arm.com/architectures/system-architectures/arm-systemready https://developer.arm.com/architectures/system-architectures...
- monocasa 6y agoI find it unfortunate though that quite a few of the requirements for those standards is "buy more ARM IP blocks" rather than asking defining blocks that can be implemented by others. It feels like a self defeating cash grab.
- colejohnson66 6y ago
- phire 6y agoThe original raspberry pi documentation did kind of give people the wrong idea. The whole block with the VPUs, ISPs, mpeg4 codec and 3d pipeline could be described as a "GPU", and the gpu firmware is the firmware that runs it. Modern Desktop CPUs also contain a management/security cpu core which runs everything. And that correctly described as GPU firmware, though its commonly called vBIOS. But the VPUs are so much more than a management processor for the 3d pipeline. They have a huge vector array and can do software encoded/decoding of video up to 480p MPEG2 (videocore 4 added hardware h264 codecs that could do 1080p) I like to think of the VPUs as multimedia co-processor cores. The ipod video used the VideoCore 2 as it's gpu. It had an arm SoC as it's main cpu and a separate videocore chip. The videocore handled all display output and video decoding. It has no 3d pipeline, but they wrote an software opengl implementation which runs on the VPU to implement the games. There are actually a few set-top boxes (and maybe a cellphone) which just just the videocore VPUs the main cpu. It's flexible enough for that.
- StillBored 6y agoIn the end none of that really matters, as evidenced by the PFTF* bringing it into compliance with the relevant standards. The UEFI/ACPI stack is sufficiently abstract that it has allowed x86 to evolve and scale from little embedded devices like the atomic pi, to HP superdomes using the same basic OS for a couple decades. So the low level boot mechanisms on Arm SBC's don't really matter because they are just used to boot a SBC specific UEFI image. The UEFI image then provides a standard mechanism for booting your OS of choice. The fact its taken 15+ years for the arm ecosystem to notice this, might be an interesting thing to study. * https://github.com/pftf https://github.com/pftf (SBBR-compliant (UEFI+ACPI) AArch64 firmware for the Raspberry Pi)
- monocasa 6y agoIt's more complex than that. One of the major reasons why there isn't a universal ARM standard of booting is that once you've gained control of execution, now you just have a bunch more per SoC work that needs to happen in the kernel compared to x86. ARM is simply far far far more heterogeneous on much deeper levels than x86-pc. "Well, ARM just should be more standardized on it's hardware interface then", is a common refrain I hear then, but that's just nerfing a major benefit of ARM in the first place. It's a strategic advantage that it didn't have it's own set of legacy cruft or an extremely heavyweight interface to everything like PCI is.
- StillBored 6y agoWell neither did x86 back in the < 486 days, but ACPI, PCI and USB were developed in response to exploding complexity of systems that needed to have their machines described in config.sys and autoexec.bat files with matching user set PIO/MMIO/DMA/IRQ jumpers set. So, at this point arm machines have shown that everyone doing their own thing just creates giant piles of DT cruft and the associated mess in the kernel as each SoC designer thinks they have the one true way to do interrupts, or whatever other portion of the SoC one chooses to look at. Hence the standards dictate the use of arm compatible GIC's and the like. Its also a large part of why many IoT like devices get updates for a year or two, then get dropped as the maintenance burden of all these custom devices/etc gets too great. Also, much of the work (like pinmuxing/clock mgmt/etc) is completely redundant if the firmware configures it. That is is part of the abstraction. edit: At this point, time to market is a more important metric than saving a few thousand transistors failing to provide standard machine autodetection/etc logic.
- pabs3 6y agoThere is a project to create an open source version of the proprietary GPU firmware that boots into the ARM processor: https://github.com/librerpi/rpi-open-firmware https://github.com/librerpi/rpi-open-firmware
- monocasa 6y ago> I heard several rumours about why ACPI. Someone said that ACPI was forced by Microsoft. In reality it was decision taken by all major distros and Microsoft. Microsoft went out of their way looking for methods to make ACPI not work well with Linux. And Microsoft viewed ACPI as their spec that they didn't want Linux "getting for free". http://antitrust.slated.org/www.iowaconsumercase.org/011607/3000/PX03020.pdf http://antitrust.slated.org/www.iowaconsumercase.org/011607/... And it's not like the distros had a choice. ACPI is the only way to, for instance, enumerate other cores than the boot processor on x86. Features as simple as SMP requires ACPI on x86.
- danhor 6y agoI'm pretty sure it's referring to the use of ACPI on AArch64, which came way later and was (probably) primarily implemented to run linux.
- CountSessine 6y agoThe real energy behind ACPI was Intel, not Microsoft - Intel ironically wanted an instruction-set neutral firmware glue given that they were splitting their efforts between Itanium and x86. And Intel is pretty pro-linux. There's much worse in UEFI - UEFI, while a lot better than the awful real-mode boot process that came before it, actually requires building Windows PE executables and dlls, even for a linux system. And the sky didn't fall.
- anyfoo 6y agoFully agreed on the horribleness of real-mode (BIOS) boot, but for others it might be interesting to know why: It was made to boot a relatively simple 16bit computer with a pretty limited configuration space ("do you have two floppy drives or one[1], and do you have the monochrome MDA graphics adapter or the unprofessional 4-color CGA one?"). And then continued to be bolted on, not only by the PCs BIOS but also by the possibility to have secondary boot ROMs on extension cards, over 30 years later. [1] Call it paraphrasing, as I don't remember right now whether you could even boot from the 2nd floppy drive.
- haerwu 6y ago
- ryukafalz 6y agoI'd like to see phones get to that level of standardization too. Maybe wishful thinking. But imagine being able to grab a generic GNU/Linux image and slap it on your phone no matter what that phone is! I suppose the only phone manufacturers that are at all likely to do something like this are companies like Purism and Pine64.
- pabs3 6y agoFor phones there is the bigger problem of SoC and device vendors not mainlining Linux drivers for the hardware they have produced. This is less common with SoC vendors but I think there are still some problematic ones, and of course all the ARM GPU drivers are non-vendor ones created using reverse engineering (except the RPi one).