public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: ricky.zheng@i2mlabs.com
To: John Dallaway <john@dallaway.org.uk>
Cc: Jonathan Larmour <jifl@ecoscentric.com>,
	  Simon Kallweit <simon.kallweit@intefo.ch>,
	  eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: NAND support
Date: Mon, 11 May 2009 11:32:00 -0000	[thread overview]
Message-ID: <20090511233216.vhfwq5n1xcso0s48@webmail.i2mlabs.com> (raw)
In-Reply-To: <4A0446C7.5090105@dallaway.org.uk>

Hi all,

Quoting John Dallaway <john@dallaway.org.uk>:

> Hi Jifl, Ricky and Simon
>
> Jonathan Larmour wrote:
>
>> John Dallaway wrote:
>>
>>> Jifl, can you also advise here please? Could dual licensing of UFFS
>>> under both LGPL and the eCos Public License be achieved with a single
>>> source base using a single license banner?
>>
>> Both these licences are acceptable to the FSF, so I can't see any issue
>> with it.
>>
>> There's then the matter of how to achieve this. Here's my recommendation
>> of how to modify the banner:
>
> [ snip ]
>
> Jifl, thanks for the example license text. This seems much more sensible
> than maintaining two sets of sources with different license headers.
>
> Ricky, are you happy to incorporate the license headers proposed by Jifl
> into your master sources?

I think it's a great proposal, and I will do it by this weekend.

About another UFFS (Unified FFS):
I started UFFS (Ultra-low-cost FFS) at 2005 and released it to public  
(sourceforge.net) under GPL at early 2007. Unified FFS project was  
started at late 2008 by students from Epitech, the first stable  
version is expected at next month.

Ultra-low-cost FFS has no relationship with Unified FFS.

>
> Simon, it would be useful if you would post an outline of how you
> propose to integrate UFFS and NAND device support with eCos to the
> ecos-devel list so we can avoid any surprises later on. This will be a
> great addition to eCos!

eCos is a great platform, a working UFFS package on eCos certainly  
encourage me put more effort on UFFS :)

Cheers,
Ricky Zheng


      reply	other threads:[~2009-05-11 11:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49FFE56B.2070009@intefo.ch>
     [not found] ` <49FFFFBE.4030401@dallaway.org.uk>
     [not found]   ` <4A0001D4.9050309@intefo.ch>
     [not found]     ` <4A001A6A.3040304@dallaway.org.uk>
     [not found]       ` <4A002ABD.9050009@intefo.ch>
2009-05-05 13:55         ` John Dallaway
2009-05-05 23:12           ` Ricky Zheng
2009-05-08 12:53           ` Jonathan Larmour
2009-05-08 14:51             ` John Dallaway
2009-05-11 11:32               ` ricky.zheng [this message]

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=20090511233216.vhfwq5n1xcso0s48@webmail.i2mlabs.com \
    --to=ricky.zheng@i2mlabs.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=jifl@ecoscentric.com \
    --cc=john@dallaway.org.uk \
    --cc=simon.kallweit@intefo.ch \
    /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).