1. 20 Aug, 2016 13 commits
  2. 16 Aug, 2016 24 commits
  3. 15 Aug, 2016 3 commits
    • Tom Rini's avatar
      common: env_nand: Ensure that we have nand_info[0] prior to use · 4cc9699b
      Tom Rini authored
      Now that nand_info[] is an array of pointers we need to ensure that it's
      been populated prior to use.  We may for example have ENV in NAND set in
      configurations that run on boards with and without NAND (where default
      env is fine enough, such as omap3_beagle and beagleboard (NAND) vs
      beagle xM (no NAND)).
      
      Fixes: b616d9b0 ("nand: Embed mtd_info in struct nand_chip")
      Cc: Scott Wood <oss@buserror.net>
      Signed-off-by: default avatarTom Rini <trini@konsulko.com>
      Acked-by: default avatarScott Wood <oss@buserror.net>
      4cc9699b
    • Andreas Fenkart's avatar
      tools/env: ensure environment starts at erase block boundary · 183923d3
      Andreas Fenkart authored
      56086921 added support for unaligned environments access.
      U-boot itself does not support this:
      - env_nand.c fails when using an unaligned offset. It produces an
        error in nand_erase_opts{drivers/mtd/nand/nand_util.c}
      - in env_sf/env_flash the unused space at the end is preserved, but
        not in the beginning. block alignment is assumed
      - env_sata/env_mmc aligns offset/length to the block size of the
        underlying device. data is silently redirected to the beginning of
        a block
      
      There is seems no use case for unaligned environment. If there is
      some useful data at the beginning of the the block (e.g. end of u-boot)
      that would be very unsafe. If the redundant environments are hosted by
      the same erase block then that invalidates the idea of double buffering.
      It might be that unaligned access was allowed in the past, and that
      people with legacy u-boot are trapped. But at the time of 56086921
      it wasn't supported and due to reasons above I guess it was never
      introduced.
      I prefer to remove that (unused) feature in favor of simplicity
      Signed-off-by: default avatarAndreas Fenkart <andreas.fenkart@digitalstrom.com>
      Acked-by: default avatarStefan Agner <stefan.agner@toradex.com>
      183923d3
    • Chris Zankel's avatar
      xtensa: add support for the 'xtfpga' evaluation board · 7e270ec3
      Chris Zankel authored
      The 'xtfpga' board is actually a set of FPGA evaluation boards that
      can be configured to run an Xtensa processor.
      
       - Avnet Xilinx LX60
       - Avnet Xilinx LX110
       - Avnet Xilinx LX200
       - Xilinx ML605
       - Xilinx KC705
      
      These boards share the same components (open-ethernet, ns16550 serial,
      lcd display, flash, etc.).
      Signed-off-by: default avatarChris Zankel <chris@zankel.net>
      Signed-off-by: default avatarMax Filippov <jcmvbkbc@gmail.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      Reviewed-by: default avatarTom Rini <trini@konsulko.com>
      7e270ec3