- 06 Nov, 2005 40 commits
-
-
Nicolas Pitre authored
Change to the extended cfi table parsing for Intel NOR flash that uses the info in the extended table to 'walk' the table rather than using hard coding for various primary extended query table version numbers. From: Jared Hulbert <jaredeh@gmail.com> Signed-off-by:
Nicolas Pitre <nico@cam.org> Signed-off-by:
Thomas Gleixner <tglx@linutronix.de>
-
Artem B. Bityutskiy authored
Signed-off-by:
Artem B. Bityutskiy <dedekind@infradead.org> Signed-off-by:
-
Ben Dooks authored
Spotted by basprog@mail.ru Signed-off-by:
Ben Dooks <ben-linux@fluff.org> Signed-off-by:
-
Todd Poynor authored
Some callers to block-layer commit_write function treat non-zero return as error, notably the loopback mount driver sometimes used in conjunction with JFFS2 on NAND flash for bad block avoidance, etc. Return zero for success as do various other commit_write functions. Signed-off-by:
Todd Poynor <tpoynor@mvista.com> Signed-off-by:
-
Nicolas Pitre authored
If they get inlined into non __xipram functions we're screwed. Signed-off-by:
-
Ben Dooks authored
Signed-off-by:
Ben Dooks <ben@simtec.co.uk> Signed-off-by:
-
Ben Dooks authored
Added .owner initialisation to allow the tracking of the device_driver owners when built as a module Signed-off-by:
-
Ben Dooks authored
Added owner to device driver field for tracking when loaded as a module. Signed-off-by:
-
Ben Dooks authored
Added owner fields to the device_driver for tracking ownership when built as a module Signed-off-by:
-
Artem B. Bityutskiy authored
Don't assume eraseblock size is power of 2. Dataflash can have aligned eraseblock size. From: Peter Menzebach <pm-mtd@mw-itcon.de> Acked-by:
-
Artem B. Bityutskiy authored
- assume wbuf may be of size which is not power of 2 - don't make strange assumption about not padding wbuf for DataFlash - use wbuf = DataFlash page and eraseblock >= 8 Dataflash pages From: Peter Menzebach <pm-mtd@mw-itcon.de> Acked-by:
-
Kyungmin Park authored
Add density mask for better support of DDP chips. Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by:
-
Kyungmin Park authored
Add suspend/resume Signed-off-by:
-
Artem B. Bityutskiy authored
Signed-off-by:
-
Artem B. Bityutskiy authored
Signed-off-by:
-
Kyungmin Park authored
Simple bad block table source and header files Signed-off-by:
-
Ben Dooks authored
Signed-off-by:
-
Ferenc Havasi authored
Signed-off-by:
Ferenc Havasi <havasi@inf.u-szeged.hu> Signed-off-by:
-
Pete Popov authored
- cleaned up the partitions and include files - added more flexible CS and address detection and setup Regression tested on db1200 and db1550. Signed-off-by:
Pete Popov <ppopov@pacbell.net> Signed-off-by:
-
Artem B. Bityutskiy authored
Simplify the debugging code further. Update the TODO list Signed-off-by:
-
Joern Engel authored
Add support for "4G Systems MTX-1 Flash device", better known as meshcube. From: Bruno Randolf <bruno.randolf@4g-systems.biz> Signed-off-by:
Joern Engel <joern@wohnheim.fh-wedel.de> Signed-off-by:
-
Ferenc Havasi authored
Always keep valid data in reserved_size. It did not cause problems, but the reservation code was unoptimal when centralized summary was active or the size of the erase block was very small. Signed-off-by:
-
Vitaly Wool authored
The changes introduced allow to suspend/resume NAND flash. A new state (FL_PM_SUSPENDED) is introduced, as well as routines for mtd->suspend and mtd->resume to put the flash in suspended state from software pov. Signed-off-by:
Vitaly Wool <vwool@ru.mvista.com> Signed-off-by:
-
Todd Poynor authored
From: Vitaly Bordug <vbordug@ru.mvista.com> Signed-off-by:
-
Artem B. Bityutskiy authored
Signed-off-by:
-
Ferenc Havasi authored
Do the summary collection in the right place. If the device was not writebuffered but had c->mtd->writev function (e.g. blkmtd) the summary collector function was not called. Signed-off-by:
-
Kyungmin Park authored
Now we can use the generic platform driver Signed-off-by:
-
Kyungmin Park authored
Signed-off-by:
-
David Vrabel authored
- Intel chip driver has a reboot notifier so no need to reset the chip here. - Don't play with chip selects (platform code should do this if necessary). Signed-off-by:
David Vrabel <dvrabel@arcom.com> Signed-off-by:
-
Ferenc Havasi authored
Signed-off-by:
-
Ferenc Havasi authored
The goal of summary is to speed up the mount time. Erase block summary (EBS) stores summary information at the end of every (closed) erase block. It is no longer necessary to scan all nodes separetly (and read all pages of them) just read this "small" summary, where every information is stored which is needed at mount time. This summary information is stored in a JFFS2_FEATURE_RWCOMPAT_DELETE. During the mount process if there is no summary info the orignal scan process will be executed. EBS works with NAND and NOR flashes, too. There is a user space tool called sumtool to generate this summary information for a JFFS2 image. Signed-off-by:
-
Kyungmin Park authored
Signed-off-by:
-
Kyungmin Park authored
- Remove unused block, page parameters - Add constant instead of runtime value Signed-off-by:
-
Kyungmin Park authored
Signed-off-by:
-
Kyungmin Park authored
- Update OMAP OneNAND mapping file using device driver model - Remove board specific macro and values. Signed-off-by:
-
Kyungmin Park authored
Based on NAND memory bad block table code Signed-off-by:
-
Kyungmin Park authored
Add OneNAND Sync. Burst Read support Tested with OMAP platform Signed-off-by:
-
Kyungmin Park authored
OneNAND is a new flash technology from Samsung with integrated SRAM buffers and logic interface. Signed-off-by:
-
Ferenc Havasi authored
Remove support for virtual blocks, which are build by concatenation of multiple physical erase blocks. For more information please read the MTD mailing list thread "[PATCH] remove support for virtual blocks" Signed-off-by:
-
Artem B. Bityutskiy authored
Signed-off-by:
-
