Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
接近 2 年 前同步成功

通知 170
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 01 7月, 2006 1 次提交
  3. 28 6月, 2006 1 次提交
  5. 22 6月, 2006 1 次提交
  7. 15 6月, 2006 1 次提交
  9. 14 6月, 2006 1 次提交
  11. 30 5月, 2006 2 次提交
  13. 29 5月, 2006 2 次提交
    • 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
    • A
      [MTD] Fix debug printk format warning in m25p80 SPI chip driver, again. · 19676ff0
      由 Andrew Morton 提交于 
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      19676ff0
  15. 25 5月, 2006 1 次提交
  17. 23 5月, 2006 3 次提交
  19. 22 5月, 2006 1 次提交
  21. 20 5月, 2006 1 次提交
  23. 17 5月, 2006 1 次提交
  25. 16 5月, 2006 1 次提交
  27. 14 5月, 2006 3 次提交
  29. 12 5月, 2006 1 次提交
  31. 10 5月, 2006 1 次提交
  33. 09 5月, 2006 1 次提交
  35. 08 5月, 2006 1 次提交
  37. 19 4月, 2006 1 次提交
    • J
      mtd: improve parameter parsing for block2mtd · 954c2422
      由 Joern Engel 提交于 
      Expand the parameter parsing for block2mtd.  It now accepts:
Ki, Mi, Gi	- the official prefixes for binary multiples,
		  see http://physics.nist.gov/cuu/Units/binary.html,
ki		- mistake on my side and analog to "k" for decimal multiples,
KiB, MiB, GiB	- for people that prefer to add a "B" for byte,
kiB		- combination of the above.

There were complaints about not accepting "k" for 1024.  This has long
been common practice, but is known to lead to confusion.  Hence the new
SI units and hence block2mtd only accepts units that cannot be confused
with decimal units.  Diverging from common practice doesn't always please
people, even if the change is for the better.
Signed-off-by: NJoern Engel <joern@wohnheim.fh-wedel.de>
Cc: David Woodhouse <dwmw2@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: NAndrew Morton <akpm@osdl.org>
      954c2422
  39. 17 4月, 2006 1 次提交
  41. 12 4月, 2006 1 次提交
  43. 11 4月, 2006 1 次提交
    • J
      [PATCH] Remove blkmtd · acc8dadc
      由 Joern Engel 提交于 
      Remove the blkmtd driver.

- An alternative exists (block2mtd) that hasn't had  bug report for > 1 year.

- Most embedded people tend to use ancient kernels with custom patches from
  mtd cvs and elsewhere, so the 1 year warning period neither helps nor hurts
  them too much.

- It's in the way of klibc.  The problems caused by pulling blkmtd support
  are fairly low, while the problems caused by delaying klibc can be fairly
  substantial.  At best, this would be a severe burden on hpa's time.
Signed-off-by: NJoern Engel <joern@wohnheim.fh-wedel.de>
Acked-by: NThomas Gleixner <tglx@linutronix.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: David Woodhouse <dwmw2@infradead.org>
Signed-off-by: NAndrew Morton <akpm@osdl.org>
Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      acc8dadc
  45. 01 4月, 2006 5 次提交
  47. 14 3月, 2006 1 次提交
  49. 17 1月, 2006 1 次提交
  51. 15 1月, 2006 1 次提交
  53. 14 1月, 2006 4 次提交