Eric Lee / smarc-uboot

24 Feb, 2018

1 commit

  • d021e9421   Convert CONFIG_BOOTP_BOOTPATH et al to Kconfig ... Browse Code »

    This converts the following to Kconfig:
    CONFIG_BOOTP_BOOTPATH
    CONFIG_BOOTP_DNS
    CONFIG_BOOTP_GATEWAY
    CONFIG_BOOTP_HOSTNAME
    CONFIG_BOOTP_PXE
    CONFIG_BOOTP_SUBNETMASK
    CONFIG_CMDLINE_EDITING
    CONFIG_AUTO_COMPLETE
    CONFIG_SYS_LONGHELP
    CONFIG_SUPPORT_RAW_INITRD
    CONFIG_ENV_VARS_UBOOT_CONFIG

    Signed-off-by: Adam Ford
    [trini: Re-run the migration]
    Signed-off-by: Tom Rini

    Adam Ford
     

11 Feb, 2018

1 commit

  • 278b90ce7   configs: Migrate CONFIG_SYS_TEXT_BASE ... Browse Code »
    15

    On the NIOS2 and Xtensa architectures, we do not have
    CONFIG_SYS_TEXT_BASE set. This is a strict migration of the current
    values into the defconfig and removing them from the headers.

    I did not attempt to add more default values in and for now will leave
    that to maintainers.

    Signed-off-by: Tom Rini

    Tom Rini
     

29 Jan, 2018

2 commits

21 Oct, 2017

1 commit

  • 8daec2d9d   net: Add SMC911X driver to Kconfig, convert ... Browse Code »

    We add the various SMC91XX symbols to drivers/net/Kconfig and then this
    converts the following to Kconfig:
    CONFIG_SMC911X
    CONFIG_SMC911X_BASE
    CONFIG_SMC911X_16_BIT
    CONFIG_SMC911X_32_BIT

    Signed-off-by: Adam Ford
    [trini: Apply to the rest of the tree, re-squash old and new patch]
    Signed-off-by: Tom Rini

    Adam Ford
     

04 Sep, 2017

2 commits

  • e090579d0   include/configs: remove numerous CONFIG_SYS_BARGSIZE definitions ... Browse Code »

    This commit removes definitions of CONFIG_SYS_BARGSIZE defined to be
    equal to CONFIG_SYS_CBSIZE in numerous configuration files.

    We remove such definitions in two situations:

    - CONFIG_SYS_CBSIZE is otherwise not defined in the board
    configuration file, which means the default value of
    CONFIG_SYS_CBSIZE == 256 applies. In this case, the default value
    of CONFIG_SYS_BARGSIZE == 512 (common/image.c) is suitable, as it is
    larger.

    - CONFIG_SYS_CBSIZE is defined in the board configuration file, but
    to a value equal or less than 512. In this case, the default value
    of CONFIG_SYS_BARGSIZE == 512 (common.image.c) is suitable, as it
    is equal or larger.

    Signed-off-by: Thomas Petazzoni
    Reviewed-by: Tom Rini

    Thomas Petazzoni
     
  • 432e39806   include/configs: drop default definitions of CONFIG_SYS_PBSIZE ... Browse Code »
    1

    Now that the fallback value of CONFIG_SYS_PBSIZE in
    include/config_fallbacks.h has been adjusted, remove its definition
    from a large number of board configuration files.

    Signed-off-by: Thomas Petazzoni
    Reviewed-by: Tom Rini

    Thomas Petazzoni
     

15 Aug, 2017

1 commit

26 Jul, 2017

1 commit

22 May, 2017

1 commit

20 Mar, 2017

1 commit

09 Feb, 2017

1 commit

  • e9d33e732   cmd: move CONFIG_CMD_UNZIP and CONFIG_CMD_ZIP to Kconfig ... Browse Code »

    CONFIG_CMD_ZIP is not defined by any board. I am moving
    CONFIG_CMD_UNZIP to defconfig files except UniPhier SoC family.

    I am the maintainer of UniPhier platform, so I know "select CMD_UNZIP"
    is better for this platform.

    Signed-off-by: Masahiro Yamada
    Acked-by: Michal Simek
    Acked-by: Stefan Roese
    Acked-by: Ryan Harkin
    Tested-by: Ryan Harkin

    Masahiro Yamada
     

28 Jan, 2017

1 commit

04 Dec, 2016

