1. 08 4月, 2017 6 次提交
    • A
      ti_armv7_common: env: Use args_mmc in FIT loading path · 5bb7318f
      Andrew F. Davis 提交于
      The env command 'args_fit' does not define a root path, this forces us to
      embed the rootfs into the FIT image. FIT images do not need to contain a
      rootfs, when they do not the kernel will fall-back to the kernel argument
      'root', if this is not defined the kernel will not boot. It is safe to
      add this as when we do have the rootfs in FIT this argument is ignored.
      As 'loadfit' is only called from the MMC boot path, use 'args_mmc' to
      correctly populate 'bootargs'.
      Signed-off-by: NAndrew F. Davis <afd@ti.com>
      Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
      5bb7318f
    • F
      Apparent conflict between CONFIG_BLK and CONFIG_API · f2288c5a
      fuz@fuz.su 提交于
      Good evening,
      
      I am trying to port FreeBSD to the ASUS Tinker Board, a computer based
      on the Rockchip 3288 SoC. FreeBSD's boot loader (named loader(8)) needs
      CONFIG_API to be enabled, but trying to build an U-Boot from trunk with
      both CONFIG_API and CONFIG_BLK (as required for Rockchip SoC's?) leads
      to the following build failure:
      
      $ CROSS_COMPILE=arm-none-eabi- gmake tinker-rk3288_defconfig all
      ...
        CC      api/api_storage.o
      api/api_storage.c: In function 'dev_read_stor':
      api/api_storage.c:334:9: error: 'struct blk_desc' has no member named 'block_read'
        if ((dd->block_read) == NULL) {
               ^~
      api/api_storage.c:339:11: error: 'struct blk_desc' has no member named 'block_read'
        return dd->block_read(dd, start, len, buf);
                 ^~
      api/api_storage.c:340:1: warning: control reaches end of non-void function [-Wreturn-type]
       }
       ^
      gmake[2]: *** [scripts/Makefile.build:281: api/api_storage.o] Fehler 1
      gmake[1]: *** [Makefile:1229: api] Fehler 2
      gmake: *** [Makefile:460: __build_one_by_one] Error 2
      
      I applied the following fix, but the product doesn't boot. Perhaps
      that's not a property of the fix though:
      
      Yours,
      Robert Clausecker
      f2288c5a
    • S
      board: ti: am57xx: enable input on mmc clock · 411278b8
      Sekhar Nori 提交于
      As per the latest pinmux data available for AM572x EVM,
      rev A3, input should be enabled on MMC clock lines for
      MMC2/2/3 for stable operation.
      
      Further, AM572x TRM, SPRUHZ6, Revised June 2016, in
      section 18.4.6.1.1 "Pad Configuration Registers" states
      that input should be enabled for MMC 2/3/4 clock lines.
      
      Enable input on MMC1 and MMC3 clock to match the latest
      pinmux data. Input is already enabled on MMC2 clock for
      BeagleBoard x15. Further, input is already enabled on all
      MMCx clocks for other AM57xx boards (AM572x and AM571x
      IDK).
      
      Tested with HS and UHS SD card on AM572x EVM Rev A3.
      Signed-off-by: NSekhar Nori <nsekhar@ti.com>
      Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
      411278b8
    • V
      ARM: keystone: Pass SPI MTD partition table via kernel command line · 3f18ff07
      Vignesh R 提交于
      SPI U-Boot image for K2 boards have now exceeded 512K partition
      allocated to it and no longer fit the partitions defined in kernel DTS
      file. Therefore, pass an updated MTD partition table from U-Boot as
      kernel command line arguments to avoid kernel from accidentally
      modifying boot loader image that has overflowed to next user partition.
      
      To do is, introduce a common environment file for declaring SPI
      partition so that each individual boards need not repeat the same.
      Choose appropriate SPI bus from board config file and pass it as command
      line argument to kernel.
      Signed-off-by: NVignesh R <vigneshr@ti.com>
      3f18ff07
    • P
      ARMv8: add GOT sections to the list of sections copied · 4b0d506e
      Philipp Tomsich 提交于
      Recent Linux distributions (e.g. Debian 9) include cross-compilers for
      AArch64, but only for the aarch64-linux-gnu triplet only. It can thus
      be expected that users will attempt to use the system cross-compiler
      (instead of an aarch64-elf variant) to compile U-Boot for their ARMv8
      target systems.
      
      One key differences between an aarch64-linux-gnu and an aarch64-elf
      compiler are the default settings regarding position-independent: with
      the aarch64-linux-gnu compiler, the default will create and use the
      global offset table.
      
      This change-set adjusts the list of sections copied on ARMv8 to include
      the GOT sections. With this added, the list matches the previous setup
      for AArch32 closely.
      
      Note that this is not an 'academic' issue, but was in fact encountered
      by our QA during testing of the RK3399-Q7 BSP and resulted in an
      early failure of the SPL stage during FDT setup.
      Signed-off-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
      Tested-by: NKlaus Goger <klaus.goger@theobroma-systems.com>
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      Reviewed-by: NTom Rini <trini@konsulko.com>
      4b0d506e
    • J
      env_mmc: Allow SPL to use any MMC device to load/save the environment · 687d2073
      Jean-Jacques Hiblot 提交于
      SPL has been restricted to use only dev 0 based on the assumption that only
      one MMC device is registered. This is not always the case and many
      platforms now register several devices as expected by the spl mmc boot code
      For those platform SPL_ENV_SUPPORT is broken if dev is forced to 0.
      
      A word of warning: this commit may break SPL_ENV_SUPPORT on platforms that
      do not register the same MMC controllers in SPL and in u-boot (mostly iMX6
      based platforms). Fortunately none of those activate SPL_ENV_SUPPORT in
      their default configuration.
      Signed-off-by: NJean-Jacques Hiblot <jjhiblot@ti.com>
      687d2073
  2. 07 4月, 2017 2 次提交
  3. 06 4月, 2017 32 次提交