From: Bart Veer <bartv@ecoscentric.com>
To: will_wagner@carallon.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] flash erase and bootblocks
Date: Thu, 12 May 2005 10:34:00 -0000 [thread overview]
Message-ID: <20050511210908.BD6ED65C065@smtp.ecoscentric.com> (raw)
In-Reply-To: <20050511202137.GR31731@lunn.ch> (message from Andrew Lunn on Wed, 11 May 2005 22:21:37 +0200)
>>>>> "Andrew" == Andrew Lunn <andrew@lunn.ch> writes:
Andrew> On Mon, May 09, 2005 at 10:41:17AM +0100, Will Wagner wrote:
>> 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.
Andrew> Take a look at the flash_v2 branch in CVS. It has a new
Andrew> api which should allow this to work much cleaner. There is
Andrew> a driver for AMD devices, but i don't know if this
Andrew> particular device is supported. You will need to check the
Andrew> sources.
The V2 AMD driver supports all AMD devices and compatibles, by virtue
of not knowing anything at all about specific chips. Instead details
such as the boot sector layout are supplied on a per-platform basis,
or you can make it use CFI at the cost of a bit more code. You can
look at the documentation as well as the sources.
Bart
--
Bart Veer eCos Configuration Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2005-05-11 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 14:08 Will Wagner
2005-05-11 20:41 ` Andrew Lunn
2005-05-12 10:34 ` Bart Veer [this message]
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=20050511210908.BD6ED65C065@smtp.ecoscentric.com \
--to=bartv@ecoscentric.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=will_wagner@carallon.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).