From: Pavel Kiryukhin <savl@dev.rtsoft.ru>
To: linux-mtd@lists.infradead.org
Cc: Pavel Kiryukhin <savl@dev.rtsoft.ru>
Subject: Protection registers and "top parameter" memory
Date: Thu, 31 Mar 2005 22:39:31 +0400 [thread overview]
Message-ID: <424C43E3.3050802@dev.rtsoft.ru> (raw)
Hi all,
I can not write protection registers (OTP) on Intel StrataFlash Wireless
L18 memory: otp_write reports "all ok", but I get 0xff back.
After some investigation I think I found a reason:
to initiate writing we need issue the Program Protection Register
command at the parameter's partition base address + some offset.
My flash is so caled "Top Parameter" memory that has parameter partition
at the top of memory map.
It seems that current driver assumes that Parameter partition starts at
bottom of memory map.
So I simply changed the direction of "chip walk" in
cfi_intelext_otp_walk [cfi_cmdset_0001.c] to top->bottom in case of
Intel StrataFlash (based on cfi->id and cfi->mfr).
The first tested chip now should always correspond to parameter partition.
As I'm new to flash programming please tell me if this is a known issue
and if not - is my approach correct?
--
I'm not in list so please answer (or cc) to savl@dev.rtsoft.ru
--
Thank you,
Pavel Kiryukhin,
RTSoft, Moscow, Russia.
reply other threads:[~2005-03-31 18:37 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=424C43E3.3050802@dev.rtsoft.ru \
--to=savl@dev.rtsoft.ru \
--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