1. 05 6月, 2008 1 次提交
  2. 23 7月, 2007 1 次提交
  3. 08 5月, 2007 1 次提交
  4. 18 4月, 2007 1 次提交
  5. 09 2月, 2007 1 次提交
  6. 29 11月, 2006 1 次提交
  7. 31 10月, 2006 1 次提交
  8. 22 10月, 2006 1 次提交
  9. 26 9月, 2006 4 次提交
  10. 29 6月, 2006 2 次提交
  11. 21 6月, 2006 1 次提交
    • T
      [MTD] NAND: Fix breakage all over the place · 7bc3312b
      Thomas Gleixner 提交于
      Following problems are addressed:
      
      - wrong status caused early break out of nand_wait()
      - removed the bogus status check in nand_wait() which
        is a relict of the abandoned support for interrupted
        erase.
      - status check moved to the correct place in read_oob
      - oob support for syndrom based ecc with strange layouts
      - use given offset in the AUTOOOB based oob operations
      
      Partially based on a patch from Vitaly Vool <vwool@ru.mvista.com>
      Thanks to Savin Zlobec <savin@epico.si> for tracking down the
      status problem.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      7bc3312b
  12. 29 5月, 2006 3 次提交
    • T
      [MTD] Rework the out of band handling completely · 8593fbc6
      Thomas Gleixner 提交于
      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: NThomas Gleixner <tglx@linutronix.de>
      8593fbc6
    • T
      [MTD] NAND Replace oobinfo by ecclayout · 5bd34c09
      Thomas Gleixner 提交于
      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: NThomas Gleixner <tglx@linutronix.de>
      5bd34c09
    • T
      [MTD] NAND Fix platform structure and NDFC driver · 8be834f7
      Thomas Gleixner 提交于
      The platform structure was lacking an oobinfo field.
      The NDFC driver had some remains from another tree.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      8be834f7
  13. 27 5月, 2006 1 次提交
  14. 25 5月, 2006 3 次提交
  15. 24 5月, 2006 2 次提交
  16. 23 5月, 2006 7 次提交
  17. 26 4月, 2006 1 次提交
  18. 07 11月, 2005 2 次提交
  19. 29 6月, 2005 1 次提交
    • T
      [MTD] NAND: Reorganize chip locking · 0dfc6246
      Thomas Gleixner 提交于
      The code was wrong in several aspects. The locking order was
      inconsistent, the device aquire code did not reset a variable
      after a wakeup and the wakeup handling was not working for
      applications where multiple chips are sharing a single
      hardware controller.
      When a hardware controller is available the locking is now
      reduced to the hardware controller lock and the waitqueue is
      moved to the hardware controller structure in order to avoid
      a wake_up_all().
      
      The problem was pointed out by Ben Dooks, who also found the
      missing variable reset as main cause for his deadlock problem.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      0dfc6246
  20. 27 5月, 2005 1 次提交
  21. 23 5月, 2005 3 次提交
  22. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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