From: cetoni GmbH - Uwe Kindler <uwe.kindler@cetoni.de>
To: ecos-maintainers@ecos.sourceware.org
Cc: rutger@cs.vu.nl
Subject: Re: NAND & YAFFS
Date: Fri, 15 May 2009 06:44:00 -0000 [thread overview]
Message-ID: <4A0D0F19.1000803@cetoni.de> (raw)
Hi,
I completely agree with Rutgers opinion about his development of eCos
NAND support.
(http://ecos.sourceware.org/ml/ecos-maintainers/2009-05/msg00011.html).
I think the situation is very disappointing for him.
He invested a lot of work and time, he made his project public very
early and he carefully designed the NAND flash IO and device layers.
Because his work was public from the beginning, anyone could contribute,
criticize or help. At the moment his implementation is the only one I
know in detail and the only one that is public accessible. Furthermore
its NAND framework is already used and known by other eCos community
members. So at the moment I tend to say, Rutgers implementation is the
current eCos NAND framework.
I think before we decide if some parts of eCosCentrics NAND
implementation can be used, we should carefully check both
implementations and discuss pros and cons. To do this we would need
public access to the eCosCentric NAND implementation as soon as possible.
Furthermore I would like to know from eCosCentric in some short words,
why their NAND implementation/design is better than Rutgers
implementation. If this is not relizable within some days, we should
stay with Rutgers implementation to get working NAND support as fast as
possible.
Kind regards,
Dipl. Inf. (FH)
Uwe Kindler
Software Engineering
--
cetoni GmbH
Am Wiesenring 6
D-07554 Korbussen
Tel.: +49 (0) 36602 338 28
Fax: +49 (0) 36602 338 11
uwe.kindler@cetoni.de
http://www.cetoni.de
next reply other threads:[~2009-05-15 6:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 6:44 cetoni GmbH - Uwe Kindler [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=4A0D0F19.1000803@cetoni.de \
--to=uwe.kindler@cetoni.de \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=rutger@cs.vu.nl \
/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).