Angus CLARK [Thu, 5 Jan 2012 16:13:56 +0000 (16:13 +0000)]
nand-data: update READID data for family of Micron devices
Update the READID data for the following Micron devices: MT29F4G08ABADA,
MT29F4G16ABADA, MT29F4G08ABBDA, MT29F4G16ABBDA, MT29F8G08ADBDA, MT29F8G16ADBDA,
MT29F8G08ADADA, MT29F8G16ADADA. (Problem with the second byte in the Full ID
column.)
Signed-off-by: Angus Clark <angus.clark@st.com> Acked-by: Brian Norris <computersforpeace@gmail.com>
Angus CLARK [Thu, 5 Jan 2012 16:13:55 +0000 (16:13 +0000)]
nand-data: rename duplicate Numonyx NAND01G devices as 'Rev C'
The table includes two entries for each of the following Numonyx devices:
NAND01GR3B2B, NAND01GW3B2B, NAND01GR4B2B, NAND01GW4B2B. After further analysis,
it seems that the data for the second set of entries actaully coresponds to the
'Rev C' version of the devices, rather than 'Rev B' as suggested by the names.
This patch renames the second set of entries with the 'Rev C' names.
Signed-off-by: Angus Clark <angus.clark@st.com> Acked-by: Brian Norris <computersforpeace@gmail.com>
Angus CLARK [Thu, 5 Jan 2012 16:13:54 +0000 (16:13 +0000)]
nand-data: updates to S30ML-P devices
Updates to Spansion S30ML-P devices:
- expand names to differentiate between x8 and x16 devices
- fix ID 5th byte: 0x01 to 0x10 (checked with datasheet; seems regression
introduced as part of commit 165cfaa9cdb1054bbafa98f24f179c6aa101fbe6
"nand-data: remove asterisks")
Signed-off-by: Angus Clark <angus.clark@st.com> Acked-by: Brian Norris <computersforpeace@gmail.com>
Angus CLARK [Tue, 6 Dec 2011 12:07:39 +0000 (12:07 +0000)]
nand-data: Samsung devices: fix ID Length = "5?"
Change the ID Length for Samsung devices K9F8G08B0M, K9F8G08U0M, K9F8G08U1M,
from "5?" to "5", as documented in the datasheets and verified on a K9F8G08B0M
device.
Signed-off-by: Angus Clark <angus.clark@st.com> Acked-by: Brian Norris <computersforpeace@gmail.com>
Angus CLARK [Tue, 6 Dec 2011 12:07:37 +0000 (12:07 +0000)]
nand-data: update TC58DVM72A1TG00 BBM info
Update Toshiba TC58DVM72A1TG00 bad block marker information to "1st page (6th
byte in OOB = non FFh)", as described in datasheet, and confirmed with Toshiba
engineers.
Signed-off-by: Angus Clark <angus.clark@st.com> Acked-by: Brian Norris <computersforpeace@gmail.com>
Brian Norris [Tue, 9 Aug 2011 22:05:31 +0000 (15:05 -0700)]
faq: general: add bug reporting FAQ
It's surprising to note that we do not have a general "how to send a bug
report" FAQ. This patch provides a starting point and (most importantly)
directs UBI/UBIFS users to the appropriate bug reporting information.
Signed-off-by: Brian Norris <computersforpeace@gmail.com> Signed-off-by: Artem Bityutskiy <dedekind1@gmail.com>
Brian Norris [Tue, 9 Aug 2011 22:03:54 +0000 (15:03 -0700)]
faq: ubi(fs): sending bug reports using `mtdinfo'
The `mtdinfo' utility (with the `-a' flag) is much more informative
than `cat /proc/mtd', so encourage users to use it if possible when
sending bug reports.
Signed-off-by: Brian Norris <computersforpeace@gmail.com> Signed-off-by: Artem Bityutskiy <dedekind1@gmail.com>
Brian Norris [Mon, 8 Aug 2011 19:37:16 +0000 (12:37 -0700)]
doc: update info on compiling mtd-utils
The recursive build system for mtd-utils was rewritten enough recently
such that the description regarding builing ubi-utils by typing `make'
from its subdirectory is now incorrect. Update the UBI docs to reflect
this.
Also, I copied and edited some basic info from the UBI docs to include
in the general description on compiling mtd-utils.
Signed-off-by: Brian Norris <computersforpeace@gmail.com> Signed-off-by: Artem Bityutskiy <dedekind1@gmail.com>
Brian Norris [Mon, 8 Aug 2011 19:37:14 +0000 (12:37 -0700)]
faq/doc: ubi(fs): move "bug report" questions to FAQ
The "How do I send XXX bug report?" questions belong in the FAQ
for easier access (plus, they're questions anyway). We can then
consolidate/link the bug report information to the "general" FAQ
to give a more unified location for bug reporting info.
Signed-off-by: Brian Norris <computersforpeace@gmail.com> Signed-off-by: Artem Bityutskiy <dedekind1@gmail.com>
Brian Norris [Tue, 19 Jul 2011 22:40:43 +0000 (15:40 -0700)]
nand-data: update ONFI detection stats
Chips that support ONFI will be detected properly; we don't rely on any
ID decoding for these, even if ID decoding would detect them correctly.
This patch just updates the "Full Support" field for certain ONFI-capable
chips and changes their "Detection Method" to "ONFI".
Signed-off-by: Brian Norris <computersforpeace@gmail.com> Signed-off-by: Artem Bityutskiy <dedekind1@gmail.com>
Brian Norris [Tue, 19 Jul 2011 22:40:41 +0000 (15:40 -0700)]
nand-data: remove asterisks
Asterisks (*) were added to indicate that support for certain NAND parts
was not yet integrated into the mainline kernel. Fixes have been merged
now, so remove the notes.
Signed-off-by: Brian Norris <computersforpeace@gmail.com> Signed-off-by: Artem Bityutskiy <dedekind1@gmail.com>
Several parts of the UBI and UBIFS documentation already mention the need to
use ubiformat when flashing UBIFS images. Add a new FAQ entry for the "free
space fixup" flag as an alternative in recent kernels, and put links to it in
these existing locations.
Artem Bityutskiy [Tue, 22 Mar 2011 13:28:19 +0000 (15:28 +0200)]
UBI/UBIFS: tell the truth about linux-next
Although the documentation states the linux-next branch of the
UBI and UBIFS trees is never re-based, I did re-base them several
times. So remove that statement.
Brian Norris [Tue, 31 Aug 2010 23:16:39 +0000 (16:16 -0700)]
mtd-www: NAND-DATA: Added NAND support table
Included new NAND Flash support table. This table includes data about
various NAND chips as well as information about the MTD subsystem's
support for these chips. The table is provided in CSV format and is
sorted, formatted, and output to an HTML page via a Python script
(added to Makefile). New entries can simply be added as new rows in
the CSV document.
Note: I did not link this into the main site yet. I can follow-up later
if you'd like, or feel free to do so yourself.
Philip Rakity contributed to fixing the build script.
Signed-off-by: Brian Norris <computersforpeace@gmail.com> Signed-off-by: Philip Rakity <prakity@yahoo.com> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
UBIFS: add FAQ entry for "task pdflush:110 blocked for more than 120 seconds"
This FAQ entry explains the possible relationship with the
warning "INFO: task pdflush:110 blocked for more than 120 seconds" and the
UBI background thread.
Amended by Artem.
Signed-off-by: Norbert van Bolhuis <nvbolhuis@aimvalley.nl> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>