2 commits

  • bfb380b30   cmd: move CMD_PXE to Kconfig ... Browse Code »

    Currently, CMD_PXE is forcibly enabled in config_distro_defaults.h, so
    that general purpose distributions can rely on it being defined. This
    header is included, under conditions or not, by various archs or
    famillies of archs / SoCs.

    However, it is very possible that boards based on those SoCs will not
    have a physical ethernet connector at all, even if the have a MAC; for
    example, the Nanopi Neo AIR (sunxi H3) does not. It is also possible
    that network booting is absolutely not necessary for a device.

    However, it is not possible to disable the PXE command, as it is
    forcibly enabled and is non-configurable.

    But it turns out we already have a config option to build a distro-ready
    image, in the name of DISTRO_DEFAULTS.

    Move CMD_PXE out of the hard-coded config_distro_defaults.h into a
    Kconfig option, that gets selected by DISTRO_DEFAULTS when it is set.

    Signed-off-by: "Yann E. MORIN"
    Cc: Joe Hershberger
    [trini: Make it select MENU, run moveconfig.py]
    Signed-off-by: Tom Rini

    Yann E. MORIN
     
  • 4880b026e   cmd: Convert CMD_BOOTMENU ... Browse Code »

    Also convert MENU while we're in here.

    Signed-off-by: Tom Rini

    Tom Rini
     

20 Sep, 2016

1 commit

27 Aug, 2016

1 commit

  • 067716bac   ARM: Move SYS_CACHELINE_SIZE over to Kconfig ... Browse Code »

    This series moves the CONFIG_SYS_CACHELINE_SIZE. First, in nearly all
    cases we are mirroring the values used by the Linux Kernel here. Also,
    so long as (and in this case, it is true) we implement flushes in hunks
    that are no larger than the smallest implementation (and given that we
    mirror the Linux Kernel, again we are fine) it is OK to align higher.
    The biggest changes here are that we always use 64 bytes for CPU_V7 even
    if for example the underlying core is only 32 bytes (this mirrors
    Linux). Second, we say ARM64 uses 64 bytes not 128 (as found in the
    Linux Kernel) as we do not need multi-platform support (to this degree)
    and only the Cavium ThunderX 88xx series has a use for such large
    alignment.

    Cc: Albert Aribaud
    Cc: Marek Vasut
    Cc: Stefano Babic
    Cc: Prafulla Wadaskar
    Cc: Luka Perkov
    Cc: Stefan Roese
    Cc: Nagendra T S
    Cc: Vaibhav Hiremath
    Acked-by: Lokesh Vutla
    Cc: Steve Rae
    Cc: Igor Grinberg
    Cc: Nikita Kiryanov
    Cc: Stefan Agner
    Acked-by: Heiko Schocher
    Cc: Mateusz Kulikowski
    Cc: Peter Griffin
    Acked-by: Paul Kocialkowski
    Cc: Anatolij Gustschin
    Acked-by: "Pali Rohár"
    Cc: Adam Ford
    Cc: Steve Sakoman
    Cc: Grazvydas Ignotas
    Cc: Nishanth Menon
    Cc: Stephen Warren
    Cc: Robert Baldyga
    Cc: Minkyu Kang
    Cc: Thomas Weber
    Cc: Masahiro Yamada
    Cc: David Feng
    Cc: Alison Wang
    Cc: Michal Simek
    Cc: Simon Glass
    Cc: York Sun
    Cc: Shengzhou Liu
    Cc: Mingkai Hu
    Cc: Prabhakar Kushwaha
    Cc: Aneesh Bansal
    Cc: Saksham Jain
    Cc: Qianyu Gong
    Cc: Wang Dongsheng
    Cc: Alex Porosanu
    Cc: Hongbo Zhang
    Cc: tang yuantian
    Cc: Rajesh Bhagat
    Cc: Josh Wu
    Cc: Bo Shen
    Cc: Viresh Kumar
    Cc: Hannes Schmelzer
    Cc: Thomas Chou
    Cc: Joe Hershberger
    Cc: Sam Protsenko
    Cc: Bin Meng
    Cc: Christophe Ricard
    Cc: Anand Moon
    Cc: Beniamino Galvani
    Cc: Carlo Caione
    Cc: huang lin
    Cc: Sjoerd Simons
    Cc: Xu Ziyuan
    Cc: "jk.kernel@gmail.com"
    Cc: "Ariel D'Alessandro"
    Cc: Kever Yang
    Cc: Samuel Egli
    Cc: Chin Liang See
    Cc: Dinh Nguyen
    Cc: Hans de Goede
    Cc: Ian Campbell
    Cc: Siarhei Siamashka
    Cc: Boris Brezillon
    Cc: Andre Przywara
    Cc: Bernhard Nortmann
    Cc: Wolfgang Denk
    Cc: Ben Whitten
    Cc: Tom Warren
    Cc: Alexander Graf
    Cc: Sekhar Nori
    Cc: Vitaly Andrianov
    Cc: "Andrew F. Davis"
    Cc: Murali Karicheri
    Cc: Carlos Hernandez
    Cc: Ladislav Michl
    Cc: Ash Charles
    Cc: Mugunthan V N
    Cc: Daniel Allred
    Cc: Gong Qianyu
    Signed-off-by: Tom Rini
    Acked-by: Masahiro Yamada
    Acked-by: Chin Liang See
    Tested-by: Stephen Warren
    Acked-by: Paul Kocialkowski

    Tom Rini
     

