1. 25 Jul, 2016 1 commit
  2. 22 Jul, 2016 1 commit
  3. 04 Jun, 2016 2 commits
  4. 19 Jan, 2016 1 commit
  5. 31 Mar, 2015 3 commits
  6. 17 Nov, 2014 1 commit
  7. 09 Mar, 2014 1 commit
  8. 14 Oct, 2013 1 commit
  9. 24 Jul, 2013 1 commit
  10. 24 Jun, 2013 1 commit
  11. 31 May, 2013 1 commit
    • Sergey Lapin's avatar
      mtd: resync with Linux-3.7.1 · dfe64e2c
      Sergey Lapin authored
      This patch is essentially an update of u-boot MTD subsystem to
      the state of Linux-3.7.1 with exclusion of some bits:
      - the update is concentrated on NAND, no onenand or CFI/NOR/SPI
      flashes interfaces are updated EXCEPT for API changes.
      - new large NAND chips support is there, though some updates
      have got in Linux-3.8.-rc1, (which will follow on top of this patch).
      To produce this update I used tag v3.7.1 of linux-stable repository.
      The update was made using application of relevant patches,
      with changes relevant to U-Boot-only stuff sticked together
      to keep bisectability. Then all changes were grouped together
      to this patch.
      Signed-off-by: default avatarSergey Lapin <slapin@ossfans.org>
      [scottwood@freescale.com: some eccstrength and build fixes]
      Signed-off-by: default avatarScott Wood <scottwood@freescale.com>
  12. 22 May, 2013 1 commit
  13. 10 Apr, 2013 1 commit
    • Tom Rini's avatar
      nand: Extend nand_(read|write)_skip_bad with *actual and limit parameters · c39d6a0e
      Tom Rini authored
      We make these two functions take a size_t pointer to how much space
      was used on NAND to read or write the buffer (when reads/writes happen)
      so that bad blocks can be accounted for.  We also make them take an
      loff_t limit on how much data can be read or written.  This means that
      we can now catch the case of when writing to a partition would exceed
      the partition size due to bad blocks.  To do this we also need to make
      check_skip_len count not just complete blocks used but partial ones as
      well.  All callers of nand_(read|write)_skip_bad are adjusted to call
      these with the most sensible limits available.
      The changes were started by Pantelis and finished by Tom.
      Signed-off-by: default avatarPantelis Antoniou <panto@antoniou-consulting.com>
      Signed-off-by: default avatarTom Rini <trini@ti.com>
  14. 26 Nov, 2012 1 commit
  15. 17 Sep, 2012 3 commits
  16. 01 Sep, 2012 1 commit
  17. 30 Apr, 2012 1 commit
  18. 26 Jan, 2012 2 commits
    • Scott Wood's avatar
      nand/fsl_elbc: Convert to self-init · c1783474
      Scott Wood authored
      This driver doesn't yet make use of the added flexibility (not that that
      should stop anyone from converting...), but it will with the in-progress
      hack to support 4k-page NAND.
      Signed-off-by: default avatarScott Wood <scottwood@freescale.com>
    • Scott Wood's avatar
      nand: Introduce CONFIG_SYS_NAND_SELF_INIT · 578931b3
      Scott Wood authored
      This allows a driver to run code between nand_scan_ident() and
      nand_scan_tail(), among other things.  See the additions to
      doc/README.nand for details.
      To allow a gradual transition, Boards that don't set
      CONFIG_SYS_NAND_SELF_INIT will still be initialized the old way, but
      new drivers should not require this, and existing drivers should be
      converted when convenient.
      Signed-off-by: default avatarScott Wood <scottwood@freescale.com>
  19. 06 Dec, 2011 1 commit
  20. 30 Sep, 2011 2 commits
  21. 01 Jul, 2011 3 commits
  22. 12 Jan, 2011 1 commit
  23. 11 Oct, 2010 1 commit
    • Scott Wood's avatar
      nand erase: .spread, .part, .chip subcommands · 30486322
      Scott Wood authored
      A while back, in http://lists.denx.de/pipermail/u-boot/2009-June/054428.html,
      Michele De Candia posted a patch to not count bad blocks toward the
      requested size to be erased.  This is desireable when you're passing in
      something like $filesize, but not when you're trying to erase a partition.
      Thus, a .spread subcommand (named for consistency with
      http://lists.denx.de/pipermail/u-boot/2010-August/075163.html) is introduced
      to make explicit the user's desire to erase for a given amount of data,
      rather than to erase a specific region of the chip.
      While passing $filesize to "nand erase" is useful, accidentally passing
      something like $fliesize currently produces quite unpleasant results, as the
      variable evaluates to nothing and U-Boot assumes that you want to erase
      the entire rest of the chip/partition.  To improve the safety of the
      erase command, require the user to make explicit their intentions by
      using a .part or .chip subcommand.  This is an incompatible user interface
      change, but keeping compatibility would eliminate the safety gain, and IMHO
      it's worth it.
      While touching nand_erase_opts(), make it accept 64-bit offsets and sizes,
      fix the percentage display when erase length is rounded up, eliminate
      an inconsistent warning about rounding up the erase length which only
      happened when the length was less than one block (rounding up for $filesize
      is normal operation), and add a diagnostic if there's an attempt to erase
      beginning at a non-block boundary.
      Signed-off-by: default avatarScott Wood <scottwood@freescale.com>
      Tested-by: default avatarBen Gardiner <bengardiner@nanometrics.ca>
  24. 12 Jul, 2010 1 commit
    • Ben Gardiner's avatar
      NAND: environment offset in OOB (CONFIG_ENV_OFFSET_OOB) · c9f7351b
      Ben Gardiner authored
      This is a re-submission of the patch by Harald Welte
      <laforge@openmoko.org> with minor modifications for rebase and changes
      as suggested by Scott Wood <scottwood@freescale.com> [1] [2].
      This patch enables the environment partition to have a run-time dynamic
      location (offset) in the NAND flash.  The reason for this is simply that
      all NAND flashes have factory-default bad blocks, and a fixed compile
      time offset would mean that sometimes the environment partition would
      live inside factory bad blocks. Since the number of factory default
      blocks can be quite high (easily 1.3MBytes in current standard
      components), it is not economic to keep that many spare blocks inside
      the environment partition.
      With this patch and CONFIG_ENV_OFFSET_OOB enabled, the location of the
      environment partition is stored in the out-of-band (OOB) data of the
      first block in flash. Since the first block is where most systems boot
      from, the vendors guarantee that the first block is not a factory
      default block.
      This patch introduces the 'nand env.oob' command, which can be called
      from the u-boot command line. 'nand env.oob get' reads the address of
      the environment partition from the OOB data, 'nand env.oob set
      {offset,partition-name}' allows the setting of the marker by specifying
      a numeric offset or a partition name.
      [1] http://article.gmane.org/gmane.comp.boot-loaders.u-boot/43916
      [2] http://article.gmane.org/gmane.comp.boot-loaders.u-boot/79195Signed-off-by: default avatarBen Gardiner <bengardiner@nanometrics.ca>
      Acked-by: default avatarHarald Welte <laforge@gnumonks.org>
  25. 17 Jul, 2009 1 commit
    • Scott Wood's avatar
      Remove legacy NAND and disk on chip code. · be33b046
      Scott Wood authored
      Legacy NAND had been scheduled for removal.  Any boards that use this
      were already not building in the previous release due to an #error.
      The disk on chip code in common/cmd_doc.c relies on legacy NAND,
      and it has also been removed.  There is newer disk on chip code
      in drivers/mtd/nand; someone with access to hardware and sufficient
      time and motivation can try to get that working, but for now disk
      on chip is not supported.
      Signed-off-by: default avatarScott Wood <scottwood@freescale.com>
  26. 07 Jul, 2009 1 commit
  27. 23 Jan, 2009 1 commit
  28. 18 Oct, 2008 1 commit
  29. 14 Aug, 2008 1 commit
  30. 12 Aug, 2008 2 commits