From: Michael Bergandi <mbergandi@gmail.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: uni@martinlaabs.de, ecos-devel@ecos.sourceware.org
Subject: Re: eCos on AT91SAM9 - call to action
Date: Wed, 16 Mar 2011 18:35:00 -0000 [thread overview]
Message-ID: <AANLkTinwB5gbDajYZju7Btqj6UdjxHe37T6j2Cgds4+H@mail.gmail.com> (raw)
In-Reply-To: <4D80FEDE.4020106@dallaway.org.uk>
> Martin Laabs wrote:
>
>> my port based on the one of Evgeniy Dushitov at the very beginning.
>> However - after some weeks I discovered that it was very hard to support
>> more CPUs out of the AT91SAM9 family with that code-base.
>> So I started from beginning, reusing only some code snipplet from
>> Evgeniy. I made the decision to split the port into three packages.
>
> [ snip ]
>
> It sounds like your input will be valuable. Please do track the
> discussion in bug 1000819 and comment where appropriate. To be clear, I
> still think it makes sense that we focus on Evgeniy's contribution and
> modify it where necessary during the review.
>
> John Dallaway
> eCos maintainer
> http://www.dallaway.org.uk/john
>
I hope that a serious look at what Martin has to offer will be
considered before deciding on which contribution is used as a base.
IMHO, simply because an existing contribution is currently being used
in the community, that should not preclude a new contribution for
replacing it, if it is in fact a 'better' contribution. I haven't seen
or worked with either code base, so I have no vested interest either
way.
--
Mike
next prev parent reply other threads:[~2011-03-16 18:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 11:16 John Dallaway
2011-03-16 13:40 ` Grant Edwards
2011-03-16 14:31 ` AW: " Richard Rauch
2011-03-16 17:07 ` Martin Laabs
2011-03-16 18:18 ` John Dallaway
2011-03-16 18:35 ` Michael Bergandi [this message]
2011-03-17 10:14 ` Martin Laabs
2011-03-17 13:13 ` John Eigelaar
2011-06-16 13:38 ` Frank Pagliughi
2011-06-16 14:05 ` John Dallaway
2011-06-16 14:16 ` John Eigelaar
2011-06-16 14:27 ` eCos on AT91SAM3 [ was Re: eCos on AT91SAM9 - call to action ] John Dallaway
2011-06-16 14:29 ` eCos on AT91SAM9 - call to action Frank Pagliughi
2011-06-20 15:18 ` Eagle 100 (Stellaris LM3S6918) Frank Pagliughi
2011-06-20 16:17 ` Stanislav Meduna
2011-06-21 11:05 ` John Dallaway
2011-06-21 16:34 ` Christophe Coutand
2011-06-23 14:31 ` John Dallaway
2011-06-23 16:48 ` Frank Pagliughi
2011-06-23 17:57 ` Christophe Coutand
2011-07-10 20:38 ` Ilija Kocho
2011-07-12 8:57 ` Christophe Coutand
2011-07-13 14:52 ` Ilija Kocho
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=AANLkTinwB5gbDajYZju7Btqj6UdjxHe37T6j2Cgds4+H@mail.gmail.com \
--to=mbergandi@gmail.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
--cc=uni@martinlaabs.de \
/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).