u-boot.git/board/raspberrypi, branch v2016.03

rpi: set board serial number in environment

2016-02-24T23:44:12+00:00

Gets propagated into the device tree and then into /proc/cpuinfo where
users often expect it.

Signed-off-by: Lubomir Rintel 
Tested-by: Stephen Warren 
Reviewed-by: Stephen Warren

rpi: set ethaddr as well

2016-02-08T15:10:49+00:00

Let's set "ethaddr" when we get the ethernet address too, so that
fdt_fixup_ethernet() sets the address in the device tree and the Linux
driver can pick it up.

Signed-off-by: Lubomir Rintel 
Tested-by: Stephen Warren

rpi: fix up Model B entries

2016-02-08T15:10:38+00:00

The P5 header was not present on "Model B" any board prior to Revision 2.0,
there's no need for a separate device tree.

Also, it looks like "rev2" is incorrectly used to only cover the 512MiB
memory models; there also were 256MiB 2.0 boards.

I don't have all of the boards to check this, I'm following this table:
http://elinux.org/RPi_HardwareHistory#Board_Revision_History

Signed-off-by: Lubomir Rintel

rpi: link to another model number info source

2016-02-08T15:10:37+00:00

This source has been blessed by Dom Cobley at the RPi Foundation, so seems
like the best source to refer to. It's a superset of and consistent with
the other sources.

Cc: Lubomir Rintel 
Cc: Eric Anholt 
Signed-off-by: Stephen Warren

rpi: add support for Raspberry Pi Zero

2015-12-05T23:22:36+00:00

For U-Boot's purposes, at present all we care about is ensuring there's
a model table entry.

Signed-off-by: Stephen Warren

rpi: fix revision scheme parsing

2015-12-05T23:22:36+00:00

The RPi has two different schemes for encoding board revision values.
When adding RPi 2 support, I thought that the conflicting type field
values were to be interpreted based on bcm2835-vs-bcm2836. In fact, the
scheme bit determines the encoding. The RPi Zero uses the bcm2835 yet
uses the new encoding scheme. Fix the code to cater for this correctly.

Signed-off-by: Stephen Warren

rpi: get rid of BCM2835_BOARD_REV_* macros

2015-12-05T23:22:35+00:00

There are two numbering schemes for the RPi revision values; old and new
scheme. The values within each scheme overlap. Hence, it doesn't make
sense to have absolute/global names for the revision IDs. Get rid of the
names and just use the raw revision/type values to set up the array of
per-revision data.

This change makes most sense when coupled with the next change. However,
it's split out so that the mechanical cut/paste is separate from the
logic changes for easier review and problem bisection.

Signed-off-by: Stephen Warren

ARM: rpi: Add CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG support

2015-10-24T17:50:30+00:00

Add CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG support and enable it to set
'board_rev' and 'board_name' envs.
'board_rev' can be used in scripts to determine what board we are running on
and 'board_name' for pretty printing.

Signed-off-by: Guillaume GARDET 

Cc: Stephen Warren 
Acked-by: Stephen Warren

ARM: rpi: add another revision of Raspberry Pi A+

2015-10-19T06:12:25+00:00

Seen this one in the wild. Is labelled "Raspberry Pi Model A+ V1.1,
(C) Raspberry Pi 2014". A standard A+ board, much like the one with
version 0x12, didn't notice any differencies.

Signed-off-by: Lubomir Rintel

Move ALLOC_CACHE_ALIGN_BUFFER() to the new memalign.h header

2015-09-11T21:15:20+00:00

Now that we have a new header file for cache-aligned allocation, we should
move the stack-based allocation macro there also.

Signed-off-by: Simon Glass