1. 08 Aug, 2018 1 commit
    • Ye Li's avatar
      MLK-19132-2 fastboot: Disable BCB_SUPPORT config at default · 06de519a
      Ye Li authored
      The BCB_SUPPORT is not needed by fastboot to support uuu, change it to
      disabled at default. Android header file explicitly enables this
      config, so there is no impact to android.
      
      Also remove the CONFIG_BCB_SUPPORT from whilelist, since we already add
      it in kconfig.
      Signed-off-by: default avatarYe Li <ye.li@nxp.com>
      (cherry picked from commit 36fd8fd0d5f34d69ef9a1a3833f3f052d64a25b3)
      06de519a
  2. 04 Jul, 2018 1 commit
    • Yu Shan's avatar
      [iot] Check Trusty OS available before load it · 0a8e4589
      Yu Shan authored
      When SECURE_BOOT enabled, use HAB verify
      Trusty OS image or check its IVT available.
      
      If not available, bootloader consider the TOS
      lost unexpected and wipe all data on disk.
      Then enter limited fastboot mode. In this situation
      only bootloader and tos is able to flash, gpt won't
      be available for external.
      
      Change-Id: I04f037f5bd5a51f53174b5b99b2c3053182a8fcf
      Signed-off-by: default avatarHaoran.Wang <elven.wang@nxp.com>
      0a8e4589
  3. 26 Jun, 2018 2 commits
  4. 15 Jun, 2018 1 commit
  5. 16 May, 2018 2 commits
    • Frank Li's avatar
      MLK-18257-2: fix fastboot build warning · d5226a3a
      Frank Li authored
      cmd/fastboot.c: In function ‘do_fastboot’:
      cmd/fastboot.c:19:8: warning: unused variable ‘usb_controller’ [-Wunused-variable]
      
      drivers/usb/gadget/f_fastboot.c: In function ‘fastboot_setup’:
      drivers/usb/gadget/f_fastboot.c:1620:2: warning: ‘serialnr.high’ is used uninitialized in this function [-Wuninitialized]
        sprintf(serial, "%08x%08x", serialnr.high, serialnr.low);
        ^
      drivers/usb/gadget/f_fastboot.c:1620:2: warning: ‘serialnr.low’ is used uninitialized in this function [-Wuninitialized]
      Signed-off-by: default avatarFrank Li <Frank.Li@nxp.com>
      d5226a3a
    • Frank Li's avatar
      MLK-18257-1 Enable fastboot support in qxp mek board · 719651a4
      Frank Li authored
      Signed-off-by: default avatarFrank Li <Frank.Li@nxp.com>
      719651a4
  6. 03 May, 2018 2 commits
  7. 02 Apr, 2018 3 commits
  8. 28 Mar, 2018 1 commit
  9. 08 Dec, 2017 1 commit
  10. 30 Nov, 2017 1 commit
  11. 02 Nov, 2017 3 commits
  12. 18 May, 2017 1 commit
  13. 05 Apr, 2017 3 commits
    • Adrian Alonso's avatar
      MLK-13130: configs: mx6qarm2: android lpddr2 pop support · 41a5d287
      Adrian Alonso authored
      Add Android support for mx6qarm2 lpddr2 pop target
      Signed-off-by: default avatarAdrian Alonso <adrian.alonso@nxp.com>
      (cherry picked from commit 6356f2b420f3571493755f6b3a307a66a539b60c)
      41a5d287
    • Ye Li's avatar
      MLK-12527-2 android: Add FSL android fastboot support · d0d678fd
      Ye Li authored
      Integrate the FSL android fastboot features into community's fastboot.
      
      1. Use USB gadget g_dnl driver
      2. Integrate the FSL SD/SATA/NAND flash operations, since the GPT and
         EFI partitions are not support by i.MX.
      3. Add FDT support to community's android image.
      4. Add a new boot command "boota" for android image boot. The boota
         implements to load ramdisk and fdt to their loading addresses
         specified in boot.img header, while bootm won't do it for android image.
      5. Support the authentication of boot.img at the "load_addr" for
         both SD and NAND.
      6. We use new configuration CONFIG_FSL_FASTBOOT for Freescale's fastboot
         with relevant header file "fsl_fastboot.h". While disabling the
         configuration, the community fastboot is used.
      7. Overwrite the cmdline in boot.img by using bootargs saved in local environment.
      8. Add recovery and reboot-bootloader support.
      Signed-off-by: default avatarYe Li <ye.li@nxp.com>
      (cherry picked from commit 23d63ff185929fff5e392efc853d69b606ba081a)
      d0d678fd
    • Ye Li's avatar
      MLK-12500-1 HAB: Add kernel image authentication in image loading · fd9a9759
      Ye Li authored
      To support the trust boot chain, we integrate the authentication
      into the kernel image loading process. The kernel image will be verified
      at its load address. So when signing the kernel image, we need to
      use this load address which may change on different platforms.
      Signed-off-by: default avatarYe Li <ye.li@nxp.com>
      (cherry picked from commit 3c118b8d6bbe1a25ca8c8bafeb528309f16fc73d)
      fd9a9759
  14. 12 Feb, 2017 1 commit
    • Masahiro Yamada's avatar
      flash: complete CONFIG_SYS_NO_FLASH move with renaming · e856bdcf
      Masahiro Yamada authored
      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: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      e856bdcf
  15. 08 Feb, 2017 4 commits
    • Masahiro Yamada's avatar
      cmd: move CONFIG_CMD_UNZIP and CONFIG_CMD_ZIP to Kconfig · e9d33e73
      Masahiro Yamada authored
      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: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Acked-by: default avatarMichal Simek <michal.simek@xilinx.com>
      Acked-by: default avatarStefan Roese <sr@denx.de>
      Acked-by: default avatarRyan Harkin <ryan.harkin@linaro.org>
      Tested-by: default avatarRyan Harkin <ryan.harkin@linaro.org>
      e9d33e73
    • Grygorii Strashko's avatar
      cmd: bootm: fix build when CONFIG_CMD_IMLS_NAND · dbe7881d
      Grygorii Strashko authored
      Now when CONFIG_CMD_IMLS_NAND is enabled the u-boot build will fail,
      because nand_read_skip_bad() function has been changed to accept more
      parameters, hence fix it.
      
       CC      cmd/bootm.o
      cmd/bootm.c: In function 'nand_imls_legacyimage':
      cmd/bootm.c:390:8: error: too few arguments to function 'nand_read_skip_bad'
        ret = nand_read_skip_bad(mtd, off, &len, imgdata);
              ^
      In file included from cmd/bootm.c:18:0:
      include/nand.h:101:5: note: declared here
       int nand_read_skip_bad(struct mtd_info *mtd, loff_t offset, size_t *length,
           ^
       LD      drivers/block/built-in.o
      Signed-off-by: default avatarGrygorii Strashko <grygorii.strashko@ti.com>
      Reviewed-by: default avatarTom Rini <trini@konsulko.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      dbe7881d
    • Masahiro Yamada's avatar
      cmd: rework "license" command · d726f225
      Masahiro Yamada authored
      The previous commit ("add a new command to show .config contents")
      improves the basic infrastructure of "embed a compressed file into
      the U-Boot image, and print it by a command".  The same pattern for
      the "license" command.
      
      This commit reworks the command to improve the following:
      
      [1] Improve log style
      
      Kbuild style log
      
        GZIP    cmd/license_data.gz
        CHK     cmd/license_data_gz.h
        UPD     cmd/license_data_gz.h
        CHK     cmd/license_data_size.h
        UPD     cmd/license_data_size.h
      
      instead of the bare Make log:
      
      cat ./Licenses/gpl-2.0.txt | gzip -9 -c | \
      		tools/bin2header license_gzip > ./include/license.h
      
      [2] Collect related code into the "cmd" directory
      
      Prior to this commit, the license.h was created by tools/Makefile,
      placed under the "include" directory, included from cmd/license.c,
      and deleted by the top-level Makefile.  It is not a good idea to
      scatter related code.
      
      [3] Drop the fixed-malloc size LICENSE_MAX
      
      Just allocate the minimum required size of buffer because we know
      the size of the original gpl-2.0.txt.
      
      [4] Fix more issues
      
      Terminate the buffer with zero to prevent puts() from over-running.
      Add "static" to do_license.
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      d726f225
    • Masahiro Yamada's avatar
      cmd: add a new command "config" to show .config contents · 61304dbe
      Masahiro Yamada authored
      This feature is inspired by /proc/config.gz of Linux.  In Linux,
      if CONFIG_IKCONFIG is enabled, the ".config" file contents are
      embedded in the kernel image.  If CONFIG_IKCONFIG_PROC is also
      enabled, the ".config" contents are exposed to /proc/config.gz.
      Users can do "zcat /proc/config.gz" to check which config options
      are enabled on the running kernel image.
      
      The idea is almost the same here; if CONFIG_CMD_CONFIG is enabled,
      the ".config" contents are compressed and saved in the U-Boot image,
      then printed by the new command "config".
      
      The usage is quite simple.  Enable CONFIG_CMD_CONFIG, then run
       > config
      from the command line interface.  The ".config" contents will be
      printed on the console.
      
      This feature increases the U-Boot image size by about 4KB (this is
      mostly due to the gzip-compressed .config file).  By default, it is
      enabled only for Sandbox because we do not care about the memory
      footprint on it.  Of course, this feature is architecture agnostic,
      so you can enable it on any board if the image size increase is
      acceptable for you.
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      61304dbe
  16. 01 Feb, 2017 1 commit
  17. 28 Jan, 2017 5 commits
  18. 26 Jan, 2017 1 commit
  19. 25 Jan, 2017 1 commit
    • Konstantin Porotchkin's avatar
      arm64: mvebu: Update bubt command MMC block device access · e559ef1a
      Konstantin Porotchkin authored
      Update the MMC block device access code in bubt command
      implementation according to the latest MMC driver changes.
      
      Change-Id: Ie852ceefa0b040ffe1362bdb7815fcea9b2d923b
      Signed-off-by: default avatarKonstantin Porotchkin <kostap@marvell.com>
      Cc: Stefan Roese <sr@denx.de>
      Cc: Nadav Haklai <nadavh@marvell.com>
      Cc: Neta Zur Hershkovits <neta@marvell.com>
      Cc: Omri Itach <omrii@marvell.com>
      Cc: Igal Liberman <igall@marvell.com>
      Cc: Haim Boot <hayim@marvell.com>
      Cc: Hanna Hawa <hannah@marvell.com>
      e559ef1a
  20. 24 Jan, 2017 1 commit
  21. 21 Jan, 2017 1 commit
    • Uri Mashiach's avatar
      status_led: Kconfig migration · 2d8d190c
      Uri Mashiach authored
      Move all of the status LED feature to drivers/led/Kconfig.
      The LED status definitions were moved from the board configuration
      files to the defconfig files.
      
      TBD: Move all of the definitions in the include/status_led.h to the
      relevant board's defconfig files.
      
      Tested boards: CL-SOM-AM57x, CM-T335
      Signed-off-by: default avatarUri Mashiach <uri.mashiach@compulab.co.il>
      2d8d190c
  22. 20 Jan, 2017 3 commits
    • Emmanuel Vadot's avatar
      bootm: qnx: Disable data cache before booting QNX image · 995eab8b
      Emmanuel Vadot authored
      Instead of disabling the data cache in the bootelf command, disabling
      it in the do_bootm_qnxelf function.
      Some ELF binary might want the cache enabled.
      Signed-off-by: default avatarEmmanuel Vadot <manu@bidouilliste.com>
      995eab8b
    • Sébastien Szymanski's avatar
    • Rick Altherr's avatar
      bootm: relocate ramdisk if CONFIG_SYS_BOOT_RAMDISK_HIGH set · c2e7e72b
      Rick Altherr authored
      In 35fc84fa, bootm was refactored so plain 'bootm' and
      'bootm <subcommand>' shared a common implementation.
      The 'bootm ramdisk' command implementation is now part of the common
      implementation but not invoke by plain 'bootm' since the original
      implementation never did ramdisk relocation.  Instead, ramdisk
      relocation happened in image_setup_linux() which is typically called
      during the OS portion of 'bootm'.
      
      On ARM, parameters to the Linux kernel can either be passed by FDT or
      ATAGS. When using FDT, image_setup_linux() is called which also triggers
      ramdisk relocation.  When using ATAGS, image_setup_linux() is _not_
      called because it mostly does FDT setup.
      
      Instead of calling image_setup_linux() in both FDT and ATAGS cases,
      include BOOTM_STATE_RAMDISK in the requested states during a plain
      'bootm' if CONFIG_SYS_BOOT_RAMDISK_HIGH is set and remove the ramdisk
      relocation from image_setup_linux().  This causes ramdisk relocation to
      happen on any system where CONFIG_SYS_BOOT_RAMDISK_HIGH regardless of
      the OS being booted. Also remove IMAGE_ENABLE_RAMDISK_HIGH as it was
      only used by the now-removed code from image_setup_linux().
      Signed-off-by: default avatarRick Altherr <raltherr@google.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: default avatarJoel Stanley <joel@jms.id.au>
      c2e7e72b