kernel/linux.git/drivers/mtd/chips, branch linux-2.6.18.y

MTD: Fix bug in fixup_convert_atmel_pri

2006-09-16T12:54:17+00:00

The memset() in fixup_convert_atmel_pri is supposed to zero out everything except the first 5 bytes in *extp, but it ends up zeroing out something way outside the struct instead. Fix this potentially dangerous code by casting the pointer to char * before doing arithmetic. Signed-off-by: Håvard Skinnemoen Signed-off-by: David Woodhouse

MTD: Add lock/unlock operations for Atmel AT49BV6416

2006-08-17T01:16:43+00:00

The AT49BV6416 is locked by default, so we really need to provide at least the unlock() operation for write and erase to work. This patch implements both ->lock() and ->unlock() and provides a fixup to install them when an AT49BV6416 chip is detected. These functions are probably valid on more Atmel chips, but I believe it's mostly obsolete ones. The AT49BV6416 is in fact obsolete, but it's used on all current AT32STK1000 development boards. Signed-off-by: Haavard Skinnemoen Signed-off-by: Josh Boyer

MTD: Convert Atmel PRI information to AMD format

2006-08-17T01:13:06+00:00

Atmel flash chips don't have PRI information in the same format as AMD flash chips. This patch installs a fixup for all Atmel chips that converts the relevant PRI fields into AMD format. Only the fields that are actually used by the command set is actually converted. The rest are initialized to zero (which should be safe) Signed-off-by: Haavard Skinnemoen Signed-off-by: Josh Boyer

[PATCH] MTD: Add Macronix MX29F040 to JEDEC

2006-08-15T00:48:30+00:00

Signed-off-by: Takashi YOSHII Signed-off-by: Josh Boyer

[MTD] Fixes of performance and stability issues in CFI driver.

2006-07-15T12:43:59+00:00

Fix of performance and stability issues on Intel NOR chips. It fixes: 1. Very low write performance on Sibley (perf tests demonstrated write performance less than 100Kb/sec when it should be over 400Kb/sec). 2. Low erase performance. (perf tests on Sibleuy demonstrated erase performance 246Kb/sec when it should be over 300Kb/sec). 3. Error on JFFS2 tests with CPU loading application when MTD returns "block erase error: (status timeout)" To fix the issue it does the following: 1. Removes the timeout tuning from inval_cache_and_wait_for_operation. 2. Waiting conditions in inval_cache_and_wait_for_operation now is based on timer resolution If timeout is lower than timer resolution then we do in cycle "Checking the status" udelay(1); cond_resched(); If timeout is greater than timer resolution (probably erase operation) We do the following sleep for half of operation timeout and do in cycle the following "Checking the status" sleep for timer resolution Signed-off-by: Nicolas Pitre Signed-off-by: Alexey Korolev Signed-off-by: David Woodhouse

Remove obsolete #include

2006-06-30T17:25:36+00:00

Signed-off-by: Jörn Engel Signed-off-by: Adrian Bunk

[MTD] Initialize 'writesize'

2006-06-22T14:15:48+00:00

Signed-off-by: Artem B. Bityutskiy

[MTD] Restore MTD_ROM and MTD_RAM types

2006-06-14T20:39:48+00:00

Let's not attempt the abolition of mtd->type until/unless it's properly thought through. And certainly, let's not do it by halves. Signed-off-by: David Woodhouse

[MTD] assume mtd->writesize is 1 for NOR flashes

2006-06-14T15:53:44+00:00

Signed-off-by: Artem B. Bityitskiy

[MTD] replace MTD_RAM with MTD_GENERIC_TYPE

2006-05-30T12:25:24+00:00

Ram devices get the extra capability of MTD_NO_ERASE - not requiring an explicit erase before writing to it. Currently only mtdblock uses this capability. Rest of the patch is a simple text replacement. Signed-off-by: Joern Engel