20 Aug, 2016

1 commit

10 Jun, 2016

1 commit

27 May, 2016

1 commit

  • 0dac6b4e8   net: Move the VCI and client arch values to Kconfig ... Browse Code »

    We have a bunch of boards that define their vendor class identifier and
    client archs in the board files or in the distro config. Move everything
    to the generic Kconfig options.

    We're missing the distinction between i386 and x86_64, as I couldn't find
    any config variable that would tell us the difference. Is that really important
    to people? I guess not, so I left it out.

    Signed-off-by: Alexander Graf
    Reviewed-by: Tom Rini

    Alexander Graf
     

26 Apr, 2016

4 commits

16 Mar, 2016

3 commits

15 Mar, 2016

1 commit

06 Feb, 2016

1 commit

  • a187559e3   Use correct spelling of "U-Boot" ... Browse Code »

    Correct spelling of "U-Boot" shall be used in all written text
    (documentation, comments in source files etc.).

    Signed-off-by: Bin Meng
    Reviewed-by: Heiko Schocher
    Reviewed-by: Simon Glass
    Reviewed-by: Minkyu Kang

    Bin Meng
     

08 Jan, 2016

1 commit

  • 7babe4825   arm64: Juno/FVP: adjust kernel load address ... Browse Code »

    The default kernel load offset for an arm64 kernel is 0x80000, so
    U-Boot takes cares of moving the loaded kernel to a matching memory
    location just before booting it.
    Since we run with caches off, this takes a while for any decently
    sized kernel - with no output explaining the reason for the delay
    (unless one uses a DEBUG build).
    By adjusting the default load offset for Juno and VFP to be 512K
    aligned in the first place we can skip this copying and boot much
    faster.
    Tested on Juno.

    Signed-off-by: Andre Przywara
    Reviewed-by: Linus Walleij
    Tested-by: Ryan Harkin

    Andre Przywara
     

22 Nov, 2015

3 commits

  • f3c71c93d   vexpress64: store env in flash ... Browse Code »

    Add support for storing the environment in CFI NOR flash on Juno and FVP
    models.

    I also removed some config values that are not used by CFI flash parts.

    Juno has 1 flash part with 259 sectors. The first 255 sectors are
    0x40000 (256kb) and are followed by 4 sectors of 0x10000 (64KB).

    FVP models simulate a 64MB NOR flash part at base address 0x0FFC0000.
    This part has 256 x 256kb sectors. We use the last sector to store the
    environment.

    To save the NOR flash to a file, the following parameters should be
    passed to the model:

    -C bp.flashloader1.fname=${FILENAME}
    -C bp.flashloader1.fnameWrite=${FILENAME}

    Foundation models don't simulate the NOR flash, but having NOR support
    in the u-boot binary does not harm: attempting to write to the NOR will
    fail gracefully.

    Signed-off-by: Ryan Harkin
    Acked-by: Linus Walleij

    Ryan Harkin
     
  • 3e933f43e   vexpress64: remove #error ... Browse Code »

    This patch allows vexpress64 targets to be compiled when
    CONFIG_SYS_FLASH_CFI is enabled.

    I considered using #warning instead of #error, but this just clutters up
    the build output and hides real warnings.

    Without this patch, you see errors during compilation like this:

    include/configs/vexpress_aemv8a.h:42:2: error: #error "Unknown board
    variant"
    #error "Unknown board variant"
    include/configs/vexpress_aemv8a.h:115:2: error: #error "Unknown board
    variant"
    #error "Unknown board variant"
    include/configs/vexpress_aemv8a.h:280:2: error: #error "Unknown board
    variant"
    #error "Unknown board variant"
    make[1]: *** [tools/envcrc.o] Error 1
    make: *** [tools] Error 2
    In file included from include/config.h:5:0,
    from tools/envcrc.c:19:

    Signed-off-by: Ryan Harkin
    Acked-by: Linus Walleij

    Ryan Harkin
     
  • 2c2b21838   vexpress64: use 2nd DRAM bank only on juno ... Browse Code »

    This patch makes the 2nd DRAM bank available on Juno only and not on
    other vexpress64 targets, eg. the FVP models.

    The commit below added a 2nd bank of NOR flash for Juno, but also for
    all vexpress64 targets:

    commit 2d0cee1ca2b9d977fa3214896bb2e30cfec77059
    Author: Liviu Dudau
    Date: Mon Oct 19 11:08:31 2015 +0100

    vexpress64: Juno: Declare all 8GB of RAM and make them visible to the kernel.

    Juno comes with 8GB RAM, but U-Boot only passes 2GB to the kernel.
    Declare a secondary memory bank and set the sizes correctly.

    Signed-off-by: Liviu Dudau
    Reviewed-by: Linus Walleij
    Reviewed-by: Ryan Harkin
    Tested-by: Ryan Harkin

    Unfortunately, I only fully tested on Juno R0, R1 and the FVP Foundation
    model. Whilst FVP Base AEMV8 models run U-Boot OK, they fail to boot
    the kernel.

    Signed-off-by: Ryan Harkin
    Acked-by: Liviu Dudau
    Reviewed-by: Linus Walleij

    Ryan Harkin
     

