From: John Dallaway <john@dallaway.org.uk>
To: Sergei Gavrikov <sergei.gavrikov@gmail.com>
Cc: eCos development list <ecos-devel@ecos.sourceware.org>
Subject: Re: LPC2xxx internal flash driver
Date: Wed, 23 Feb 2011 08:50:00 -0000 [thread overview]
Message-ID: <4D64CA3F.5060801@dallaway.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1102222007140.17562@sg-laptop>
Hi Sergei
Sergei Gavrikov wrote:
> Well, what can I say. I would avoid addition 'flash_arm_lpc2xxx' package
> by default for mentioned targets in ecos.db, but, this is my view only.
> Perhaps, I missed something and if Andrew is on the list, he can correct
> me on the "v1/v2 mix" issue.
Thank you for looking into this. It seems that a flash v2 version of the
package with dummy block-locking functions would be desirable. Maybe
someone in the eCos community will be interested in developing support
for LPC2xxx internal flash along these lines.
For avoidance of doubt, I will not add the existing package to any
LPC2xxx target definitions.
John Dallaway
eCos maintainer
http://www.dallaway.org.uk/john
prev parent reply other threads:[~2011-02-23 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 12:13 John Dallaway
2011-02-22 13:03 ` Sergei Gavrikov
2011-02-22 19:19 ` Sergei Gavrikov
2011-02-23 8:50 ` John Dallaway [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=4D64CA3F.5060801@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-devel@ecos.sourceware.org \
--cc=sergei.gavrikov@gmail.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).