From: Jonathan Larmour <jifl@jifvik.org>
To: Ross Younger <wry@eCosCentric.com>,
eCos developers <ecos-devel@ecos.sourceware.org>
Cc: Rutger Hofman <rutger@cs.vu.nl>,
Simon Kallweit <simon.kallweit@intefo.ch>
Subject: NAND technical review
Date: Fri, 02 Oct 2009 15:51:00 -0000 [thread overview]
Message-ID: <4AC6218C.20407@jifvik.org> (raw)
As per my ecos-discuss mail just now, I would like to get going straight
away with a public discussion of the _technical_ merits of both NAND
implementations. There is a risk of rehashing old ground, but I'm sure in
both cases things have moved on a bit since the last time round, not least
in response to comments, so it would also be good to clarify the current
state.
I think at first the ball is really in Ross/eCosCentric's court to give
the technical rationale for the decision, so I'd like to ask him first to
give his rationale and his own perspective of the comparison of the
pros/cons. I think the primary onus of the legwork is on eCosCentric, not
least because they saw Rutger's version before implementation - although
that was an early version, so it's entirely possible things have changed
now. Obviously I would especially like Rutger's view on whether any
purported benefits of eCosCentric's implementation are really the case,
and any claimed disadvantages of his own are plausible. I suspect some of
this to come down to subjective opinions of course.
But this is an open discussion, so I'd appreciate anyone's views. I'd
especially value Simon Kallweit's views as someone who has actually used
both code implementations which gives him a very good perspective.
Although if anyone wants to contribute, please keep it on topic, within
this thread, and technical.
Thanks. Over to Ross....
Jifl
--
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
next reply other threads:[~2009-10-02 15:51 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 15:51 Jonathan Larmour [this message]
2009-10-06 13:51 ` Ross Younger
2009-10-07 3:12 ` Jonathan Larmour
2009-10-07 16:22 ` Rutger Hofman
2009-10-08 7:15 ` Jürgen Lambrecht
2009-10-15 3:53 ` Jonathan Larmour
2009-10-15 11:54 ` Jürgen Lambrecht
2009-10-15 3:49 ` Jonathan Larmour
2009-10-15 14:36 ` Rutger Hofman
2009-10-16 1:32 ` Jonathan Larmour
2009-10-19 9:56 ` Ross Younger
2009-10-19 14:21 ` Rutger Hofman
2009-10-20 3:21 ` Jonathan Larmour
2009-10-20 12:19 ` Rutger Hofman
2009-10-21 1:45 ` Jonathan Larmour
2009-10-21 12:15 ` Rutger Hofman
2009-10-23 14:06 ` Jonathan Larmour
2009-10-23 15:25 ` Rutger Hofman
2009-10-23 18:03 ` Rutger Hofman
2009-10-27 20:02 ` Rutger Hofman
2009-11-10 7:03 ` Jonathan Larmour
2010-12-11 19:18 ` John Dallaway
2010-12-22 14:54 ` Rutger Hofman
2009-10-15 15:43 ` Rutger Hofman
[not found] ` <4ACDF868.7050706@ecoscentric.com>
2009-10-09 8:27 ` Ross Younger
2009-10-13 2:21 ` Jonathan Larmour
2009-10-13 13:35 ` Rutger Hofman
2009-10-16 4:04 ` Jonathan Larmour
2009-10-19 14:51 ` Rutger Hofman
2009-10-20 4:28 ` Jonathan Larmour
2009-10-07 9:40 ` Jürgen Lambrecht
2009-10-07 16:27 ` Rutger Hofman
2009-10-13 2:44 ` Jonathan Larmour
2009-10-13 6:35 ` Jürgen Lambrecht
2009-10-15 3:55 ` Jonathan Larmour
2009-10-13 12:59 ` Rutger Hofman
2009-10-15 4:41 ` Jonathan Larmour
2009-10-15 14:55 ` Rutger Hofman
2009-10-16 1:45 ` Jonathan Larmour
2009-10-19 10:53 ` Ross Younger
2009-10-20 1:40 ` Jonathan Larmour
2009-10-20 10:17 ` Ross Younger
2009-10-21 2:06 ` Jonathan Larmour
2009-10-22 10:05 ` Ross Younger
2009-11-10 5:15 ` Jonathan Larmour
2009-11-10 10:38 ` Ross Younger
2009-11-10 11:28 ` Ethernet over SPI driver for ENC424J600 Ilija Stanislevik
2009-11-10 12:16 ` Chris Holgate
2009-11-12 18:32 ` NAND technical review Ross Younger
2009-10-13 14:19 ` Rutger Hofman
2009-10-13 19:58 ` Lambrecht Jürgen
2009-10-07 12:11 ` Rutger Hofman
2009-10-08 12:31 ` Ross Younger
2009-10-08 8:16 ` Jürgen Lambrecht
2009-10-12 1:13 ` Jonathan Larmour
2009-10-16 7:29 ` Simon Kallweit
2009-10-16 13:53 ` Jonathan Larmour
2009-10-19 15:02 ` Rutger Hofman
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=4AC6218C.20407@jifvik.org \
--to=jifl@jifvik.org \
--cc=ecos-devel@ecos.sourceware.org \
--cc=rutger@cs.vu.nl \
--cc=simon.kallweit@intefo.ch \
--cc=wry@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).