From: Andrea Galbusera <andrea.galbusera@teamware.it>
To: linux-mtd <linux-mtd@lists.infradead.org>,
uClinux development list <uclinux-dev@uclinux.org>
Subject: AMD flash lock/unlock support question
Date: 15 Dec 2003 11:09:50 +0100 [thread overview]
Message-ID: <1071482990.3915.106.camel@andreagal> (raw)
Hi all!
I´m new to embedded linux development, so, please, be patient if I ask
for anything silly.
I´m working with a Coldfire/uClinux system. The hardware mounts two AMD
Am29DL640G flash chips. I can succesfully enable read/write/erase
operations via MTD using uClinux kernel 2.4.20-uc0.
My project actually require to support lock/unlock functions to protect
some flash memory sections. Are they already available for AMD chips?
Anybody succeded using these functions through util/lock.c and
util/unlock.c tools?
Looking at more recent sources from mtd cvs I saw some functions in
cfi_cmdset_0002.c (is this the right one for my chips?) which look to be
relevant for my problem (cfi_amdstd_lock_varsize() and
cfi_amdstd_unlock_varsize()). What development status are these?
TIA
Andrea
reply other threads:[~2003-12-15 10:08 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=1071482990.3915.106.camel@andreagal \
--to=andrea.galbusera@teamware.it \
--cc=linux-mtd@lists.infradead.org \
--cc=uclinux-dev@uclinux.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