03 Dec, 2018

1 commit


01 Dec, 2018

1 commit

  • The "Flamingo" carrier-board for the RK3399-Q7 has a RV3029 populated
    and the application will use the off-module RV3029 RTC including the
    battery backed SRAM.

    To support this use case, this commit includes the following changes:
    * updates the rv3029 driver to use DM
    * implements the read8/write8 operations

    This syncs the implementation with the Linux code (based on 4.17),
    porting the trickle-charger support from there (with improvements to
    avoid unnecessary EEPROM updates) and adheres to the Linux DTS
    binding.

    Signed-off-by: Philipp Tomsich
    Tested-by: Klaus Goger

    Philipp Tomsich
     

29 Nov, 2018

1 commit


27 Nov, 2018

1 commit


26 Nov, 2018

1 commit


17 Nov, 2018

1 commit


14 Nov, 2018

1 commit


25 Oct, 2018

1 commit


22 Oct, 2018

1 commit


20 Oct, 2018

3 commits


10 Oct, 2018

1 commit


09 Oct, 2018

3 commits


06 Oct, 2018

1 commit

  • Instead of manually specifying CONFIG_SYS_EXTRA_ENV_RELOC
    for every board that needs it, it shouldn't hurt to let
    initr_reloc_global_data() always relocate gd->env_addr
    unless we know this pointer is outside the initial binary.

    To achieve this, the relocation is omitted if
    CONFIG_ENV_ADDR is defined (and ENV_IS_EMBEDDED is not).

    Signed-off-by: Simon Goldschmidt

    Simon Goldschmidt
     

01 Oct, 2018

3 commits

  • Tom Rini
     
  • The escape sequence '\#' does not work for the latest GNU Make from
    the git tree.

    Replace it with $(pound) as Linux did.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     
  • [ commit 9564a8cf422d7b58f6e857e3546d346fa970191e in Linux ]

    I tried building using a freshly built Make (4.2.1-69-g8a731d1), but
    already the objtool build broke with

    orc_dump.c: In function ‘orc_dump’:
    orc_dump.c:106:2: error: ‘elf_getshnum’ is deprecated [-Werror=deprecated-declarations]
    if (elf_getshdrnum(elf, &nr_sections)) {

    Turns out that with that new Make, the backslash was not removed, so cpp
    didn't see a #include directive, grep found nothing, and
    -DLIBELF_USE_DEPRECATED was wrongly put in CFLAGS.

    Now, that new Make behaviour is documented in their NEWS file:

    * WARNING: Backward-incompatibility!
    Number signs (#) appearing inside a macro reference or function invocation
    no longer introduce comments and should not be escaped with backslashes:
    thus a call such as:
    foo := $(shell echo '#')
    is legal. Previously the number sign needed to be escaped, for example:
    foo := $(shell echo '\#')
    Now this latter will resolve to "\#". If you want to write makefiles
    portable to both versions, assign the number sign to a variable:
    C := \#
    foo := $(shell echo '$C')
    This was claimed to be fixed in 3.81, but wasn't, for some reason.
    To detect this change search for 'nocomment' in the .FEATURES variable.

    This also fixes up the two make-cmd instances to replace # with $(pound)
    rather than with \#. There might very well be other places that need
    similar fixup in preparation for whatever future Make release contains
    the above change, but at least this builds an x86_64 defconfig with the
    new make.

    Link: https://bugzilla.kernel.org/show_bug.cgi?id=197847
    Cc: Randy Dunlap
    Signed-off-by: Rasmus Villemoes
    Signed-off-by: Masahiro Yamada

    Rasmus Villemoes
     

29 Sep, 2018

3 commits


28 Sep, 2018

1 commit


27 Sep, 2018

1 commit

  • Patch queue for efi - 2018-09-26

    A lot of goodness in this release. We're *very* close to running the
    UEFI Shell and SCT natively. The only missing piece are HII protocols.

    - FAT write support (needed for SCT)
    - improved FAT directory support (needed for SCT)
    - RTC support with QEMU -M virt
    - Sandbox support (run UEFI binaries in Linux - yay)
    - Proper UTF-16 support
    - EFI_UNICODE_COLLATION_PROTOCOL support (for UEFI Shell)
    - EFI_SIMPLE_TEXT_INPUT_EX_PROTOCOL support (for UEFI Shell)
    - Fix window size determination
    - Fix Tegra by explicitly unmapping RAM
    - Clean up handle entanglement
    - Lots of generic code cleanup

    [trini: Fixup merge conflict in include/configs/qemu-arm.h]
    Signed-off-by: Tom Rini

    Tom Rini
     

26 Sep, 2018

1 commit


24 Sep, 2018

1 commit


23 Sep, 2018

2 commits


15 Sep, 2018

1 commit


11 Sep, 2018

2 commits


18 Aug, 2018

6 commits


17 Aug, 2018

2 commits

  • We have the following cases:
    - CONFIG_NR_DRAM_BANKS was defined, migrate normally
    - CONFIG_NR_DRAM_BANKS_MAX was defined and then used for
    CONFIG_NR_DRAM_BANKS after a check, just migrate it over now.
    - CONFIG_NR_DRAM_BANKS was very oddly defined on p2771-0000-* (to 1024 +
    2), set this to 8.

    Signed-off-by: Tom Rini

    Tom Rini
     
  • While we have long since migrated to CONFIG_SYS_GENERIC_BOARD being
    enabled, we had just a few places left that still referenced or defined
    it. Update.

    Signed-off-by: Tom Rini

    Tom Rini