From: Will Wagner <will_wagner@carallon.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] flash erase and bootblocks
Date: Mon, 09 May 2005 14:08:00 -0000 [thread overview]
Message-ID: <427F303D.8000806@carallon.com> (raw)
Hi All,
I have a question about support for smaller bootblock sectors when
erasing/programming flash.
I have a driver for AMD AM29DL323D flash chips all working nicely. These
chips have 8 smaller sectors at the beginning of flash.
The erase and program routines in flash_am29xxxx.inl have support for
the smaller bootblocks. However the flash_erase function in flash.c
doesn't support the bootblocks so if I try to erase just one of the
smaller sectors it erases all of them at once.
Anyone got any suggestions on how to get round this? Otherwise I guess
I'll have to alter flash_erase to suit my needs.
Mnay thanks,
Will Wagner
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2005-05-09 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 14:08 Will Wagner [this message]
2005-05-11 20:41 ` Andrew Lunn
2005-05-12 10:34 ` Bart Veer
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=427F303D.8000806@carallon.com \
--to=will_wagner@carallon.com \
--cc=ecos-discuss@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).