Eric Lee / smarc-uboot

10 Jan, 2018

1 commit

  • cfb8462aa   ARM: Drop unreferenced CONFIG_MACH_* defines ... Browse Code »

    These macros are all defined once and never checked or used anywhere:

    CONFIG_MACH_ASPENITE
    CONFIG_MACH_DAVINCI_CALIMAIN
    CONFIG_MACH_DOCKSTAR
    CONFIG_MACH_EDMINIV2
    CONFIG_MACH_GOFLEXHOME
    CONFIG_MACH_GONI
    CONFIG_MACH_GURUPLUG
    CONFIG_MACH_KM_KIRKWOOD
    CONFIG_MACH_OPENRD_BASE
    CONFIG_MACH_SHEEVAPLUG

    Almost all of them were only used for the mach_is_foo() logic in
    arch/arm/asm/mach-types.h that were dropped in
    commit f9dadaef8b75fa ("arm: Re-sync asm/mach-types.h with
    Linux Kernel v4.9")

    Signed-off-by: Tuomas Tynkkynen

    Tuomas Tynkkynen
     

06 Nov, 2017

1 commit

26 Jul, 2017

1 commit

  • 2be296538   Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig ... Browse Code »
    20

    This converts the following to Kconfig:
    CONFIG_ENV_IS_IN_MMC
    CONFIG_ENV_IS_IN_NAND
    CONFIG_ENV_IS_IN_UBI
    CONFIG_ENV_IS_NOWHERE

    In fact this already exists for sunxi as a 'choice' config. However not
    all the choices are available in Kconfig yet so we cannot use that. It
    would lead to more than one option being set.

    In addition, one purpose of this series is to allow the environment to be
    stored in more than one place. So the existing choice is converted to a
    normal config allowing each option to be set independently.

    There are not many opportunities for Kconfig updates to reduce the size of
    this patch. This was tested with

    ./tools/moveconfig.py -i CONFIG_ENV_IS_IN_MMC

    And then manual updates. This is because for CHAIN_OF_TRUST boards they
    can only have ENV_IS_NOWHERE set, so we enforce that via Kconfig logic
    now.

    Signed-off-by: Simon Glass
    Signed-off-by: Tom Rini

    Simon Glass
     

23 May, 2017

1 commit

  • fc843a02a   Kconfig: Add a CONFIG_IDE option ... Browse Code »

    At present IDE support is controlled by CONFIG_CMD_IDE. Add a separate
    CONFIG_IDE option so that IDE support can be enabled without requiring
    the 'ide' command.

    Update existing users and move the ide driver into drivers/block since
    it should not be in common/.

    Signed-off-by: Simon Glass

    Simon Glass
     

31 Jan, 2017

1 commit

  • 54925327f   mmc: move CONFIG_GENERIC_MMC to Kconfig ... Browse Code »
    40

    Now, CONFIG_GENERIC_MMC seems equivalent to CONFIG_MMC.

    Let's create an entry for "config GENERIC_MMC" with "default MMC",
    then convert all macro defines in headers to Kconfig. Almost all
    of the defines will go away.

    I see only two exceptions:
    configs/blanche_defconfig
    configs/sandbox_noblk_defconfig

    They define CONFIG_GENERIC_MMC, but not CONFIG_MMC. Something
    might be wrong with these two boards, so should be checked later.

    Anyway, this is the output of the moveconfig tool.

    This commit was created as follows:

    [1] create a config entry in drivers/mmc/Kconfig

    [2] tools/moveconfig.py -r HEAD GENERIC_MMC

    [3] manual clean-up of garbage comments in doc/README.* and
    include/configs/*.h

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Tom Rini

    Masahiro Yamada
     

28 Jan, 2017

1 commit

30 Dec, 2016

1 commit

  • c27269953   mmc: complete unfinished move of CONFIG_MMC ... Browse Code »
    26

    Commit 7a777f6d6f35 ("mmc: Add generic Kconfig option") created
    a Kconfig entry for this option without any actual moves, then
    commit 44c798799f66 ("sunxi: Use Kconfig CONFIG_MMC") moved
    instances only for SUNXI.

    We generally do not like such partial moves. This kind of work
    is automated by tools/moveconfig.py, so it is pretty easy to
    complete this move.

    I am adding "default ARM || PPC || SANDBOX" (suggested by Tom).
    This shortens the configs and will ease new board porting.

    This commit was created as follows:

    [1] Edit Kconfig (remove the "depends on", add the "default",
    copy the prompt and help message from Linux)

    [2] Run 'tools/moveconfig.py -y -s -r HEAD MMC'

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Jaehoon Chung

    Masahiro Yamada
     

20 Sep, 2016

1 commit

26 Apr, 2016

2 commits

24 Mar, 2016

1 commit

  • 371b9e9c3   ARM: sheevaplug: correct nand partition layout ... Browse Code »

    Commit 1e3d640316 (ARM: sheevaplug: redefine MTDPARTS) changed the partition
    layout (without any description why), but didn't change the offset/size to
    load the kernel from or the root=/dev/mtdblockX in the bootargs.

    The 3MB forseen for a kernel is furthermore too little. A 4.4 build of
    mvebu_v5_defconfig is 3.6MB:

    -rw-r--r-- 1 peko peko 3.6M Jan 16 20:24 uImage.kirkwood-sheevaplug

    When device tree support for sheevaplug was added to the kernel in commit
    ee514b381e (ARM: Kirkwood: Add dts files for Sheevaplug and eSATA
    Sheevaplug) a default flash partition layout (used if mtdparts= isn't passed
    on the command line / CONFIG_MTD_CMDLINE_PARTS isn't enabled) with 1MB for
    u-boot / environment, 4MB for the kernel and the rest for the rootfs, so use
    that layout here and adjust the kernel loading to match.

    Signed-off-by: Peter Korsgaard
    Signed-off-by: Stefan Roese

    Peter Korsgaard
     

15 Mar, 2016

3 commits

18 Nov, 2015

4 commits

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
     

26 Jun, 2015

1 commit

07 Feb, 2015

3 commits

26 Jan, 2015

1 commit

01 Oct, 2014

5 commits

31 Aug, 2014

1 commit

01 Aug, 2014

1 commit

24 Jul, 2013

1 commit

13 Oct, 2010

1 commit

  • 54e999a30   kirkwood: added common config file mv-common.h ... Browse Code »

    It is observed that, in most of the board configs the code is being
    duplicated, also for any common change all board files needs update
    This issue was under discussion from long on mailing list and we
    converge on introducing common config file.

    With this patch-
    1. Total Kirkwood specific configuration code is reduced by 210 lines
    2. All common configuration can be shared by multiple boards
    3. Easy to manage common updates like ARM relocation changes

    mv-common.h file is added to include/configs/
    It contains all common configuration supported for all Kirkwood boards
    The respective board configs are updated for its usage

    Build tested for guruplug, mv88f6281gtw_ge, openrd_base,
    rd6281a and sheevaplug
    Binary execution tested for sheevaplug

    Todo:
    1. Other custom Kirkwood boards to be synced
    2. The support to be extended for Orion5X based boards

    Signed-off-by: Prafulla Wadaskar

    Prafulla Wadaskar
     

13 Jul, 2010

1 commit

30 Apr, 2010

1 commit

  • 5414fec85   configs/sheevaplug: added a few additional commands ... Browse Code »

    This patch includes a few additional commands in the sheevaplug
    version of u-boot:
    - support for LONGHELP so you can get help messages
    - auto completion and command editing
    - ubi and mii support
    - ext2 filesystem (convenient if you have an ext2 from which you want to boot)
    - jffs2 and ubifs filesystems (if you want to use these in NAND)

    This also makes it more similar to openrd client.

    Side effect of this patch is that the code now needs 3 sectors i.s.o. 2
    so an existing env is overwritten

    Signed-off-by: Frans Meulenbroeks

    Frans Meulenbroeks
     

09 Dec, 2009

1 commit

10 Aug, 2009

1 commit

19 Jul, 2009

1 commit

  • 55dd4ba54   Marvell Sheevaplug Board support ... Browse Code »

    Reference:
    http://plugcomputer.org/
    http://openplug.org/plugwiki/index.php/Das_U-boot_plug_support

    This patch is tested for-
    1. Boot from DRAM/NAND flash
    2. File transfer using tftp
    3. NAND flash read/write/erase
    4. Linux kernel and RFS Boot from NAND
    5. Enabled USB PHY init for kernel need
    6. Boot from USB supported

    Note: to boot Kirkwood kernel with USB support,
    you should add "usb start" in the boot sequence

    Signed-off-by: Prafulla Wadaskar

    Prafulla Wadaskar