stable - 6.5.5
mainline - 4.19.295
mainline - 5.10.197
mainline - 5.15.133
mainline - 5.4.257
mainline - 4.14.326
mainline - 6.4.16
mainline - 6.1.55
mainline - 6.6-rc2
[click here for custom version]
CONFIG_ARM_APPENDED_DTB is not available for the default architecture x86.
Result is shown for architecture arm
is depended by
Use appended device tree blob to zImage (EXPERIMENTAL)
Linux Kernel Configuration
└─> Boot options
└─> Use appended device tree blob to zImage (EXPERIMENTAL)
With this option, the boot code will look for a device tree binary
(DTB) appended to zImage
(e.g. cat zImage <filename>.dtb > zImage_w_dtb).
This is meant as a backward compatibility convenience for those
systems with a bootloader that can't be upgraded to accommodate
the documented boot protocol using a device tree.
Beware that there is very little in terms of protection against
this option being confused by leftover garbage in memory that might
look like a DTB header after a reboot if no actual DTB is appended
to zImage. Do not leave this option active in a production kernel
if you don't intend to always append a DTB. Proper passing of the
location into r2 of a bootloader provided DTB is always preferable
to this option.
kernelconfig.io - © copyright 2022 -