Paul Burton b2f815bb5f boston: Pad binary in .mcs to a multiple of 16 bytes ... When flashing U-Boot on a Boston board using Xilinx Vivado tools, the final 0x00 byte which ends the .relocs section seems to be skipped & left in flash as 0xff unless the data contained in the .mcs is padded out to a 16 byte boundary. Without our final zero byte relocation will fail with an error about a spurious reloc: Avoid this problem by padding out the data in the .mcs file to a 16 byte boundary using srec_cat's -range-pad functionality. Signed-off-by: Paul Burton <paul.burton@mips.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>		2018-01-25 17:40:42 +01:00
..
boston-lcd.h
boston-regs.h
checkboard.c
config.mk	boston: Pad binary in .mcs to a multiple of 16 bytes	2018-01-25 17:40:42 +01:00
ddr.c	board_f: Rename initdram() to dram_init()	2017-04-13 09:40:57 -04:00
dt.c	boston: Setup memory ranges in FDT provided to Linux	2017-05-12 13:29:50 +02:00
Kconfig
lowlevel_init.S	boston: Remove unused label in lowlevel_display	2017-11-28 21:59:30 +01:00
MAINTAINERS	Update Paul Burton's email address	2017-11-28 21:59:30 +01:00
Makefile	boston: Setup memory ranges in FDT provided to Linux	2017-05-12 13:29:50 +02:00