From: "Brian Norris" <norris@broadcom.com>
To: linux-mtd@lists.infradead.org
Cc: Kevin Cernekee <cernekee@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <norris@broadcom.com>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: [PATCH 2/2] mtd: nand: Increase NAND_MAX_OOBSIZE
Date: Fri, 20 Aug 2010 12:36:13 -0700 [thread overview]
Message-ID: <1282332973-12077-2-git-send-email-norris@broadcom.com> (raw)
In-Reply-To: <1282332973-12077-1-git-send-email-norris@broadcom.com>
An increase in NAND_MAX_OOBSIZE and NAND_MAX_PAGESIZE is necessary
in order to support many new chips. Among those:
Toshiba TC58TxG4S2FBAxx 8KB page, 576B OOB
Micron MT29F64G08CBAAA 8KB page, 448B OOB
Signed-off-by: Brian Norris <norris@broadcom.com>
---
include/linux/mtd/nand.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/mtd/nand.h b/include/linux/mtd/nand.h
index 102e12c..a8921c2 100644
--- a/include/linux/mtd/nand.h
+++ b/include/linux/mtd/nand.h
@@ -53,8 +53,8 @@ extern int nand_unlock(struct mtd_info *mtd, loff_t ofs, uint64_t len);
* is supported now. If you add a chip with bigger oobsize/page
* adjust this accordingly.
*/
-#define NAND_MAX_OOBSIZE 256
-#define NAND_MAX_PAGESIZE 4096
+#define NAND_MAX_OOBSIZE 576
+#define NAND_MAX_PAGESIZE 8192
/*
* Constants for hardware specific CLE/ALE/NCE function
--
1.7.0.4
next prev parent reply other threads:[~2010-08-20 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 19:36 [PATCH 1/2] mtd: nand: Support new Toshiba SLC Brian Norris
2010-08-20 19:36 ` Brian Norris [this message]
2010-08-20 19:43 ` [PATCH 2/2] mtd: nand: Increase NAND_MAX_OOBSIZE David Woodhouse
2010-08-20 21:28 ` Brian Norris
2010-08-20 21:38 ` David Woodhouse
2010-08-30 12:27 ` [PATCH 1/2] mtd: nand: Support new Toshiba SLC Artem Bityutskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1282332973-12077-2-git-send-email-norris@broadcom.com \
--to=norris@broadcom.com \
--cc=cernekee@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).