public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Paul MAILLET <paulmaillet37@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: RE : JFFS2 for NAND flash file system
Date: Wed, 01 Jun 2011 09:23:00 -0000	[thread overview]
Message-ID: <BANLkTi=BYZRwGJD8Spy4xbFzArTfPfjy0A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=gyorSa2HKm-237g8h_VQZA6fucA@mail.gmail.com>

Hi,

Sorry if my questions could seem a bit lacking but I am new here and I
am quite curious.

For the moment the differences between JFFS2 NAND flash support and
eCos NAND support is not clear in my head.
I understand that NAND flash devices have some drawbacks that must be
taken in account, like :
- wear-levelling for increasing the life time of the device
- ECC (error code correction) to manage bit-flipping
- Bad blocks management

I may be wrong but in my head all these functionality should be
present in the eCos NAND flash support.
For me this layer will use the below layer, the hardware specific NAND
driver, to perform simple read/write.
It will implement WL, ECC and BBM, and provide an API for upper layers
like file systems. Am I wrong?

Here is a drawing of layers as i see it :
___________________
|                                 |   API for app/user
|           FILE IO           |
|___________________|
|                                 |   API for upper layer
|               FS              |  Manage the file system
|___________________|  Use the eCos NAND support interface to perform read/write
|                                 |           API for upper layer
|  eCos NAND support  |           Implement NAND drawbacks management
|___________________|           Uses HW NAND driver to perform simple
R/W operations
|                                 |                     API to access the HW
|   HW NAND Driver      |                    Manage R/W operations
|___________________|                    Reach the hardware


For me it is clear that the FS has nothing to do with all the NAND
drawbacks, it's the job of the NAND support layer, isn't it?

Finally, what are the functionality that make the FS compliant to NAND
devices as it will use a NAND support layer which already take in
account drawbacks from NAND device?

Here is how things are disposed in my head, does it has to be rectified?

PS : Is the Linux mtd layer (or a part of it) the equivalent of the
eCos NAND support?

Thanks for your time,
Best regards,
Paul

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2011-06-01  9:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 10:15 [ECOS] " Paul MAILLET
2011-05-17 10:51 ` Ross Younger
2011-05-17 18:15 ` Stanislav Meduna
2011-05-31 15:20 ` [ECOS] " Paul MAILLET
2011-05-31 18:50   ` Ross Younger
2011-05-31 20:40     ` [ECOS] " Stanislav Meduna
     [not found]       ` <4DE55229.8000009@dallaway.org.uk>
2012-01-11 11:35         ` [ECOS] " Stanislav Meduna
2011-06-01  7:11     ` [ECOS] Re: RE : " Lambrecht Jürgen
2011-06-01  7:28   ` Lambrecht Jürgen
2011-06-01  9:23   ` Paul MAILLET [this message]
2011-06-01 10:54     ` [ECOS] " Stanislav Meduna
2011-06-01 12:23     ` [ECOS] Re: RE : " Ross Younger
2011-06-01 14:44     ` Paul MAILLET
2011-06-07  7:14       ` Lambrecht Jürgen
     [not found]       ` <BANLkTi=795UVVWk-7NK8PNLRjV+0wfJ8pQ@mail.gmail.com>
2011-06-20 12:42         ` Paul MAILLET
2011-08-02  6:53           ` Lambrecht Jürgen

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='BANLkTi=BYZRwGJD8Spy4xbFzArTfPfjy0A@mail.gmail.com' \
    --to=paulmaillet37@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).