04-11-2023, 01:01 AM
(04-10-2023, 04:13 AM)CounterPillow Wrote:(04-10-2023, 01:24 AM)balbes150 Wrote:(04-09-2023, 07:59 AM)CounterPillow Wrote: Overlays shouldn't be done with kernel patches. They should be enabled through mainline u-boot.
Absolutely the opposite. Using u-boot for overlay is a very bad solution. The correct solution is to perform the overlay "on the fly" in a running system, analogous to PnP drivers. Using u-booth to overlay, you will have to reboot the entire system at every change and do a bunch of stupid work.
Absolutely the opposite. "on-the-fly" overlays were rejected by the mainline kernel because they're a bad hack. Of course, Armbian loves carrying bad hacks around, which is why people keep complaining that they can't get more than a week's worth of uptime in the chats with it.
Show how you will enable the overlay in EFI mode (using u-boot and with EDK2). In the main core, the part uses the opinion of "authoritative" idiots who do not understand the essence. Example - placing dtb files in the root system is complete idiocy. And there are more than enough such examples. But idiots stupidly repeat this idiocy referring to "this is used in the main core, so this is the right decision." And if you follow your logic, all overlays are hacks that violate security and stability, so they should not be used. The only correct solution is to use a full-fledged DTB with included content at once at the level of the entire DTB.
Show examples that Armbian cannot provide uptime.
How many users use your system ?