08 Apr, 2017

2 commits


07 Apr, 2017

1 commit

  • The environment location is something that might change per board
    (depending on what storage options are availaible there) or depending on
    the user choice (when we have several options).

    Instead of hardcoding it in our configuration header, create a Kconfig
    choice with the options we use for now, and the symbols that depend on it.

    Once done, also remove the irrelevant sunxi defines.

    Signed-off-by: Maxime Ripard
    Reviewed-by: Tom Rini
    Reviewed-by: Jagan Teki

    Maxime Ripard
     

06 Apr, 2017

2 commits

  • The SPARC architecture is currently unmaintained, remove.

    Cc: Francois Retief
    Signed-off-by: Tom Rini

    Tom Rini
     
  • The architecture is currently unmaintained, remove.

    Cc: Benjamin Matthews
    Cc: Chong Huang
    Cc: Dimitar Penev
    Cc: Haitao Zhang
    Cc: I-SYST Micromodule
    Cc: M.Hasewinkel (MHA)
    Cc: Marek Vasut
    Cc: Martin Strubel
    Cc: Peter Meerwald
    Cc: Sonic Zhang
    Cc: Valentin Yakovenkov
    Cc: Wojtek Skulski
    Cc: Wojtek Skulski
    Signed-off-by: Tom Rini

    Tom Rini
     

13 Feb, 2017

