1. 02 Apr, 2007 1 commit
  2. 08 Mar, 2007 1 commit
    • Vitaly Wool's avatar
      [MTD] [NAND] make oobavail public · 1f92267c
      Vitaly Wool authored
      During the MTD rework the oobavail parameter of mtd_info structure has become
      private. This is not quite correct in terms of integrity and logic. If we have
      means to write to OOB area, then we'd like to know upfront how many bytes out
      of OOB are spare per page to be able to adapt to specific cases.
      The patch inlined adds the public oobavail parameter.
      Signed-off-by: default avatarVitaly Wool <vwool@ru.mvista.com>
      Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      1f92267c
  3. 09 Feb, 2007 3 commits
  4. 29 Nov, 2006 4 commits
  5. 28 Nov, 2006 1 commit
    • Vitaly Wool's avatar
      [MTD] [NAND] remove len/ooblen confusion. · 7014568b
      Vitaly Wool authored
      As was discussed between Ricard Wanderlöf, David Woodhouse, Artem 
      Bityutskiy and me, the current API for reading/writing OOB is confusing. 
      
      The thing that introduces confusion is the need to specify ops.len 
      together with ops.ooblen for reads/writes that concern only OOB not data 
      area. So, ops.len is overloaded: when ops.datbuf != NULL it serves to 
      specify the length of the data read, and when ops.datbuf == NULL, it 
      serves to specify the full OOB read length.
      
      The patch inlined below is the slightly updated version of the previous 
      patch serving the same purpose, but with the new Artem's comments taken 
      into account.
      
      Artem, BTW, thanks a lot for your valuable input!
      Signed-off-by: default avatarVitaly Wool <vwool@ru.mvista.com>
      Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      7014568b
  6. 29 Jun, 2006 1 commit
  7. 14 Jun, 2006 1 commit
  8. 29 May, 2006 5 commits
    • Thomas Gleixner's avatar
      [MTD] NAND Expose the new raw mode function and status info to userspace · f1a28c02
      Thomas Gleixner authored
      The raw read/write access to NAND (without ECC) has been changed in the
      NAND rework. Expose the new way - setting the file mode via ioctl - to
      userspace. Also allow to read out the ecc statistics information so userspace
      tools can see that bitflips happened and whether errors where correctable
      or not. Also expose the number of bad blocks for the partition, so nandwrite
      can check if the data fits into the parition before writing to it.
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      f1a28c02
    • Thomas Gleixner's avatar
      [MTD] Rework the out of band handling completely · 8593fbc6
      Thomas Gleixner authored
      Hopefully the last iteration on this!
      
      The handling of out of band data on NAND was accompanied by tons of fruitless
      discussions and halfarsed patches to make it work for a particular
      problem. Sufficiently annoyed by I all those "I know it better" mails and the
      resonable amount of discarded "it solves my problem" patches, I finally decided
      to go for the big rework. After removing the _ecc variants of mtd read/write
      functions the solution to satisfy the various requirements was to refactor the
      read/write _oob functions in mtd.
      
      The major change is that read/write_oob now takes a pointer to an operation
      descriptor structure "struct mtd_oob_ops".instead of having a function with at
      least seven arguments.
      
      read/write_oob which should probably renamed to a more descriptive name, can do
      the following tasks:
      
      - read/write out of band data
      - read/write data content and out of band data
      - read/write raw data content and out of band data (ecc disabled)
      
      struct mtd_oob_ops has a mode field, which determines the oob handling mode.
      
      Aside of the MTD_OOB_RAW mode, which is intended to be especially for
      diagnostic purposes and some internal functions e.g. bad block table creation,
      the other two modes are for mtd clients:
      
      MTD_OOB_PLACE puts/gets the given oob data exactly to/from the place which is
      described by the ooboffs and ooblen fields of the mtd_oob_ops strcuture. It's
      up to the caller to make sure that the byte positions are not used by the ECC
      placement algorithms.
      
      MTD_OOB_AUTO puts/gets the given oob data automaticaly to/from the places in
      the out of band area which are described by the oobfree tuples in the ecclayout
      data structre which is associated to the devicee.
      
      The decision whether data plus oob or oob only handling is done depends on the
      setting of the datbuf member of the data structure. When datbuf == NULL then
      the internal read/write_oob functions are selected, otherwise the read/write
      data routines are invoked.
      
      Tested on a few platforms with all variants. Please be aware of possible
      regressions for your particular device / application scenario
      
      Disclaimer: Any whining will be ignored from those who just contributed "hot
      air blurb" and never sat down to tackle the underlying problem of the mess in
      the NAND driver grown over time and the big chunk of work to fix up the
      existing users. The problem was not the holiness of the existing MTD
      interfaces. The problems was the lack of time to go for the big overhaul. It's
      easy to add more mess to the existing one, but it takes alot of effort to go
      for a real solution.
      
      Improvements and bugfixes are welcome!
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      8593fbc6
    • Thomas Gleixner's avatar
      [MTD] Remove silly MTD_WRITE/READ macros · f4a43cfc
      Thomas Gleixner authored
      Most of those macros are unused and the used ones just obfuscate
      the code. Remove them and fixup all users.
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      f4a43cfc
    • Thomas Gleixner's avatar
      [MTD] NAND Replace oobinfo by ecclayout · 5bd34c09
      Thomas Gleixner authored
      The nand_oobinfo structure is not fitting the newer error correction
      demands anymore. Replace it by struct nand_ecclayout and fixup the users
      all over the place. Keep the nand_oobinfo based ioctl for user space
      compability reasons.
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      5bd34c09
    • Thomas Gleixner's avatar
      [MTD] NAND Consolidate oobinfo handling · ff268fb8
      Thomas Gleixner authored
      The info structure for out of band data was copied into
      the mtd structure. Make it a pointer and remove the ability
      to set it from userspace. The position of ecc bytes is
      defined by the hardware and should not be changed by software.
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      ff268fb8
  9. 25 May, 2006 1 commit
  10. 23 May, 2006 3 commits
  11. 22 May, 2006 1 commit
    • Joern Engel's avatar
      [MTD] Introduce writesize · 28318776
      Joern Engel authored
      At least two flashes exists that have the concept of a minimum write unit,
      similar to NAND pages, but no other NAND characteristics.  Therefore, rename
      the minimum write unit to "writesize" for all flashes, including NAND.
      Signed-off-by: default avatarJoern Engel <joern@wh.fh-wedel.de>
      28318776
  12. 13 May, 2006 1 commit
  13. 26 Apr, 2006 1 commit
  14. 09 Nov, 2005 1 commit
    • Olaf Hering's avatar
      [PATCH] changing CONFIG_LOCALVERSION rebuilds too much, for no good reason · 733482e4
      Olaf Hering authored
      This patch removes almost all inclusions of linux/version.h.  The 3
      #defines are unused in most of the touched files.
      
      A few drivers use the simple KERNEL_VERSION(a,b,c) macro, which is
      unfortunatly in linux/version.h.
      
      There are also lots of #ifdef for long obsolete kernels, this was not
      touched.  In a few places, the linux/version.h include was move to where
      the LINUX_VERSION_CODE was used.
      
      quilt vi `find * -type f -name "*.[ch]"|xargs grep -El '(UTS_RELEASE|LINUX_VERSION_CODE|KERNEL_VERSION|linux/version.h)'|grep -Ev '(/(boot|coda|drm)/|~$)'`
      
      search pattern:
      /UTS_RELEASE\|LINUX_VERSION_CODE\|KERNEL_VERSION\|linux\/\(utsname\|version\).h
      Signed-off-by: default avatarOlaf Hering <olh@suse.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      733482e4
  15. 07 Nov, 2005 1 commit
  16. 06 Nov, 2005 1 commit
    • Nicolas Pitre's avatar
      {MTD] add support for Intel's "Sibley" flash · 638d9838
      Nicolas Pitre authored
      This updates the Primary Vendor-Specific Extended Query parsing to
      version 1.4 in order to get the information about the Configurable
      Programming Mode regions implemented in the Sibley flash, as well as
      selecting the appropriate write command code.
      
      This flash does not behave like traditional NOR flash when writing data.
      While mtdblock should just work, further changes are needed for JFFS2 use.
      Signed-off-by: default avatarNicolas Pitre <nico@cam.org>
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      638d9838
  17. 23 May, 2005 3 commits
  18. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4