[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071116134105.3823.66507.stgit@warthog.procyon.org.uk>
Date: Fri, 16 Nov 2007 13:41:05 +0000
From: David Howells <dhowells@...hat.com>
To: torvalds@...l.org, akpm@...ux-foundation.org, dwmw2@...radead.org
Cc: linux-kernel@...r.kernel.org, linux-am33-list@...hat.com,
dhowells@...hat.com
Subject: [PATCH 2/2] MN10300: Fix MTD JEDEC probe so that the ASB2303 bootprom
can be detected
Fix MTD JEDEC probe so that the ASB2303 bootprom can be accessed. This is
presumably required because the bootprom is normally write-protected and so
the normal flash probes don't work as they require the ability to write to the
flash to send it commands.
In the condition of the excluded if-statement, uaddr is 1.
Signed-off-by: David Howells <dhowells@...hat.com>
---
drivers/mtd/chips/jedec_probe.c | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/drivers/mtd/chips/jedec_probe.c b/drivers/mtd/chips/jedec_probe.c
index a67b23b..734674d 100644
--- a/drivers/mtd/chips/jedec_probe.c
+++ b/drivers/mtd/chips/jedec_probe.c
@@ -1868,11 +1868,18 @@ static inline __u8 finfo_uaddr(const struct amd_flash_info *finfo, int device_ty
uaddr = finfo->uaddr[uaddr_idx];
+ /* the MN10300 ASB2303 board doesn't detect its bootprom if this test
+ * is allowed to take place, presumably because the flash is
+ * write-protected and so cannot be commanded for the purposes of
+ * probing
+ */
+#ifndef CONFIG_MN10300_UNIT_ASB2303
if (uaddr != MTD_UADDR_NOT_SUPPORTED ) {
/* ASSERT("The unlock addresses for non-8-bit mode
are bollocks. We don't really need an array."); */
uaddr = finfo->uaddr[0];
}
+#endif
uaddr_done:
return uaddr;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists