From: Ben Dooks <ben@fluff.org.uk>
To: "K.F.J. Martens" <gmc@metro.cx>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Horrible Bug? AMD29LV400BB with mtd in 2.6.10rc2
Date: Fri, 3 Dec 2004 00:46:01 +0000 [thread overview]
Message-ID: <20041203004601.GA29522@home.fluff.org> (raw)
In-Reply-To: <20041202225607.GH3233@metro.cx>
On Thu, Dec 02, 2004 at 11:56:07PM +0100, K.F.J. Martens wrote:
> Hi All,
>
> I'm currently developing a flash file system for the TomTom GO, a car
> navigation system that employs an ARM processor.
>
> In it is an EON29LV400BB flash chip, which is entirely compatible with
> AMD's AM29LV400BB.
>
> Now, what I did was copy the AM29LV400BB definition in
> mtd/chips/jedec_probe.c to a new definition in the struct amd_flash_info
> array jedec_table like so:
>
>
> },{
> .mfr_id = MANUFACTURER_EON,
> .dev_id = EON29LV400BB,
> .name = "EON AM29LV400BB",
> .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),
> }
> }, {
>
>
>
> Now, here comes. This does not work, and the reason is that the x8 and
> x16 addresses are swapped. It's a bit late now to hook up one of those
> devices and paste the exact error message, but it was something along
> the line of 'MTD jedec_match(): 0x0555 0x0aaa did not match'
>
> If I reverse them like so:
>
>
> [0] = MTD_UADDR_0x0555_0x02AA, /* x8 */
> [1] = MTD_UADDR_0x0AAA_0x0555, /* x16 */
>
There has been some fixing in the jedec and similar probe code
to fix the use of the fields of device width / overlap due to
incorrect addressing being used for the chip commands.
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next prev parent reply other threads:[~2004-12-03 0:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 22:56 Horrible Bug? AMD29LV400BB with mtd in 2.6.10rc2 K.F.J. Martens
2004-12-03 0:46 ` Ben Dooks [this message]
2004-12-03 17:11 ` K.F.J. Martens
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=20041203004601.GA29522@home.fluff.org \
--to=ben@fluff.org.uk \
--cc=gmc@metro.cx \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.