From: Jonathan Larmour <jifl@eCosCentric.com>
To: Himanshu Patel <himanshup@aftek.com>,
'Rutger Hofman' <rutger@cs.vu.nl>,
'eCos Discuss' <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] FAT32 over NAND
Date: Tue, 20 Jan 2009 18:42:00 -0000 [thread overview]
Message-ID: <49761AF0.5020603@eCosCentric.com> (raw)
In-Reply-To: <20090120151449.GB15884@lunn.ch>
Andrew Lunn wrote:
> On Tue, Jan 20, 2009 at 08:41:35PM +0530, Himanshu Patel wrote:
>> Okay...Thanks...
>>
>> YAFFS2 is not a possible option...As device should be able to access from PC
>> running Windows also through mass storage interface...
>>
>> Can we make use of NFTL (NAND flash translation layer) which Linux is
>> providing?
>
> Depends on what license you want to use. If you are happy that your
> entire system, is GPL, yes. However most people want to keep there
> application closed, in which case you cannot use Linux kernel code.
There are also patent issues. FTLs are covered by patents by M-Systems,
Inc. in the US and Europe at least. You cannot develop or sell a product
containing an FTL in those markets without getting a licence from M-Systems
(unless it's used in a PCMCIA device, for which M-Systems grants a
no-royalty licence).
See the bottomr of http://sources.redhat.com/jffs2/jffs2-html/node1.html
Because of this, I doubt eCos will ever have an FTL.
Jifl
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-01-20 18:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 14:50 [ECOS] Size of eCos Himanshu Patel
2009-01-20 14:08 ` [ECOS] FAT32 over NAND Himanshu Patel
2009-01-20 14:31 ` Andrew Lunn
2009-01-20 14:40 ` Himanshu Patel
2009-01-20 14:42 ` Rutger Hofman
2009-01-20 15:11 ` Himanshu Patel
2009-01-20 15:15 ` Andrew Lunn
2009-01-20 15:17 ` Himanshu Patel
2009-01-20 18:42 ` Jonathan Larmour [this message]
2009-01-20 19:09 ` Paul D. DeRocco
2009-01-21 2:18 ` Jonathan Larmour
2009-01-21 4:26 ` Paul D. DeRocco
2009-01-20 15:14 ` Himanshu Patel
2009-01-20 15:40 ` Rutger Hofman
2009-01-20 16:30 ` Chris Zimman
2009-01-21 13:59 ` Rutger Hofman
2009-01-21 14:08 ` Himanshu Patel
2009-01-21 20:18 ` Rutger Hofman
2009-01-21 20:54 ` Paul D. DeRocco
2009-01-21 14:12 ` Himanshu Patel
2009-01-21 16:12 ` Chris Zimman
2009-01-21 14:14 ` Himanshu Patel
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=49761AF0.5020603@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=himanshup@aftek.com \
--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).