Skip to content
Snippets Groups Projects
  1. Dec 09, 2016
  2. Dec 01, 2016
  3. Oct 06, 2016
  4. Sep 27, 2016
  5. Jul 22, 2016
  6. Jun 26, 2016
    • Marek Vasut's avatar
      common: Pass the boot device into spl_boot_mode() · 2b1cdafa
      Marek Vasut authored
      
      The SPL code already knows which boot device it calls the spl_boot_mode()
      on, so pass that information into the function. This allows the code of
      spl_boot_mode() avoid invoking spl_boot_device() again, but it also lets
      board_boot_order() correctly alter the behavior of the boot process.
      
      The later one is important, since in certain cases, it is desired that
      spl_boot_device() return value be overriden using board_boot_order().
      
      Signed-off-by: default avatarMarek Vasut <marex@denx.de>
      Cc: Andreas Bießmann <andreas.devel@googlemail.com>
      Cc: Albert Aribaud <albert.u.boot@aribaud.net>
      Cc: Tom Rini <trini@konsulko.com>
      Reviewed-by: default avatarAndreas Bießmann <andreas@biessmann.org>
      [add newly introduced zynq variant]
      Signed-aff-by: default avatarAndreas Bießmann <andreas@biessmann.org>
      2b1cdafa
  7. May 27, 2016
  8. May 24, 2016
  9. May 17, 2016
  10. Mar 14, 2016
  11. Nov 18, 2015
    • Nikita Kiryanov's avatar
      spl: mmc: add support for BOOT_DEVICE_MMC2 · a1e56cf6
      Nikita Kiryanov authored
      
      Currently the mmc device that SPL looks at is always mmc0, regardless
      of the BOOT_DEVICE_MMCx value. This forces some boards to
      implement hacks in order to boot from other mmc devices.
      
      Make SPL take into account the correct mmc device.
      
      Signed-off-by: default avatarNikita Kiryanov <nikita@compulab.co.il>
      Reviewed-by: default avatarTom Rini <trini@konsulko.com>
      a1e56cf6
    • Nikita Kiryanov's avatar
      spl: change return values of spl_*_load_image() · 36afd451
      Nikita Kiryanov authored
      
      Make spl_*_load_image() functions return a value instead of
      hanging if a problem is encountered. This enables main spl code
      to make the decision whether to hang or not, thus preparing
      it to support alternative boot devices.
      
      Some boot devices (namely nand and spi) do not hang on error.
      Instead, they return normally and SPL proceeds to boot the
      contents of the load address. This is considered a bug and
      is rectified by hanging on error for these devices as well.
      
      Signed-off-by: default avatarNikita Kiryanov <nikita@compulab.co.il>
      Cc: Igor Grinberg <grinberg@compulab.co.il>
      Cc: Tom Rini <trini@konsulko.com>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Ian Campbell <ijc@hellion.org.uk>
      Cc: Hans De Goede <hdegoede@redhat.com>
      Cc: Albert Aribaud <albert.u.boot@aribaud.net>
      Cc: Jagan Teki <jteki@openedev.com>
      Reviewed-by: default avatarTom Rini <trini@konsulko.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      36afd451
  12. Jul 21, 2015
    • Simon Glass's avatar
      dm: spl: Allow device tree/driver model in board_init_f() · 070d00b8
      Simon Glass authored
      
      Add an spl_init() function that does basic init such that board_init_f() can
      use simple malloc(), device tree and driver model. Each one is set up only
      if enabled for SPL.
      
      Note: We really should refactor SPL such that there is a single
      board_init_f() and rename the existing weak board_init_f() functions
      provided by boards, calling them from the single board_init_f().
      
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      070d00b8
  13. Jun 11, 2015
    • Simon Glass's avatar
      arm: spl: Add an API to detect when U-Boot is started from SPL · 32ba8952
      Simon Glass authored
      
      For secure boot systems it is common to have a read-only U-Boot which starts
      the machine and jumps to a read-write U-Boot for actual booting the OS. This
      allows the read-write U-Boot to be upgraded without risk of permanently
      bricking the machine. In the event that the read-write U-Boot is corrupted,
      the read-only U-Boot can detect this with a checksum and boot into a
      recovery flow.
      
      To support this, add a way to detect when U-Boot is run from SPL as opposed
      to some other method, such as booted directly (no SPL) or started from
      another source (e.g. a primary U-Boot). This works by putting a special value
      in r0.
      
      For now we rely on board-specific code to actually check the register and
      set a flag. At some point this could be generalised, perhaps by using a spare
      register and passing a flag to _main and/or board_init_f().
      
      This commit does not implement any feature, but merely provides the API for
      boards to implement.
      
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      32ba8952
  14. Nov 17, 2014
Loading