From: Andy Hawkins <a.hawkins@cabletime.com>
To: D.A.Fedorov@inp.nsk.su
Cc: linux-mtd@lists.infradead.org
Subject: Re: Problem writing to NOR flash
Date: 26 Jul 2004 16:39:20 +0100 [thread overview]
Message-ID: <1090856360.2220.63.camel@adh> (raw)
In-Reply-To: <Pine.SGI.4.10.10407262153220.569820-100000@Sky.inp.nsk.su>
Hi,
On Mon, 2004-07-26 at 16:00, Dmitry A. Fedorov wrote:
> I have use the same cmdset (exactly) but single (interleave 1) 16 bit
> wide chip Am29LV640. No problems yet with backported code.
I've been doing a bit of digging now. The chip in question is an ST
M29W320DB (32MBit)
do_xxlock_oneblock is called, with an address of 0. However, this is
translated in the function to an address of ffc00002. This address is
then (eventually) passed into map_write16, which adds the virtual
address of the flash onto this address...
This to me appears to be invalid, but I'm not entirely sure what
*should* be happening here. The chip's start address is added on to the
address inside do_xxlock_oneblock (although this is zero), and then the
virtual address is added on again. However, the translation doesn't
appear correct to me:
adr = ((adr & ~0xffff) | 0x2) + ~0x3fffff;
As you can probably tell, I don't fully understand how the code is
*supposed* to work, so it's difficult to know exactly what is going
wrong here.
Thanks.
Andy
next prev parent reply other threads:[~2004-07-26 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 13:32 Problem writing to NOR flash Andy Hawkins
2004-07-26 14:00 ` Dmitry A. Fedorov
2004-07-26 14:11 ` Andy Hawkins
2004-07-26 14:35 ` Dmitry A. Fedorov
2004-07-26 14:49 ` Andy Hawkins
2004-07-26 15:00 ` Dmitry A. Fedorov
2004-07-26 15:39 ` Andy Hawkins [this message]
2004-07-26 16:07 ` Andy Hawkins
2004-08-05 23:24 ` Eric W. Biederman
2004-08-12 6:59 ` Eric W. Biederman
2004-07-29 19:41 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2004-07-19 16:06 Andy Hawkins
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=1090856360.2220.63.camel@adh \
--to=a.hawkins@cabletime.com \
--cc=D.A.Fedorov@inp.nsk.su \
--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