summaryrefslogtreecommitdiff
path: root/arch/arm/mach-uniphier/memconf
diff options
context:
space:
mode:
authorMasahiro Yamada <yamada.masahiro@socionext.com>2015-12-17 18:00:37 +0900
committerMasahiro Yamada <yamada.masahiro@socionext.com>2015-12-23 00:08:56 +0900
commit8ea4f49a47753150a6e7cdb3649764d06cd16427 (patch)
tree78c21e5776e9ba116dfad41e916519b52899255a /arch/arm/mach-uniphier/memconf
parent33886693b645dd737a21065c095eac2ce7cbd956 (diff)
downloadu-boot-imx-8ea4f49a47753150a6e7cdb3649764d06cd16427.zip
u-boot-imx-8ea4f49a47753150a6e7cdb3649764d06cd16427.tar.gz
u-boot-imx-8ea4f49a47753150a6e7cdb3649764d06cd16427.tar.bz2
ARM: uniphier: set DTB file name to fdt_file environment
When we want to boot Linux with a DTB file downloaded from a TFTP server or somewhere, we need to know the file name to be downloaded. Assume the U-Boot configuration is shared among some similar boards. If they are similar enough, the difference only appears in device trees. The build procedure would be like this: - Board A: make foo_common_defconfig && make DEVICE_TREE=foo_board_a - Board B: make foo_common_defconfig && make DEVICE_TREE=foo_board_b - Board C: make foo_common_defconfig && make DEVICE_TREE=foo_board_c In this case, the U-Boot image contains nothing about the DTB file name it is running with. (CONFIG_DEFAULT_DEVICE_TREE is not helpful for this purpose because it is painful to change it from "make menuconfig" for each board.) This commit allows to lookup the DTB file name based on the compatible string and set it to "fdt_file" environment. Then "tftpboot $fdt_file" will download the file we want. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'arch/arm/mach-uniphier/memconf')
0 files changed, 0 insertions, 0 deletions