From: "Christian Magnusson" <christian.magnusson@runaware.com>
To: <linux-mtd@lists.infradead.org>,
"'uClinux development list'" <uclinux-dev@uclinux.org>
Subject: Support for AM29LV004T in mtd-driver
Date: Thu, 4 Mar 2004 13:35:10 +0100 [thread overview]
Message-ID: <200403041233.i24CX6rl023928@mail.runaware.com> (raw)
I'm using uClinux on my MCF5206eC3 evaluation board, and I noticed that the
AM29LV004T flash wasn't detected in jedec_probe.c.
I have tested it on the linux-2.4.24-uc0 kernel and it works perfect with
interleave 2 since there are 2 x 512Kb flash in the board.
I still haven't tried the patch for the linux-2.6.2-uc0 kernel yet, since I
was unsure about the .uaddr structure. Does anyone know for sure what it
should be set to?
/Christian
diff -u -r uClinux-dist/linux-2.4.x/drivers/mtd/chips/jedec_probe.c
uClinux-dist-test/linux-2.4.x/drivers/mtd/chips/jedec_probe.c
--- uClinux-dist/linux-2.4.x/drivers/mtd/chips/jedec_probe.c Tue Feb 17
13:53:07 2004
+++ uClinux-dist-test/linux-2.4.x/drivers/mtd/chips/jedec_probe.c Thu
Mar 4 10:29:29 2004
@@ -44,6 +44,8 @@
#define AM29F040 0x00A4
#define AM29LV040B 0x004F
#define AM29F032B 0x0041
+#define AM29LV004T 0x00B5
+#define AM29LV004B 0x00B6
/* Atmel */
#define AT49BV512 0x0003
@@ -150,6 +152,30 @@
static const struct amd_flash_info jedec_table[] = {
{
mfr_id: MANUFACTURER_AMD,
+ dev_id: AM29LV004T,
+ name: "AMD AM29LV004T",
+ DevSize: SIZE_512KiB,
+ CmdSet: P_ID_AMD_STD,
+ NumEraseRegions: 4,
+ regions: {ERASEINFO(0x10000,7),
+ ERASEINFO(0x08000,1),
+ ERASEINFO(0x02000,2),
+ ERASEINFO(0x04000,1)
+ }
+ }, {
+ mfr_id: MANUFACTURER_AMD,
+ dev_id: AM29LV004B,
+ name: "AMD AM29LV004B",
+ DevSize: SIZE_512KiB,
+ CmdSet: P_ID_AMD_STD,
+ NumEraseRegions: 4,
+ regions: {ERASEINFO(0x04000,1),
+ ERASEINFO(0x02000,2),
+ ERASEINFO(0x08000,1),
+ ERASEINFO(0x10000,7)
+ }
+ }, {
+ mfr_id: MANUFACTURER_AMD,
dev_id: AM29F032B,
name: "AMD AM29F032B",
DevSize: SIZE_4MiB,
--- uClinux-dist-test/linux-2.6.x.old/drivers/mtd/chips/jedec_probe.c Fri
Jan 30 00:22:39 2004
+++ uClinux-dist-test/linux-2.6.x/drivers/mtd/chips/jedec_probe.c Thu
Mar 4 10:40:44 2004
@@ -50,6 +50,8 @@
#define AM29F040 0x00A4
#define AM29LV040B 0x004F
#define AM29F032B 0x0041
+#define AM29LV004T 0x00B5
+#define AM29LV004B 0x00B6
/* Atmel */
#define AT49BV512 0x0003
@@ -239,6 +241,40 @@
static const struct amd_flash_info jedec_table[] = {
{
.mfr_id = MANUFACTURER_AMD,
+ .dev_id = AM29LV004T,
+ .name = "AMD AM29LV004T",
+ .uaddr = {
+ [0] = MTD_UADDR_0x0AAA_0x0555, /* x8 */
+ [1] = MTD_UADDR_0x0555_0x02AA, /* x16 */
+ },
+ .DevSize = SIZE_512KiB,
+ .CmdSet = P_ID_AMD_STD,
+ .NumEraseRegions= 4,
+ .regions = {
+ ERASEINFO(0x10000,7),
+ ERASEINFO(0x08000,1),
+ ERASEINFO(0x02000,2),
+ ERASEINFO(0x04000,1)
+ }
+ }, {
+ .mfr_id = MANUFACTURER_AMD,
+ .dev_id = AM29LV004B,
+ .name = "AMD AM29LV004B",
+ .uaddr = {
+ [0] = MTD_UADDR_0x0AAA_0x0555, /* x8 */
+ [1] = MTD_UADDR_0x0555_0x02AA, /* x16 */
+ },
+ .DevSize = SIZE_512KiB,
+ .CmdSet = P_ID_AMD_STD,
+ .NumEraseRegions= 4,
+ .regions = {
+ ERASEINFO(0x04000,1),
+ ERASEINFO(0x02000,2),
+ ERASEINFO(0x08000,1),
+ ERASEINFO(0x10000,7)
+ }
+ }, {
+ .mfr_id = MANUFACTURER_AMD,
.dev_id = AM29F032B,
.name = "AMD AM29F032B",
.uaddr = {
reply other threads:[~2004-03-04 12:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200403041233.i24CX6rl023928@mail.runaware.com \
--to=christian.magnusson@runaware.com \
--cc=linux-mtd@lists.infradead.org \
--cc=uclinux-dev@uclinux.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