25 Oct, 2015

1 commit

  • 09f3ca3dd   arm, powerpc: select SYS_GENERIC_BOARD ... Browse Code »

    We have finished Generic Board conversion for ARM and PowerPC, i.e.
    all the boards have been converted except OpenRISC, SuperH, SPARC,
    which have not supported Generic Board framework yet.

    Select SYS_GENERIC_BOARD in arch/Kconfig and delete all the macro
    defines in include/configs/*.h.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

20 Oct, 2015

1 commit

12 Oct, 2015

5 commits

  • 492f24e88   vexpress64: juno: use /dev/sda2 ... Browse Code »

    This patch changes the default "root=" parameter to "/dev/sda2".

    Many linux based distros use /dev/sda1 for their boot partition; this is
    often not a rootfs that can be used by the "root=" parameter.

    Linaro images use /dev/sda1 as a boot partition, although this of a
    different nature to a distro image. Linaro uses /dev/sda2 for the rootfs
    partition.

    Signed-off-by: Ryan Harkin
    Reviewed-by: Linus Walleij

    Ryan Harkin
     
  • ecbed5d6f   vexpress64: juno: add alternate kernel and device tree filenames ... Browse Code »

    The latest Juno firmware stores the files in NOR flash as "norkern" for
    kernel binary, "board.dtb" for the device tree binary.

    The "old" firmware used the name "Image" for the kernel binary and
    "juno" for the device tree binary.

    Rather than just change the default U-Boot configuration to use the new
    names, breaking users with the old firmware, attempt to load the default
    filename first. If that fails, attempt to load the alternate filename.

    I've echo'd that we are loading the alternate file to counter the
    output from "afs load" shown if the first load attempt fails. For
    example, I see output like this on my Juno board when it's configured
    the with the "old" firmware:

    image "norkern" not found in flash
    Loading Image instead of norkern
    loaded region 0 from 08500000 to 80000000, 00AB6318 bytes
    image "board.dtb" not found in flash
    Loading juno instead of board.dtb
    loaded region 0 from 0A000000 to 83000000, 00003188 bytes

    Signed-off-by: Ryan Harkin
    Reviewed-by: Linus Walleij

    Ryan Harkin
     
  • 4a6bdb59e   vexpress64: juno: add optional initrd ... Browse Code »

    Some OS images require an initrd on Juno.

    If the file ramdisk.img exists in NOR flash, then we load it and pass
    the address to the kernel. Otherwise, we pass the "-" parameter as
    before.

    Signed-off-by: Ryan Harkin
    Reviewed-by: Linus Walleij

    Ryan Harkin
     
  • 74e264b49   vexpress64: juno: add androidboot.hardware=juno ... Browse Code »

    Linaro's Juno Android builds requires the androidboot.hardware parameter
    be set to a know board name.

    Non-Android kernels ignore this extra parameter because they don't
    contain code to parse it.

    Signed-off-by: Ryan Harkin
    Reviewed-by: Linus Walleij

    Ryan Harkin
     
  • fc04b9235   vexpress64: fvp dram: add DRAM configuration ... Browse Code »
    12

    Create an additional FVP configuration to boot images pre-loaded into
    DRAM.

    Sometimes it's preferential to boot the model by loading the files
    directly into DRAM via model parameters, rather than using
    SemiHosting.

    An example of model parmaters that are used to pre-load the files
    into DRAM:
    --data cluster0.cpu0=Image@0x80080000 \
    --data cluster0.cpu0=fvp-base-gicv2-psci.dtb@0x83000000 \
    --data cluster0.cpu0=uInitrd@0x84000000

    Signed-off-by: Ryan Harkin
    Reviewed-by: Linus Walleij
    [trini: Update board/armltd/vexpress64/Kconfig logic]
    Signed-off-by: Tom Rini

    Ryan Harkin