NixOS on ARM/UEFI: Difference between revisions
Marked this version for translation Tags: Mobile edit Mobile web edit |
→Device Trees: added info on problems with customized device trees/device tree overlays and EFI boot |
||
| Line 154: | Line 154: | ||
<!--T:49--> | <!--T:49--> | ||
With ''U-Boot'', it is possible to make it load a device tree, for example a more up-to-date one, by placing the dtb folder from a kernel build output at the <code>/dtb</code> location in the ESP. ''U-Boot'' will automatically load a device tree according to heuristics, which should be the right one. | With ''U-Boot'', it is possible to make it load a device tree, for example a more up-to-date one, by placing the dtb folder from a kernel build output at the <code>/dtb</code> location in the ESP. ''U-Boot'' will automatically load a device tree according to heuristics, which should be the right one. This is not done automatically, and may be potentially problematic when one wants to use NixOS <code>hardware.deviceTree.overlays</code> options - a rebuild will succeed, but the overlay will not be applied on the next boot. | ||
<!--T:50--> | <!--T:50--> | ||
If one is using systemd-boot, this can be worked around by providing the device tree's full path to <code>hardware.deviceTree.name</code> - for example, <code>hardware.deviceTree.name = "rockchip/rk3328-rock64.dtb";</code> for a PINE64 ROCK64 board. | |||
</translate> | </translate> | ||