CONFIG_ARM_APPENDED_DTB: Use appended device tree blob to zImage (EXPERIMENTAL)

General informations

The Linux kernel configuration item CONFIG_ARM_APPENDED_DTB:

• prompt: Use appended device tree blob to zImage (EXPERIMENTAL)
• type: bool
• depends on: CONFIG_OF
• defined in arch/arm/Kconfig
• found in Linux kernels: 3.2–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.12

Help text

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.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: