Eric Lee / smarc-uboot

20 Mar, 2017

1 commit

13 Feb, 2017

1 commit

  • e856bdcfb   flash: complete CONFIG_SYS_NO_FLASH move with renaming ... Browse Code »
    20

    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
     

04 Dec, 2016

1 commit

  • 3337e3af5   Enable DISTRO_DEFAULT on platforms that missed it before ... Browse Code »
    20

    A number of platforms had been using the distro default feature before
    it was moved to Kconfig but did not enable the new Kconfig option when
    it was enabled. This caused a regression in terms of features and this
    introduces breakage when more things move to Kconfig.

    Signed-off-by: Tom Rini

    Tom Rini
     

12 Oct, 2016

2 commits

07 Oct, 2016

1 commit

  • 03ab5d136   vexpress: disable cci ace slave ports when booting in non-sec/hyp mode ... Browse Code »

    Commit f225d39d3093 ("vexpress: Check TC2 firmware support before defaulting
    to nonsec booting") added support to check if the firmware on TC2 is
    configured appropriately before booting in nonsec/hyp mode.

    However when booting in non-secure/hyp mode, CCI control must be done in
    secure firmware and can't be done in non-secure/hyp mode. In order to
    ensure that, this patch disables the cci slave port inteface so that it
    is not accessed at all.

    Cc: Jon Medhurst
    Acked-by: Marc Zyngier
    Signed-off-by: Sudeep Holla
    Acked-by: Jon Medhurst
    Tested-by: Jon Medhurst

    Sudeep Holla
     

09 Sep, 2016

1 commit

17 Jun, 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

3 commits

15 Mar, 2016

1 commit

26 Jun, 2015

1 commit

01 Jun, 2015

1 commit

30 Jul, 2014

1 commit

  • dd84058d2   kconfig: add board Kconfig and defconfig files ... Browse Code »

    This commit adds:
    - arch/${ARCH}/Kconfig
    provide a menu to select target boards
    - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
    set CONFIG macros to the appropriate values for each board
    - configs/${TARGET_BOARD}_defconfig
    default setting of each board

    (This commit was automatically generated by a conversion script
    based on boards.cfg)

    In Linux Kernel, defconfig files are located under
    arch/${ARCH}/configs/ directory.
    It works in Linux Kernel since ARCH is always given from the
    command line for cross compile.

    But in U-Boot, ARCH is not given from the command line.
    Which means we cannot know ARCH until the board configuration is done.
    That is why all the "*_defconfig" files should be gathered into a
    single directory ./configs/.

    Signed-off-by: Masahiro Yamada
    Acked-by: Simon Glass

    Masahiro Yamada