1. 16 Jul, 2009 1 commit
  2. 13 Jul, 2009 1 commit
    • Po-Yu Chuang's avatar
      issue write command to base for JEDEC flash · b4db4a76
      Po-Yu Chuang authored
      
      
      For JEDEC flash, we should issue word programming command relative to
      base address rather than sector base address. Original source makes
      SST Flash fails to program sectors which are not on the 0x10000 boundaries.
      
      e.g.
      SST39LF040 uses addr1=0x5555 and addr2=0x2AAA, however, each sector
      is 0x1000 bytes.
      
      Thus, if we issue command to "sector base (0x41000) + offset(0x5555)",
      it sends to 0x46555 and the chip fails to recognize that address.
      
      This patch is tested with SST39LF040.
      Signed-off-by: default avatarPo-Yu Chuang <ratbert@faraday-tech.com>
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      b4db4a76
  3. 08 Jul, 2009 1 commit
  4. 07 Jul, 2009 8 commits
  5. 06 Jul, 2009 4 commits
  6. 12 Jun, 2009 7 commits
    • Stefan Roese's avatar
      nand/mpc512x: Add MPC512x NAND support (NFC) · 35f2edbb
      Stefan Roese authored
      
      
      This patch adds NAND Flash Controller driver for MPC5121 revision 2.
      All device features, except hardware ECC and power management, are
      supported.
      
      This NFC driver replaces the one orignally posted by John Rigby:
      
      "[PATCH] Freescale NFC NAND driver"
      
      It's a port of the Linux driver version posted by Piotr Ziecik a few
      weeks ago. Using this driver has the following advantages (from my
      point of view):
      
      - Compatibility with the Linux NAND driver (e.g. ECC usage)
      - Better code quality in general
      - Resulting U-Boot image is a bit smaller (approx. 3k)
      - Better to sync with newer Linux driver versions
      
      The only disadvantage I can see, is that HW-ECC is not supported right
      now. But this could be added later (e.g. port from Linux driver after
      it's supported there). Using HW-ECC on the MCP5121 NFC has a general
      problem because of the ECC usage in the spare area. This collides with
      JFFS2 for example.
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      Cc: Piotr Ziecik <kosmo@semihalf.com>
      Cc: Wolfgang Denk <wd@denx.de>
      Cc: John Rigby <jcrigby@gmail.com>
      Cc: Scott Wood <scottwood@freescale.com>
      35f2edbb
    • Stefan Roese's avatar
      UBI: Add compile-time check for correct malloc area configuration · 60cfe87b
      Stefan Roese authored
      
      
      UBI is quite memory greedy and requires at least approx. 512k of malloc
      area. This patch adds a compile-time check, so that boards will not
      build with less memory reserved for this area (CONFIG_SYS_MALLOC_LEN).
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      60cfe87b
    • Prafulla Wadaskar's avatar
      sf: new Macronix MX25xx SPI flash driver · 7ce6031a
      Prafulla Wadaskar authored
      
      
      Added macronix SF driver for MTD framework
      MX25L12805D is supported and tested
      TBD: sector erase implementation, other deivces support
      Signed-off-by: default avatarPrafulla Wadaskar <prafulla@marvell.com>
      Signed-off-by: default avatarMike Frysinger <vapier@gentoo.org>
      7ce6031a
    • Todor I Mollov's avatar
      sf: atmel: implement power-of-two write/erase funcs · 2a6cc588
      Todor I Mollov authored
      
      Signed-off-by: default avatarTodor I Mollov <tmollov@ucsd.edu>
      Signed-off-by: default avatarMike Frysinger <vapier@gentoo.org>
      CC: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
      2a6cc588
    • Stefan Roese's avatar
      mtd: Introduce CONFIG_MTD_DEVICE to select compilation of mtdcore.o · d558107c
      Stefan Roese authored
      
      
      This new define enables mtdcore.c compilation and with this we can
      select the MTD device infrastructure needed for the reworked mtdparts
      command.
      
      We now have the 2 MTD infrastructure defines, CONFIG_MTD_DEVICE and
      CONFIG_MTD_PARTITIONS. CONFIG_MTD_DEVICE is needed (as explained above)
      for the "mtdparts" command and CONFIG_MTD_PARTITIONS is needed for UBI.
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      Cc: Scott Wood <scottwood@freescale.com>
      d558107c
    • Stefan Roese's avatar
      mtd: Update MTD infrastructure to support 64bit device size · 8d2effea
      Stefan Roese authored
      
      
      This patch brings the U-Boot MTD infrastructure in sync with the current
      Linux MTD version (2.6.30-rc3). Biggest change is the 64bit device size
      support and a resync of the mtdpart.c file which has seen multiple fixes
      meanwhile.
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      Cc: Scott Wood <scottwood@freescale.com>
      Cc: Kyungmin Park <kmpark@infradead.org>
      8d2effea
    • Stefan Roese's avatar
      mtd: Add MTD concat support to concatenate multiple MTD NOR devices · 0a572655
      Stefan Roese authored
      
      
      This patch adds concatenation support to the U-Boot MTD infrastructure.
      By enabling CONFIG_MTD_CONCAT this MTD CFI wrapper will concatenate
      all found NOR devices into one single MTD device. This can be used by
      e.g by UBI to access a partition that spans over multiple NOR chips.
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      0a572655
  7. 03 Jun, 2009 2 commits
    • Wolfgang Denk's avatar
      Redundant Environment: protect full sector size · dfcd7f21
      Wolfgang Denk authored
      
      
      Several boards used different ways to specify the size of the
      protected area when enabling flash write protection for the sectors
      holding the environment variables: some used CONFIG_ENV_SIZE and
      CONFIG_ENV_SIZE_REDUND, some used CONFIG_ENV_SECT_SIZE, and some even
      a mix of both for the "normal" and the "redundant" areas.
      
      Normally, this makes no difference at all. However, things are
      different when you have to deal with boards that can come with
      different types of flash chips, which may have different sector
      sizes.
      
      Here we may have to chose CONFIG_ENV_SECT_SIZE such that it fits the
      biggest sector size, which may include several sectors on boards using
      the smaller sector flash types. In such a case, using CONFIG_ENV_SIZE
      or CONFIG_ENV_SIZE_REDUND to enable the protection may lead to the
      case that only the first of these sectors get protected, while the
      following ones aren't.
      
      This is no real problem, but it can be confusing for the user -
      especially on boards that use CONFIG_ENV_SECT_SIZE to protect the
      "normal" areas, while using CONFIG_ENV_SIZE_REDUND for the
      "redundant" area.
      
      To avoid such inconsistencies, I changed all sucn boards that I found
      to consistently use CONFIG_ENV_SECT_SIZE for protection. This should
      not cause any functional changes to the code.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      Cc: Paul Ruhland
      Cc: Pantelis Antoniou <panto@intracom.gr>
      Cc: Stefan Roese <sr@denx.de>
      Cc: Gary Jennejohn <garyj@denx.de>
      Cc: Dave Ellis <DGE@sixnetio.com>
      Acked-by: default avatarStefan Roese <sr@denx.de>
      dfcd7f21
    • Stefan Roese's avatar
      cfi_mtd: Fix bug in last sector detection · dba6fcf6
      Stefan Roese authored
      
      
      This patch now enabled this cfi-mtd wrapper to correctly detect and
      erase the last sector in an NOR FLASH device.
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      dba6fcf6
  8. 23 May, 2009 1 commit
  9. 29 Apr, 2009 1 commit
  10. 27 Apr, 2009 2 commits
  11. 16 Apr, 2009 1 commit
  12. 06 Apr, 2009 1 commit
  13. 04 Apr, 2009 2 commits
  14. 03 Apr, 2009 1 commit
    • Scott Wood's avatar
      Noisily disable the legacy NAND subsystem. · 99067b08
      Scott Wood authored
      
      
      Legacy NAND is marked for feature removal after April 2009 (i.e. this
      upcoming release).  There are still several boards that reference it
      (though many do so only for disk-on-chip support which has been silently
      disabled for a while now).  These boards will now fail to build
      with #error, though the code is still there if the user removes #error.
      
      The plan is to remove the code outright in the next release, along with
      any board code that refers to it (such as board/esd/common/auto_update.c).
      
      Also, remove the legacy NAND API description from README.nand.
      Signed-off-by: default avatarScott Wood <scottwood@freescale.com>
      99067b08
  15. 02 Apr, 2009 7 commits