u-boot.git/Makefile, branch v2015.10

Prepare v2015.10

2015-10-19T23:59:38+00:00

Signed-off-by: Tom Rini

Prepare v2015.10-rc5

2015-10-12T15:14:27+00:00

Signed-off-by: Tom Rini

Prepare v2015.10-rc4

2015-09-28T20:57:42+00:00

Signed-off-by: Tom Rini

Prepare v2015.10-rc3

2015-09-07T12:56:35+00:00

Signed-off-by: Tom Rini

Makefile: fix SOURCE_DATE_EPOCH for *BSD host

2015-08-28T16:33:19+00:00

The SOURCE_DATE_EPOCH mechanism for reproducible builds require some date(1)
with -d switch to print the relevant date and time strings of another point of
time.

In other words it requires some date(1) that behaves like the GNU date(1) [1].
The BSD date(1) [2] on the other hand has the same switch but with a different
meaning.

Respect this and check the date(1) abilities before usage, error on non
working version.  Use the well known pre- and suffixes for the GNU variant of
a tool on *BSD hosts to search for a working date(1) version.

[1] http://man7.org/linux/man-pages/man1/date.1.html [2]
http://www.freebsd.org/cgi/man.cgi?query=date

Signed-off-by: Andreas Bießmann

ARM: keystone2: move the custom build rules out to keystone specific makefile

2015-08-28T16:33:15+00:00

Keystone has build rules introduced by commit ef509b9063fb7 ("k2hk: add
support for k2hk SOC and EVM") and commit 0e7f2dbac6ead ("keystone: add
support for NAND gpheader image").

These are not reused by other platforms for the build, hence there is no
clear benefit is maintaining them in the generic makefile as a build
target. move these to the keystone specific make option

Original idea of using config.mk by Lokesh Vutla 

Signed-off-by: Nishanth Menon 
Signed-off-by: Lokesh Vutla

Makefile: Use correct timezone for U_BOOT_TZ

2015-08-28T16:33:12+00:00

When building with SOURCE_DATE_EPOCH the timezone is in UTC. When
building normally the timezone is taken from the build machine's locale
setting.

Signed-off-by: Chris Packham 
Tested-by: Bin Meng 
Tested-by: Paul Kocialkowski 
Tested-by: Andreas Bießmann

x86: ifdtool: Support collating microcode into one place

2015-08-26T14:54:10+00:00

The Intel Firmware Support Package (FSP) requires that microcode be provided
very early before the device tree can be scanned. We already support adding
a pointer to the microcode data in a place where early init code can access.

However this just points into the device tree and can only point to a single
lot of microcode. For boards which may have different CPU types we must
support multiple microcodes and pass all of them to the FSP in one place.

Enhance ifdtool to scan all the microcode, place it together in the ROM and
update the microcode pointer to point there. This allows us to pass multiple
microcode blocks to the FSP using its existing API.

Enable the flag in the Makefile so that this feature is used by default for
all boards.

Signed-off-by: Simon Glass 
Reviewed-by: Bin Meng 
Tested-by: Bin Meng

Prepare v2015.10-rc2

2015-08-17T21:32:23+00:00

Signed-off-by: Tom Rini

Makefile: Add target for building bootable SPL image for SoCFPGA

2015-08-08T12:14:10+00:00

Add build target for generating boot partition images recognised by
the SoCFPGA BootROM. The SoCFPGA BootROM expects four copies of the
u-boot-spl-dtb.sfp at the beginning of boot partition. Those are
u-boot-spl-dtb.bin augmented by a header with which the BootROM can
work. The u-boot-dtb.img uImage is appended to this to produce a
full boot partition image, the u-boot-with-spl-dtb.sfp . This is
the name of the final target.

Signed-off-by: Marek Vasut