From: Christophe Aeschlimann <c.aeschlimann@acn-group.ch>
To: Ran Shalit <ranshalit@gmail.com>
Cc: linux-embedded@vger.kernel.org
Subject: Re: Q: file system for embedded
Date: Thu, 14 Jun 2012 16:48:57 +0200 [thread overview]
Message-ID: <4FD9F9D9.7080101@acn-group.ch> (raw)
In-Reply-To: <CAJ2oMhKB6684j2_ZzRopCxipnUnuu9GbACCMg08OsHBJ7u6=_g@mail.gmail.com>
Le 14.06.2012 14:58, Ran Shalit a écrit :
> Hi Christophe,
>
> Thanks for the reply.
> I have no need to write to flash during the main application
> execution: I will program the configuration and executable before
> start of execution, and after initialization there is no need to write
> again to flash.
How are you going to program the flash ? Which initialization ?
> What I still do not understand is why cramfs, ubifs are recommended
> for embedded if they access the flash.
For the reasons I gave in my previous email. I never used cramfs but I
see that it is a read-only compressed format (like supported in JFFS2)
which decompresses your data on-the-fly before read/execution hence
allowing to store more information if your flash is small.
> Is accessing the flash not a problem in embedded linux ?
I'm not sure what you mean here. It's not a problem, but it requires
some care.
> What does it mean using mlockall with cramfs ?
Well if you don't have swap enabled mlockall has no effect since there
is nowhere to swap anyway. But I'm not sure I understand your question.
> Regards, Ran
Regards,
--
Christophe Aeschlimann
Embedded Software Engineer & IT Manager
ACN Advanced Communications Networks S.A.
2000 - Neuchâtel, Switzerland
Tel. +41 32 724 74 31
prev parent reply other threads:[~2012-06-14 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJ2oMh++ji7YBrx6UcLdhPVDmLuTZCr8kGQR8aEAYWyob_ccBQ@mail.gmail.com>
2012-06-13 21:31 ` Q: file system for embedded Ran Shalit
2012-06-14 8:34 ` Christophe Aeschlimann
2012-06-14 12:58 ` Ran Shalit
2012-06-14 14:48 ` Christophe Aeschlimann [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=4FD9F9D9.7080101@acn-group.ch \
--to=c.aeschlimann@acn-group.ch \
--cc=linux-embedded@vger.kernel.org \
--cc=ranshalit@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.