From: David Updegraff <dave@cray.com>
To: linux-mtd@lists.infradead.org
Subject: patch for AMD am29dl800b
Date: Thu, 01 Apr 2004 18:01:27 -0600 [thread overview]
Message-ID: <406CAD57.40004@cray.com> (raw)
In-Reply-To: <1080830176.24117.1858.camel@hades.cambridge.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 301 bytes --]
Hi.
I have a gadget with this amd chip on it. Whose id and layout dfn. is
not in the jedec_probe tables. Unfortuanately, they have _SIX_ (6)
erase regions. Anyone know of a reason expanding the regions[] array to
6 is a bad idea? Or why dealing with this chip in general is a bad idea?
-dbu.
[-- Attachment #2: am29dl800b.patch --]
[-- Type: text/x-patch, Size: 1651 bytes --]
--- drivers/mtd/chips/jedec_probe.c.orig 2004-04-01 17:27:18.267578712 -0600
+++ drivers/mtd/chips/jedec_probe.c 2004-04-01 17:59:06.562473792 -0600
@@ -38,6 +38,9 @@
/* AMD */
+#define AM29DL800BB 0x22C8
+#define AM29DL800BT 0x224A
+
#define AM29F800BB 0x2258
#define AM29F800BT 0x22D6
#define AM29LV400BB 0x22BA
@@ -222,7 +225,7 @@
const int NumEraseRegions;
const int CmdSet;
const __u8 uaddr[4]; /* unlock addrs for 8, 16, 32, 64 */
- const ulong regions[4];
+ const ulong regions[6];
};
#define ERASEINFO(size,blocks) (size<<8)|(blocks-1)
@@ -342,6 +345,45 @@
ERASEINFO(0x10000,15),
}
}, {
+/* add DL */
+ .mfr_id = MANUFACTURER_AMD,
+ .dev_id = AM29DL800BB,
+ .name = "AMD AM29DL800BB",
+ .uaddr = {
+ [0] = MTD_UADDR_0x0AAA_0x0555, /* x8 */
+ [1] = MTD_UADDR_0x0555_0x02AA, /* x16 */
+ },
+ .DevSize = SIZE_1MiB,
+ .CmdSet = P_ID_AMD_STD,
+ .NumEraseRegions= 6,
+ .regions = {
+ ERASEINFO(0x04000,1),
+ ERASEINFO(0x08000,1),
+ ERASEINFO(0x02000,4),
+ ERASEINFO(0x08000,1),
+ ERASEINFO(0x04000,1),
+ ERASEINFO(0x10000,14)
+ }
+ }, {
+ .mfr_id = MANUFACTURER_AMD,
+ .dev_id = AM29DL800BT,
+ .name = "AMD AM29DL800BT",
+ .uaddr = {
+ [0] = MTD_UADDR_0x0AAA_0x0555, /* x8 */
+ [1] = MTD_UADDR_0x0555_0x02AA, /* x16 */
+ },
+ .DevSize = SIZE_1MiB,
+ .CmdSet = P_ID_AMD_STD,
+ .NumEraseRegions= 6,
+ .regions = {
+ ERASEINFO(0x10000,14),
+ ERASEINFO(0x04000,1),
+ ERASEINFO(0x08000,1),
+ ERASEINFO(0x02000,4),
+ ERASEINFO(0x08000,1),
+ ERASEINFO(0x04000,1)
+ }
+ }, {
.mfr_id = MANUFACTURER_AMD,
.dev_id = AM29F800BB,
.name = "AMD AM29F800BB",
next prev parent reply other threads:[~2004-04-02 0:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 14:06 Bad blocks Kalev Lember
2004-04-01 14:36 ` David Woodhouse
2004-04-02 0:01 ` David Updegraff [this message]
2004-04-02 5:57 ` patch for AMD am29dl800b David Woodhouse
2004-04-02 13:30 ` David Updegraff
2004-04-02 13:39 ` David Woodhouse
2004-04-02 0:14 ` Bad blocks Greg Ungerer
2004-04-04 11:16 ` Kalev Lember
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=406CAD57.40004@cray.com \
--to=dave@cray.com \
--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