From: Andrew Lunn <andrew.lunn@ascom.ch>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: NAND & YAFFS
Date: Wed, 03 Jun 2009 06:55:00 -0000 [thread overview]
Message-ID: <20090603065544.GN8356@ma.tech.ascom.ch> (raw)
In-Reply-To: <4A256CD6.6020002@dallaway.org.uk>
On Tue, Jun 02, 2009 at 07:17:58PM +0100, John Dallaway wrote:
> Hi Andrew
>
> Andrew Lunn wrote:
>
> > An FYI for some of the newbies who are maybe not subscribed to all the
> > ecos-mailing lists:
> >
> > After checking with Ross and Paul, i've taken the technical discussion
> > about eCosCentrics's NAND implementation over to ecos-devel.
>
> Have you been able to form a view on the relative merits of the VU
> Amsterdam and eCosCentric implementations so far? Just wanting to ensure
> that this process is not stalled for any reason...
I have some first impressions, looking at the documentation. However
the discussions should really be on ecos-devel, not this semi private list.
Andrew
next prev parent reply other threads:[~2009-06-03 6:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 13:59 Ross Younger
2009-05-13 14:22 ` Simon Kallweit
2009-05-13 16:28 ` Sergei Gavrikov
2009-05-13 19:03 ` John Dallaway
2009-05-15 16:50 ` Ross Younger
2009-05-16 10:43 ` Andrew Lunn
2009-05-16 12:50 ` Ross Younger
2009-05-18 7:13 ` Andrew Lunn
2009-05-18 10:42 ` Rutger Hofman
2009-06-02 18:18 ` John Dallaway
2009-06-03 6:55 ` Andrew Lunn [this message]
2009-05-14 18:41 ` Rutger Hofman
2009-05-15 9:48 ` John Dallaway
2009-05-15 9:52 ` Andrew Lunn
2009-05-15 10:18 ` Simon Kallweit
2009-05-16 9:50 ` Andrew Lunn
2009-05-18 9:39 ` Paul Beskeen
2009-05-18 9:55 ` Simon Kallweit
2009-05-15 16:19 ` Paul Beskeen
2009-05-15 6:44 cetoni GmbH - Uwe Kindler
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=20090603065544.GN8356@ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/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).