1 commit

  • We repeated partial moves for CONFIG_SYS_NO_FLASH, but this is
    not completed. Finish this work by the tool.

    During this move, let's rename it to CONFIG_MTD_NOR_FLASH.
    Actually, we have more instances of "#ifndef CONFIG_SYS_NO_FLASH"
    than those of "#ifdef CONFIG_SYS_NO_FLASH". Flipping the logic will
    make the code more readable. Besides, negative meaning symbols do
    not fit in obj-$(CONFIG_...) style Makefiles.

    This commit was created as follows:

    [1] Edit "default n" to "default y" in the config entry in
    common/Kconfig.

    [2] Run "tools/moveconfig.py -y -r HEAD SYS_NO_FLASH"

    [3] Rename the instances in defconfigs by the following:
    find . -path './configs/*_defconfig' | xargs sed -i \
    -e '/CONFIG_SYS_NO_FLASH=y/d' \
    -e 's/# CONFIG_SYS_NO_FLASH is not set/CONFIG_MTD_NOR_FLASH=y/'

    [4] Change the conditionals by the following:
    find . -name '*.[ch]' | xargs sed -i \
    -e 's/ifndef CONFIG_SYS_NO_FLASH/ifdef CONFIG_MTD_NOR_FLASH/' \
    -e 's/ifdef CONFIG_SYS_NO_FLASH/ifndef CONFIG_MTD_NOR_FLASH/' \
    -e 's/!defined(CONFIG_SYS_NO_FLASH)/defined(CONFIG_MTD_NOR_FLASH)/' \
    -e 's/defined(CONFIG_SYS_NO_FLASH)/!defined(CONFIG_MTD_NOR_FLASH)/'

    [5] Modify the following manually
    - Rename the rest of instances
    - Remove the description from README
    - Create the new Kconfig entry in drivers/mtd/Kconfig
    - Remove the old Kconfig entry from common/Kconfig
    - Remove the garbage comments from include/configs/*.h

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

26 Jan, 2017

4 commits


24 Jan, 2017

1 commit


21 Jan, 2017

1 commit


04 Dec, 2016

1 commit


28 Oct, 2016

1 commit


26 Oct, 2016

1 commit


24 Oct, 2016

7 commits


12 Oct, 2016

2 commits


20 Sep, 2016

1 commit


17 Sep, 2016

1 commit


10 Sep, 2016

1 commit


07 Sep, 2016

1 commit


22 Jul, 2016

1 commit


02 Jul, 2016

2 commits

  • As the help message of CONFIG_BOOTDELAY says, CONFIG_BOOTDELAY=-2
    means the autoboot with no delay, with no abort check even if
    CONFIG_ZERO_BOOTDELAY_CHECK is defined.

    To sum up, the autoboot behaves as follows:

    [1] CONFIG_BOOTDELAY=0 && CONFIG_ZERO_BOOTDELAY_CHECK=y
    autoboot with no delay, but you can abort it by key input

    [2] CONFIG_BOOTDELAY=0 && CONFIG_ZERO_BOOTDELAY_CHECK=n
    autoboot with no delay, with no check for abort

    [3] CONFIG_BOOTDELAY=-1
    disable autoboot

    [4] CONFIG_BOOTDELAY=-2
    autoboot with no delay, with no check for abort

    As you notice, [2] and [4] come to the same result, which means we
    do not need CONFIG_ZERO_BOOTDELAY_CHECK. We can control all the
    cases only by CONFIG_BOOTDELAY, like this:

    [1] CONFIG_BOOTDELAY=0
    autoboot with no delay, but you can abort it by key input

    [2] CONFIG_BOOTDELAY=-1
    disable autoboot

    [3] CONFIG_BOOTDELAY=-2
    autoboot with no delay, with no check for abort

    This commit converts the logic as follow:
    CONFIG_BOOTDELAY=0 && CONFIG_ZERO_BOOTDELAY_CHECK=n
    --> CONFIG_BOOTDELAY=-2

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Stefan Roese
    Acked-by: Igor Grinberg
    Reviewed-by: Simon Glass
    Acked-by: Vladimir Zapolskiy
    Reviewed-by: Heiko Schocher
    Acked-by: Christian Riesch
    Acked-by: Hannes Schmelzer

    Masahiro Yamada
     
  • The same information now exists in common/Kconfig. Do not duplicate
    documentation from the point of view of maintainability.

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Simon Glass
    Reviewed-by: Heiko Schocher

    Masahiro Yamada
     

28 Jun, 2016

2 commits

  • Add CONFIG_{SD|NAND|ONENAND|SPI|QSPI|SATA}_BOOT kconfig entries.

    SoCs supports loading U-Boot from different medias to DRAM, such as
    i.MX6/7 supports loading U-Boot to DRAM from sd/emmc/nand/qspi/spi/sata
    and etc. For i.MX, imximage will generate different IVT headers according
    to boot medias.

    Signed-off-by: Peng Fan
    Cc: Simon Glass
    Cc: Heiko Schocher
    Cc: Joe Hershberger
    Cc: Bin Meng
    Cc: Christophe Ricard
    Cc: Nikita Kiryanov
    Cc: Francois Retief
    Cc: Tom Rini

    Peng Fan
     
  • Not only am335x supports booting from NOR, i.MX6 SoCs also
    supports booting from NOR. Make NOR_BOOT a common
    option to let different SoCs share it.

    Signed-off-by: Peng Fan
    Cc: Simon Glass
    Cc: Heiko Schocher
    Cc: Joe Hershberger
    Cc: Christophe Ricard
    Cc: Bin Meng
    Cc: Francois Retief
    Cc: Tom Rini
    Reviewed-by: Simon Glass

    Peng Fan
     

20 Jun, 2016

1 commit

  • Since commit bb597c0eeb7e ("common: bootdelay: move CONFIG_BOOTDELAY
    into a Kconfig option"), CONFIG_BOOTDELAY is defined for all boards.

    Prior to that commit, it was allowed to unset CONFIG_BOOTDELAY to
    not compile common/autoboot.c, as described in common/Makefile:

    # This option is not just y/n - it can have a numeric value
    ifdef CONFIG_BOOTDELAY
    obj-y += autoboot.o
    endif

    It was a bit odd to enable/disable code with an integer type option,
    but it was how this option worked before that commit, and several
    boards actually unset it to opt out of the autoboot feature.

    This commit adds a new bool option, CONFIG_AUTOBOOT, and makes
    CONFIG_BOOTDELAY depend on it.

    I chose "default y" for this option because most boards use the
    autoboot. I added "# CONFIG_AUTOBOOT is not set" for the boards that
    had not set CONFIG_BOOTDELAY prior to the bad commit.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

17 Jun, 2016

1 commit


10 Jun, 2016

1 commit


25 Jan, 2016

1 commit

  • There are a lot of unrelated files in common, including all of the commands.
    Moving them into their own directory makes them easier to find and is more
    logical.

    Some commands include non-command code, such as cmd_scsi.c. This should be
    sorted out at some point so that the function can be enabled with or without
    the associated command.

    Unfortunately, with m68k I get this error:

    m68k: + M5329AFEE
    +arch/m68k/cpu/mcf532x/start.o: In function `_start':
    +arch/m68k/cpu/mcf532x/start.S:159:(.text+0x452): relocation truncated to fit: R_68K_PC16 against symbol `board_init_f' defined in .text.board_init_f section in common/built-in.o

    I hope someone can shed some light on what this means. I hope it isn't
    depending on the position of code in the image.

    Signed-off-by: Simon Glass
    Reviewed-by: Bin Meng
    Reviewed-by: Heiko Schocher
    Acked-by: Stefan Roese
    Acked-by: Przemyslaw Marczak

    Simon Glass
     

14 Jan, 2016

1 commit

  • Add a 'poweroff' command to boot commands, this only gets enabled if the
    board Kconfig does a "select CMD_POWEROFF".

    Signed-off-by: Michael van Slingerland
    [hdegoede@redhat.com: Make the cmd conditional on a CMD_POWEROFF Kconfig]
    Signed-off-by: Hans de Goede

    Michael van Slingerland
     

20 Nov, 2015

1 commit

  • It is useful to be able to record console output and provide console input
    via a buffer. This provides sandbox with the ability to run a command and
    check its output. If the console is set to silent then no visible output
    is generated.

    This also provides a means to fix the problem where tests produce unwanted
    output, such as errors or warnings. This can be confusing. We can instead
    set the console to silent and record this output. It can be checked later
    in the test if required.

    It is possible that this may prove useful for non-test situations. For
    example the console output may be suppressed for normal operations, but
    recorded and stored for access by the OS. That feature is not implemented
    at present.

    Signed-off-by: Simon Glass

    Simon Glass
     

19 Nov, 2015

1 commit