1. 26 4月, 2016 3 次提交
  2. 06 2月, 2016 1 次提交
  3. 05 8月, 2015 1 次提交
  4. 26 6月, 2015 1 次提交
  5. 13 3月, 2015 1 次提交
  6. 05 12月, 2014 1 次提交
  7. 27 10月, 2014 1 次提交
  8. 22 11月, 2013 1 次提交
    • P
      mtd: nand: omap: add CONFIG_NAND_OMAP_ECCSCHEME for selection of ecc-scheme · 3f719069
      pekon gupta 提交于
      This patch adds new CONFIG_NAND_OMAP_ECCSCHEME, replacing other distributed
      CONFIG_xx used for selecting NAND ecc-schemes.
      This patch aims at solving following issues.
      
      1) Currently ecc-scheme is tied to SoC platform, which prevents user to select
         other ecc-schemes also supported in hardware. like;
       - most of OMAP3 SoC platforms use only 1-bit Hamming ecc-scheme, inspite
         the fact that they can use higher ecc-schemes like 8-bit ecc-schemes with
         software based error detection (OMAP_ECC_BCH4_CODE_HW_DETECTION_SW).
       - most of AM33xx SoC plaforms use 8-bit BCH ecc-scheme for now, but hardware
         supports BCH16 ecc-scheme also.
      
      2) Different platforms use different CONFIG_xx to select ecc-schemes, which
         adds confusion for user while migrating platforms.
       - *CONFIG_NAND_OMAP_ELM* which enables ELM hardware engine, selects only
          8-bit BCH ecc-scheme with h/w based error-correction (OMAP_ECC_BCH8_CODE_HW)
          whereas ELM hardware engine supports other ecc-schemes also like; BCH4,
          and BCH16 (in future).
       - *CONFIG_NAND_OMAP_BCH8* selects 8-bit BCH ecc-scheme with s/w based error
          correction (OMAP_ECC_BCH8_CODE_HW_DETECTION_SW).
       - *CONFIG_SPL_NAND_SOFTECC* selects 1-bit Hamming ecc-scheme using s/w library
      
      Thus adding new *CONFIG_NAND_OMAP_ECCSCHEME* de-couples ecc-scheme dependency
      on SoC platform and NAND driver. And user can select ecc-scheme independently
      foreach board.
      However, selection some hardware based ecc-schemes (OMAP_ECC_BCHx_CODE_HW) still
      depends on presence of ELM hardware engine on SoC. (Refer doc/README.nand)
      Signed-off-by: NPekon Gupta <pekon@ti.com>
      3f719069
  9. 15 10月, 2013 1 次提交
  10. 24 7月, 2013 1 次提交
  11. 14 12月, 2012 1 次提交
  12. 27 11月, 2012 1 次提交
    • S
      spl/nand: introduce CONFIG_SPL_NAND_DRIVERS, _BASE, and _ECC. · 6f2f01b9
      Scott Wood 提交于
      Some small SPLs do not use nand_base.c, and a subset of those also
      require a special driver.  Some SPLs need software ECC but others can't
      fit it.
      
      All existing boards that specify CONFIG_SPL_NAND_SUPPORT have these
      symbols added to preserve existing behavior.
      Signed-off-by: NScott Wood <scottwood@freescale.com>
      --
      v2: use positive logic for including bits of NAND, rather than
      a MINIMAL symbol that excludes things.
      6f2f01b9
  13. 23 10月, 2012 1 次提交
  14. 07 7月, 2012 2 次提交
  15. 27 1月, 2012 1 次提交
    • S
      nand_spl_simple: store ecc data on the stack · d3022c5f
      Stefano Babic 提交于
      Currently nand_spl_simple puts it's temp data at 0x10000 offset in SDRAM
      which is likely to contain already loaded data.
      The patch saves the oob data and the ecc on the stack replacing
      the fixed address in RAM.
      Signed-off-by: NStefano Babic <sbabic@denx.de>
      CC: Ilya Yanok <yanok@emcraft.com>
      CC: Scott Wood <scottwood@freescale.com>
      CC: Tom Rini <tom.rini@gmail.com>
      CC: Simon Schwarz <simonschwarzcor@googlemail.com>
      CC: Wolfgang Denk <wd@denx.de>
      Signed-off-by: NScott Wood <scottwood@freescale.com>
      d3022c5f
  16. 07 12月, 2011 2 次提交
  17. 04 11月, 2011 3 次提交
  18. 22 10月, 2011 1 次提交
  19. 06 10月, 2011 1 次提交
  20. 01 10月, 2011 1 次提交
  21. 04 9月, 2011 2 次提交
  22. 04 8月, 2011 1 次提交
  23. 13 5月, 2011 1 次提交
  24. 28 4月, 2011 1 次提交
  25. 30 11月, 2010 1 次提交
  26. 20 11月, 2010 1 次提交
  27. 05 11月, 2010 2 次提交
  28. 27 10月, 2010 1 次提交
    • W
      Replace CONFIG_SYS_GBL_DATA_SIZE by auto-generated value · 25ddd1fb
      Wolfgang Denk 提交于
      CONFIG_SYS_GBL_DATA_SIZE has always been just a bad workarond for not
      being able to use "sizeof(struct global_data)" in assembler files.
      Recent experience has shown that manual synchronization is not
      reliable enough.  This patch renames CONFIG_SYS_GBL_DATA_SIZE into
      GENERATED_GBL_DATA_SIZE which gets automatically generated by the
      asm-offsets tool.  In the result, all definitions of this value can be
      deleted from the board config files.  We have to make sure that all
      files that reference such data include the new <asm-offsets.h> file.
      
      No other changes have been done yet, but it is obvious that similar
      changes / simplifications can be done for other, related macro
      definitions as well.
      Signed-off-by: NWolfgang Denk <wd@denx.de>
      Acked-by: NKumar Gala <galak@kernel.crashing.org>
      25ddd1fb
  29. 06 7月, 2010 1 次提交
  30. 08 6月, 2010 3 次提交