Skip to content
Snippets Groups Projects
  1. Apr 08, 2017
    • Jean-Jacques Hiblot's avatar
      env_mmc: Allow SPL to use any MMC device to load/save the environment · 687d2073
      Jean-Jacques Hiblot authored
      
      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: default avatarJean-Jacques Hiblot <jjhiblot@ti.com>
      687d2073
  2. Apr 07, 2017
  3. Apr 05, 2017
  4. Mar 29, 2017
    • mario.six@gdsys.cc's avatar
      dm: Add callback to modify the device tree · 0db4cd25
      mario.six@gdsys.cc authored
      
      Certain boards come in different variations by way of utilizing daughter
      boards, for example. These boards might contain additional chips, which
      are added to the main board's busses, e.g. I2C.
      
      The device tree support for such boards would either, quite naturally,
      employ the overlay mechanism to add such chips to the tree, or would use
      one large default device tree, and delete the devices that are actually
      not present.
      
      Regardless of approach, even on the U-Boot level, a modification of the
      device tree is a prerequisite to have such modular families of boards
      supported properly.
      
      Therefore, we add an option to make the U-Boot device tree (the actual
      copy later used by the driver model) writeable, and add a callback
      method that allows boards to modify the device tree at an early stage,
      at which, hopefully, also the application of device tree overlays will
      be possible.
      
      Signed-off-by: default avatarMario Six <mario.six@gdsys.cc>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      0db4cd25
  5. Mar 28, 2017
  6. Mar 26, 2017
  7. Mar 23, 2017
    • mario.six@gdsys.cc's avatar
      dm: Add callback to modify the device tree · 2a792753
      mario.six@gdsys.cc authored
      
      Certain boards come in different variations by way of utilizing daughter
      boards, for example. These boards might contain additional chips, which
      are added to the main board's busses, e.g. I2C.
      
      The device tree support for such boards would either, quite naturally,
      employ the overlay mechanism to add such chips to the tree, or would use
      one large default device tree, and delete the devices that are actually
      not present.
      
      Regardless of approach, even on the U-Boot level, a modification of the
      device tree is a prerequisite to have such modular families of boards
      supported properly.
      
      Therefore, we add an option to make the U-Boot device tree (the actual
      copy later used by the driver model) writeable, and add a callback
      method that allows boards to modify the device tree at an early stage,
      at which, hopefully, also the application of device tree overlays will
      be possible.
      
      Signed-off-by: default avatarMario Six <mario.six@gdsys.cc>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      2a792753
  8. Mar 21, 2017
  9. Mar 18, 2017
Loading