Hi, > On 1 Feb 2025, at 16:28, Matwey V. Kornilov <matwey.korni...@gmail.com> wrote: > > пт, 31 янв. 2025 г. в 16:41, Ivan Ivanov <ivan.iva...@suse.com>: >> >> Hi, >> >>> On 30 Jan 2025, at 16:19, Matwey Kornilov <matwey.korni...@gmail.com> wrote: >>> >>> Torsten Duwe wrote: >>>> Hi Matwey, >>>> >>>> On Tue, 28 Jan 2025 16:38:21 -0000 >>>> "Matwey Kornilov" <matwey.korni...@gmail.com> wrote: >>>>> Hello, >>>>> What is the recommended way to apply device tree overlay when running >>>>> openSUSE Tumbleweed on ARM single board computer? Is there any wiser >>>>> way than just patch corresponding /boot/dtb/ file? >>>>> I'm not an expert on DTBOs, I compile and hence patch DTSes on a daily >>>> basis, but I think that our Raspberry Pi images provide a mechanism to >>>> load overlays automatically. Maybe have a look there? >>> >>> What do you mean? I found only manual command in u-boot console, but it is >>> not suitable for persistent configuration. >> >> Why not? You could modify bootcmd to apply your DTBO at boot. > > My bootcmd is `bootflow scan` which also loads the main dtb from the > filesystem. So I also have to read dtb manually in order to apply the > overlay. >
Sure, but you could extend it with some more commands, before scan, I think. >> >> >>> While I would expect something like >>> https://github.com/edk2-porting/edk2-rk3588?tab=readme-ov-file#custom-device-tree-blob-dtb-override-and-overlays >>> >> >> IIUC this is similar to how U-Boot apply overlays, it is just EDK2. >> > > If I understand correctly, it is not. There are some specific cases > (like BeagleBone Black) when u-boot automatically apply overlays, > while it doesn't discover any overlays generally. Not sure I get this. The point is that it is the device firmware which apply these overlays. Regards, Ivan
