From: "Fisher ZHU" <fisher.zhu@gmail.com>
To: "Fisher ZHU" <fisher.zhu@gmail.com>,
"ecos discuss" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] about FTL(Flash Translation Layer)
Date: Mon, 14 Jul 2008 07:35:00 -0000 [thread overview]
Message-ID: <e05d030f0807140034k2629739ei6678dd0e5a0f6c95@mail.gmail.com> (raw)
In-Reply-To: <20080714072623.GB9443@lunn.ch>
NAND flash is so prevalent!
Will ECOS support NAND flash later?
On Mon, Jul 14, 2008 at 3:26 PM, Andrew Lunn <andrew@lunn.ch> wrote:
> On Mon, Jul 14, 2008 at 10:16:39AM +0800, Fisher ZHU wrote:
>> Hello All,
>>
>> Does ECOS has a FTL(Flash Translation Layer) module to emulate a
>> NOR/NAND flash as a block device?
>
> Sort of. See packages/io/flash/current/src/flashiodev.c. NOR only.
>
> Andrew
>
--
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:[~2008-07-14 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 2:17 Fisher ZHU
2008-07-14 7:26 ` Andrew Lunn
2008-07-14 7:35 ` Fisher ZHU [this message]
2008-07-14 7:39 ` Andrew Lunn
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=e05d030f0807140034k2629739ei6678dd0e5a0f6c95@mail.gmail.com \
--to=fisher.zhu@gmail.com \
--cc=ecos-discuss@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).