u-boot.git, branch v2015.01-rc4

Prepare v2015.01-rc4

2014-12-30T02:22:38+00:00

Signed-off-by: Tom Rini

buildman: Fix some typos in README

2014-12-29T21:31:24+00:00

Signed-off-by: Dirk Behme 
Acked-by: Simon Glass

Fix hash verification

2014-12-29T21:31:24+00:00

Fix issue in parse_verify_sum() which swaps handling of env-var and *address.
Move hash_command() argc check earlier.
Cosmetic change on do_hash() variable declaration.
Improved help message for "hash" command.

Signed-off-by: Nikolay Dimitrov 
Reviewed-by: Simon Glass

common/board_f.c: fix compile error when tracing disabled

2014-12-29T21:31:23+00:00

When CONFIG_TRACE is disabled, linking fails with:

common/built-in.o:(.data.init_sequence_f+0x8): undefined reference to `trace_early_init'

To fix, wrap the call to trace_early_init() with #ifdef CONFIG_TRACE.

Cc: Simon Glass 
Cc: Tom Rini 
Signed-off-by: Kevin Hilman

bcm281xx: add support for "USB OTG clock"

2014-12-29T21:31:23+00:00

enable this clock with the following:
  clk_usb_otg_enable((void *)HSOTG_BASE_ADDR)

Signed-off-by: Steve Rae 
Reviewed-by: Felipe Balbi

initcall: add explicit hint if initcall was relocated

2014-12-29T21:31:23+00:00

Commit "initcall: Improve debugging support" makes sense and indeed
simplifies process of matching initcalls executed with static
disassembly.

Until you are debugging relocation functionality.

Existign output may make you think that at some point execution somehow
returned back to non-relocated area. And there're many reasons/problems
that may provoke this behavior.

In order to make things clear let's add explicit mention in case initall
was actually relocated like this:
--->---
initcall: 810015f8
Relocation Offset is: 0efcf000
Relocating to 8ffcf000, new gd at 8fdced3c, sp at 8fdced20
initcall: 810015b8
initcall: 8ffd093c
initcall: 8ffd0a14
initcall: 81001940 (relocated to 8ffd0940)
initcall: 81001958 (relocated to 8ffd0958)
--->---

Note "unexpected" jump from 0x8f... area to 0x81... area.
Without explanation this raises many questions: execution jumped in
relocated area right as expected and then for some reason returned back?

But I hope comment in brackets will save some time for those curious
developers who are careful enough to catch "unexpected jump to pre-reloc
area" or those unlucky ones who'll have to deal with relocation
debugging.

Signed-off-by: Alexey Brodkin 
Cc: Simon Glass 
Cc: Minkyu Kang

scripts: fix binutils-version.sh

2014-12-29T21:31:23+00:00

The current binutils-version.sh expects the version string at the end
of the first line.  It turned out to not work with Linaro toolchain:
It has "Linaro 2014.09" at the back.

To fix this issue, let's parse the word right after the close
parenthesis.

Signed-off-by: Masahiro Yamada 
Reported-by: York Sun 
Acked-by: Dirk Behme

ARM: rpi: consolidate board rev error checking

2014-12-29T21:31:22+00:00

Create a fake model table entry with default values, so we can error
check the board rev value once when querying it from the firmware, rather
than error-checking for invalid board rev values every time the model
table is used.

Signed-off-by: Stephen Warren

ARM: rpi: support model A+

2014-12-29T21:31:22+00:00

Add a board rev entry for the new model A+, and augment the board
rev error handling code to be a bit more verbose.

Signed-off-by: Stephen Warren

ARM: rpi: only set usbethaddr on relevant systems

2014-12-29T21:31:22+00:00

Model A and CM RPis don't have an on-board USB Ethernet device. Hence,
there's no point setting $usbethaddr based on the device fuses. Use the
model detection code to gate this. Note that the fuses are actually
programmed even on those devices though.

Signed-off-by: Stephen Warren