1. 17 Jun, 2006 1 commit
  2. 14 Jun, 2006 2 commits
  3. 09 Jun, 2006 3 commits
  4. 02 Jun, 2006 1 commit
    • David Woodhouse's avatar
      [JFFS2] Remove stray __exit from jffs2_compressors_exit() · 3bcc86f5
      David Woodhouse authored
      
      
      It's used from the initfunc in case of failure too. We could actually do
      with an '__initexit' for this kind of thing -- when built in to the
      kernel, it could do with being dropped with the init text. We _could_
      actually just use __init for it, but that would break if/when we start
      dropping init text from modules. So let's just leave it as it was for now,
      and mutter a little more about random 'janitorial' fixes from people who
      aren't paying attention to what they're doing.
      Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      3bcc86f5
  5. 30 May, 2006 8 commits
  6. 29 May, 2006 9 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] NAND Signal that a bitflip was corrected by ECC · 9a1fcdfd
      Thomas Gleixner authored
      
      
      Return -EUCLEAN on read when a bitflip was detected and corrected, so the
      clients can react and eventually copy the affected block to a spare one.
      Make all in kernel users aware of the change.
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      9a1fcdfd
    • 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
    • Thomas Gleixner's avatar
      [MTD] NAND Fix platform structure and NDFC driver · 8be834f7
      Thomas Gleixner authored
      
      
      The platform structure was lacking an oobinfo field.
      The NDFC driver had some remains from another tree.
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      8be834f7
    • Andrew Morton's avatar
    • David Woodhouse's avatar
  7. 28 May, 2006 2 commits
  8. 27 May, 2006 1 commit
  9. 26 May, 2006 5 commits
  10. 25 May, 2006 8 commits