Difference between revisions of "Kernel-with-device-tree"
(→u-boot) |
(→kernel) |
||
| Line 18: | Line 18: | ||
==kernel== | ==kernel== | ||
| + | |||
| + | The kernel 3.4 has already the support sor form arm soc. | ||
| + | |||
| + | * imxl (apf9328) : no | ||
| + | * imx27 (apf27) : yes | ||
| + | * imx51 (apf51) : yes | ||
| + | * imx28 (apf28) : no | ||
| + | |||
| + | So apf27 and apf51 can use device tree. | ||
Revision as of 18:13, 16 June 2012
use device tree
To use device tree on arm both bootloader (u-boot) and kernel should be compiled with the support of device tree.
u-boot
To enable device tree on u-boot, it's quite simple, just add "#define CONFIG_OF_LIBFDT" in your configuration file (include/configs/<board>.h).
On armadeus SDK, this file is in this directory: buildroot/target/device/armadeus/<board>/<board>-u-boot-<version>.h
For example, for u-boot 2012.04 on apf27, it's: buildroot/target/device/armadeus/apf27/apf27-u-boot-2012.04.h
NOTE: on u-boot 2012.04, the command bootm with device tree is broken. If you want to use it,
you need to fix it with the following patch: http://git.denx.de/?p=u-boot.git;a=commit;h=1723997610ace497252d6f9a44ec76c06951ae43
kernel
The kernel 3.4 has already the support sor form arm soc.
- imxl (apf9328) : no
- imx27 (apf27) : yes
- imx51 (apf51) : yes
- imx28 (apf28) : no
So apf27 and apf51 can use device tree.
