From: Andrew Lunn <andrew@lunn.ch>
To: Daniel Morris <danielm@eCosCentric.com>
Cc: "ecos-devel@ecos.sourceware.org" <ecos-devel@ecos.sourceware.org>
Subject: Re: NAND review
Date: Fri, 19 Jun 2009 12:06:00 -0000 [thread overview]
Message-ID: <20090619120632.GC1188@lunn.ch> (raw)
In-Reply-To: <20090619113657.GA6189@stef.ammanford.ecoscentric.com>
On Fri, Jun 19, 2009 at 12:36:57PM +0100, Daniel Morris wrote:
> On Fri, Jun 19, 2009 at 10:07:47AM +0200, Andrew Lunn wrote:
> > This should help avoid reinventing the wheel and hopefully make it
> > cornerles and symmetric. So long as you follow the Linux development
> > process, post often and early, and don't get flamed to a crisp it
> > could be good advertising for eCosCentric.
> >
>
> Did you miss the smiley off? ;-) I know that we've been too bashful and
> consistently self-deprecating to raise this issue, but is interesting
> that you've thought of what advertising benefit contributions make.
Well there are other advantages this route offers:
1) There is _one_true_way_ to get Linux booted from a NAND device
using RedBoot. This means when some custom comes to you asking for
a Redboot port, you don't need to look at the FreeScale extensions
to RedBoot, the Samsung extensions to RedBoot, the MobLin
extensions to RedBoot etc, you just do the _one_true_way_, which
you have already done N times, wash, rinse and repeat...
2) It is eCosCentric code, you know it backwards/upside down and where
the warts are, so allowing you to do a port to a new device quicker
and cheaper than if it was somebody else code.
3) The Linux parts are in mainstream. This is always the recommended
way to do it, compared to being out of tree. So that means less
work for you every time there is a new kernel release.
Andrew
next prev parent reply other threads:[~2009-06-19 12:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 8:27 Simon Kallweit
2009-05-19 13:47 ` Ross Younger
2009-05-19 14:17 ` Andrew Lunn
2009-05-20 13:24 ` Bart Veer
2009-05-20 13:34 ` Rutger Hofman
2009-05-20 13:53 ` Andrew Lunn
2009-05-20 13:56 ` Gary Thomas
2009-05-20 14:22 ` Andrew Lunn
2009-05-20 15:22 ` Andrew Lunn
2009-05-20 15:34 ` Bart Veer
2009-05-20 13:58 ` Rutger Hofman
2009-05-20 14:16 ` Ross Younger
2009-05-20 14:21 ` Gary Thomas
2009-05-20 15:25 ` Ross Younger
2009-05-20 15:37 ` Gary Thomas
2009-05-19 16:29 ` Andrew Lunn
2009-06-03 8:51 ` Andrew Lunn
2009-06-03 10:21 ` Ross Younger
2009-06-03 10:48 ` Andrew Lunn
2009-06-03 11:52 ` Simon Kallweit
2009-06-03 12:26 ` Rutger Hofman
2009-06-03 13:33 ` Jürgen Lambrecht
2009-06-10 17:39 ` Nick Garnett
2009-06-11 11:25 ` Rutger Hofman
2009-06-13 16:31 ` Andrew Lunn
2009-06-18 14:10 ` Nick Garnett
2009-06-19 7:47 ` Andrew Lunn
2009-06-19 14:14 ` Ross Younger
2009-06-19 15:02 ` Andrew Lunn
2009-06-19 16:54 ` Jürgen Lambrecht
2009-06-29 11:09 ` Nick Garnett
2009-06-19 8:07 ` Andrew Lunn
2009-06-19 11:37 ` Daniel Morris
2009-06-19 12:06 ` Andrew Lunn [this message]
2009-05-20 1:02 ` Jonathan Larmour
2009-05-20 7:11 ` Simon Kallweit
2009-05-20 11:12 ` Rutger Hofman
2009-05-20 11:29 ` Simon Kallweit
2009-05-20 13:37 ` 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=20090619120632.GC1188@lunn.ch \
--to=andrew@lunn.ch \
--cc=danielm@eCosCentric.com \
--cc=ecos-devel@ecos.sourceware.org \
/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).