aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/bcm53xx/files-4.1/drivers/firmware/broadcom
diff options
context:
space:
mode:
authorAlexey Brodkin <abrodkin@synopsys.com>2016-06-20 15:46:28 +0200
committerZoltan HERPAI <wigyori@uid0.hu>2016-06-20 15:46:28 +0200
commit49a74031a157caf97a8eb5f9a6079368ece5a5de (patch)
tree09cf46f05fe65dc9c326ab91c9e6fc015c98a4c0 /target/linux/bcm53xx/files-4.1/drivers/firmware/broadcom
parentd44ce810e4aa73562eaeef5ef0b3f0d26b3053cf (diff)
downloadmaster-187ad058-49a74031a157caf97a8eb5f9a6079368ece5a5de.tar.gz
master-187ad058-49a74031a157caf97a8eb5f9a6079368ece5a5de.tar.bz2
master-187ad058-49a74031a157caf97a8eb5f9a6079368ece5a5de.zip
arc: Build uImage as well as vmlinux output files
Initially for ARC we were building vmlinux images because it was both simpler and more convenient to debug Linux kernel in runt-time via JTAG. Now when base system works quite nice we may finally use U-Boot for loading the system image as well. Still we keep building vmlinux images as some of our boards are development boards and loading images with JTAG could be at some points very beneficial. Note for U-Boot header it's required to specify 2 values: * loading address * entry point (if it doesn't match loading address) and in case of ARC entry point (EP) not only differs from loading address but also changes from build to build due to initramfs being placed between loading address and text section. To accommodate that feature we have to calculate EP after vmlinux gets built and before call to mkimage. Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Diffstat (limited to 'target/linux/bcm53xx/files-4.1/drivers/firmware/broadcom')
0 files changed, 0 insertions, 0 deletions