public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Jonathan Larmour <jifl@ecoscentric.com>,
	Bart Veer <bartv@ecoscentric.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Flash subsystem update
Date: Tue, 17 Feb 2009 22:01:00 -0000	[thread overview]
Message-ID: <499B33AE.6050608@dallaway.org.uk> (raw)
In-Reply-To: <499A849D.6030809@dallaway.org.uk>

Hi Jifl and Bart

John Dallaway wrote:

> We need to contain further slippage as far as practically possible and
> push forward with eCos 3.0. I would therefore like to ensure we have a
> well-understood plan for addressing this issue in a realistic timescale.
> Firstly, we need to understand the issues that Bart encountered in
> detail. Bart, can you provide this detail today please? Does Jifl's
> proposed workaround work for you?

Bart, thank you for the details of the technical issues.

Jifl, I think Bart makes some valid points regarding a cautious roll out
of any revised Flash API. I also appreciate your own perspective
regarding adoption the new API as part of the new major version of eCos.

Personally, I would prefer that we seize this opportunity to switch API
rather than wait for the next major release of eCos beyond 3.0. If we
switch now, the onus would be on the eCos community to deliver a verdict
on the changes through diligent testing over the beta period and I would
hope that the eCos maintainers could commit to verify RedBoot across a
diverse sample of the boards we have to hand. We do have the option to
extend the beta period, or push out a second beta, if it proves necessary.

Jifl, what are your thoughts on all this?

John Dallaway

  reply	other threads:[~2009-02-17 22:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11  9:07 eCos 3.0 beta 1 punch list #2 John Dallaway
2009-02-13 19:56 ` Bart Veer
2009-02-17  1:29   ` Jonathan Larmour
2009-02-17  9:18     ` Jonathan Larmour
2009-02-17  9:34     ` Flash subsystem update [ was Re: eCos 3.0 beta 1 punch list #2 ] John Dallaway
2009-02-17 22:01       ` John Dallaway [this message]
2009-02-18 12:47         ` Flash subsystem update Bart Veer
2009-02-19  0:08           ` Jonathan Larmour
2009-02-19 11:50             ` Bart Veer
2009-02-19 14:40               ` John Dallaway
2009-02-19 15:13                 ` Bart Veer
2009-02-19 20:53                   ` Jonathan Larmour
2009-02-20  9:16                 ` John Dallaway
2009-02-19 20:31               ` Jonathan Larmour
2009-02-20 12:55                 ` Bart Veer
2009-02-20 21:22                   ` Jonathan Larmour
2009-02-17 21:07     ` eCos 3.0 beta 1 punch list #2 Bart Veer
2009-02-17 23:10       ` Jonathan Larmour
2009-02-19  0:48 ` Jonathan Larmour

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=499B33AE.6050608@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=bartv@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=jifl@ecoscentric.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).