Eric Lee / smarc-uboot

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
     

11 Oct, 2017

1 commit

  • ad12dc184   cmd: Toggle the default value of CONFIG_CMD_IMLS ... Browse Code »

    Having this as a 'default y' is rather annoying because it doesn't
    actually compile unless other options are defined in the board header:

    ../cmd/bootm.c: In function 'do_imls_nor':
    ../cmd/bootm.c:330:7: error: 'CONFIG_SYS_MAX_FLASH_BANKS' undeclared (first use in this function); did you mean 'CONFIG_SYS_MAX_FLASH_SECT'?
    i < CONFIG_SYS_MAX_FLASH_BANKS; ++i, ++info) {

    Make it 'default n' so people who develop new boards that start from a
    blank defconfig have one less compilation failure to debug.

    Signed-off-by: Tuomas Tynkkynen

    Tuomas Tynkkynen
     

15 Aug, 2017

1 commit

12 Aug, 2017

1 commit

09 Aug, 2017

1 commit

08 Aug, 2017

1 commit

10 Mar, 2017

1 commit

  • 285226785   Freescale/NXP: Migrate CONFIG_FSL_CAAM to defconfigs ... Browse Code »

    In some cases this is absolutely required, so select this for some secure
    features. This also requires migration of RSA_FREESCALE_EXP

    Cc: Ruchika Gupta
    Cc: Poonam Aggrwal
    Cc: Naveen Burmi
    Cc: Po Liu
    Cc: Shengzhou Liu
    Cc: Priyanka Jain
    Cc: Sumit Garg
    Cc: Shaohui Xie
    Cc: Chunhe Lan
    Cc: Feng Li
    Cc: Alison Wang
    Cc: Mingkai Hu
    Cc: York Sun
    Cc: Saksham Jain
    Cc: Prabhakar Kushwaha
    Signed-off-by: Tom Rini

    Tom Rini
     

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
     

26 Jan, 2017

1 commit

24 Jan, 2017

1 commit

22 Jan, 2017

1 commit

30 Dec, 2016

1 commit

03 Dec, 2016

1 commit

17 Sep, 2016

1 commit

10 Sep, 2016

1 commit

09 Sep, 2016

1 commit

10 Jun, 2016

1 commit

26 Apr, 2016

3 commits

15 Mar, 2016

3 commits

  • 73223f0e1   Kconfig: Move CONFIG_FIT and related options to Kconfig ... Browse Code »

    There are already two FIT options in Kconfig but the CONFIG options are
    still in the header files. We need to do a proper move to fix this.

    Move these options to Kconfig and tidy up board configuration:

    CONFIG_FIT
    CONFIG_OF_BOARD_SETUP
    CONFIG_OF_SYSTEM_SETUP
    CONFIG_FIT_SIGNATURE
    CONFIG_FIT_BEST_MATCH
    CONFIG_FIT_VERBOSE
    CONFIG_OF_STDOUT_VIA_ALIAS
    CONFIG_RSA

    Unfortunately the first one is a little complicated. We need to make sure
    this option is not enabled in SPL by this change. Also this option is
    enabled automatically in the host builds by defining CONFIG_FIT in the
    image.h file. To solve this, add a new IMAGE_USE_FIT #define which can
    be used in files that are built on the host but must also build for U-Boot
    and SPL.

    Note: Masahiro's moveconfig.py script is amazing.

    Signed-off-by: Simon Glass
    [trini: Add microblaze change, various configs/ re-applies]
    Signed-off-by: Tom Rini

    Simon Glass
     
  • 69e173eb5   Move CONFIG_OF_LIBFDT to Kconfig ... Browse Code »
    66

    Move this option to Kconfig and tidy up existing boards.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • 9e971632c   freescale: Remove CONFIG_DM from header files ... Browse Code »

    Kconfig options must defined in the defconfig files. Since RSA_SOFTWARE_EXP
    relies on CONFIG_DM, unless it is set in kconfig we cannot enable RSA.
    Remove the hacks which enable CONFIG_DM in header files and update the
    defconfig.

    Signed-off-by: Simon Glass

    Simon Glass
     

25 Nov, 2015

2 commits

22 Nov, 2015

1 commit

22 Aug, 2015

2 commits

31 Jul, 2015

1 commit

  • 467a40dfe   powerpc/mpc85xx: SECURE BOOT- NAND secure boot target for P3041 ... Browse Code »
    29

    Secure Boot Target is added for NAND for P3041.
    For mpc85xx SoCs, the core begins execution from address 0xFFFFFFFC.
    In case of secure boot, this default address maps to Boot ROM.
    The Boot ROM code requires that the bootloader(U-boot) must lie
    in 0 to 3.5G address space i.e. 0x0 - 0xDFFFFFFF.

    In case of NAND Secure Boot, CONFIG_SYS_RAMBOOT is enabled and CPC is
    configured as SRAM. U-Boot binary will be located on SRAM configured
    at address 0xBFF00000.
    In the U-Boot code, TLB entries are created to map the virtual address
    0xFFF00000 to physical address 0xBFF00000 of CPC configured as SRAM.

    Signed-off-by: Saksham Jain
    Signed-off-by: Ruchika Gupta
    Signed-off-by: Aneesh Bansal
    Reviewed-by: York Sun

    Aneesh Bansal