30 Dec, 2014

10 commits

  • Signed-off-by: Tom Rini

    Tom Rini
     
  • Signed-off-by: Dirk Behme
    Acked-by: Simon Glass

    Dirk Behme
     
  • 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

    Nikolay Dimitrov
     
  • 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

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

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

    Steve Rae
     
  • 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

    Alexey Brodkin
     
  • 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

    Masahiro Yamada
     
  • 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

    Stephen Warren
     
  • 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

    Stephen Warren
     
  • 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

    Stephen Warren
     

29 Dec, 2014

6 commits

  • The few Versatile Express ARMv8 platforms we have may just as
    well be switched to generic board from the beginning.

    Tested on the ARM foundation model and the in progress support
    for the ARMv8 Juno board.

    Signed-off-by: Linus Walleij
    Acked-by: Steve Rae

    Linus Walleij
     
  • As agreed with Steve Rae I'm taking over maintenance of the
    semihosted, emulated FVP/foundation model Versatile Express
    64 bit board variant.

    Signed-off-by: Linus Walleij
    Acked-by: Steve Rae

    Linus Walleij
     
  • By rearranging the functions in the semihosting code we can
    avoid forward-declaration of the internal static functions.
    This puts the stuff in a logical order: read/open/close/len
    and then higher-order functions follow at the end.

    Cc: Darwin Rambo
    Cc: AKASHI Takahiro
    Cc: Mark Hambleton
    Cc: Tom Rini
    Acked-by: Steve Rae
    Signed-off-by: Linus Walleij

    Linus Walleij
     
  • There is currently a regression when using newer ARM64 compilers
    for semihosting: the way long types are inferred from context
    is no longer the same.

    The semihosting runtime uses long and size_t, so use this
    explicitly in the semihosting code and interface, and voila:
    the code now works again.

    Tested with aarch64-linux-gnu-gcc: Linaro GCC 4.9-2014.09.

    Cc: Darwin Rambo
    Cc: AKASHI Takahiro
    Cc: Mark Hambleton
    Cc: Tom Rini
    Acked-by: Steve Rae
    Suggested-by: Mark Hambleton
    Signed-off-by: Linus Walleij

    Linus Walleij
     
  • The semihosting code exposes internal file handle handling
    functions to read(), open(), close() and get the length of
    a certain file handle.

    However the code using it is only interested in either
    reading and entire named file into memory or getting the
    file length of a file referred by name. No file handles
    are used.

    Thus make the file handle code internal to this file by
    removing these functions from the semihosting header file
    and staticize them.

    This gives us some freedom to rearrange the semihosting
    code without affecting the external interface.

    Cc: Darwin Rambo
    Cc: AKASHI Takahiro
    Cc: Mark Hambleton
    Cc: Tom Rini
    Acked-by: Steve Rae
    Signed-off-by: Linus Walleij

    Linus Walleij
     
  • Tom Rini
     

26 Dec, 2014

1 commit


20 Dec, 2014

1 commit


19 Dec, 2014

22 commits