1. 26 7月, 2014 1 次提交
  2. 19 6月, 2014 3 次提交
  3. 06 6月, 2014 1 次提交
    • H
      bootm: make use of legacy image format configurable · 21d29f7f
      Heiko Schocher 提交于
      make the use of legacy image format configurable through
      the config define CONFIG_IMAGE_FORMAT_LEGACY.
      
      When relying on signed FIT images with required signature check
      the legacy image format should be disabled. Therefore introduce
      this new define and enable legacy image format if CONFIG_FIT_SIGNATURE
      is not set. If CONFIG_FIT_SIGNATURE is set disable per default
      the legacy image format.
      Signed-off-by: NHeiko Schocher <hs@denx.de>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Lars Steubesand <lars.steubesand@philips.com>
      Cc: Mike Pearce <mike@kaew.be>
      Cc: Wolfgang Denk <wd@denx.de>
      Cc: Tom Rini <trini@ti.com>
      Cc: Michal Simek <monstr@monstr.eu>
      Acked-by: NSimon Glass <sjg@chromium.org>
      21d29f7f
  4. 18 4月, 2014 1 次提交
  5. 19 2月, 2014 1 次提交
  6. 20 9月, 2013 1 次提交
  7. 24 7月, 2013 1 次提交
  8. 12 7月, 2013 1 次提交
    • S
      bootm: Use selected configuration for ramdisk and fdt · f320a4d8
      Simon Glass 提交于
      If a specific configuraion is selected by the bootm command, e.g. with
      'bootm 84000000#recoveryconf' we must honour this for not just the kernel,
      but also the ramdisk and FDT.
      
      In the conversion to using a common fit_image_load() function for loading
      images from FITs (commits a51ec63b and 53f375fa) this feature was lost.
      Reinstate it by passing the selected configuration back from
      fit_image_load() to boot_get_kernel(), then use this configuration
      (which is stored in images->fit_uname_cfg) in both boot_get_ramdisk()
      and boot_get_fdt().
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      f320a4d8
  9. 26 6月, 2013 1 次提交
    • S
      Clarify bootm OS arguments · 983c72f4
      Simon Glass 提交于
      At present the arguments to bootm are processed in a somewhat confusing
      way. Sub-functions must know how many arguments their calling functions
      have processed, and the OS boot function must also have this information.
      Also it isn't obvious that 'bootm' and 'bootm start' provide arguments in
      the same way.
      
      Adjust the code so that arguments are removed from the list before calling
      a sub-function. This means that all functions can know that argv[0] is the
      first argument of which they need to take notice.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      983c72f4
  10. 05 6月, 2013 1 次提交
  11. 15 5月, 2013 2 次提交