From: Gary Thomas <gary@mlbassoc.com>
To: rpai@it.iitb.ac.in
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] - RAM File system
Date: Sat, 21 May 2005 15:03:00 -0000 [thread overview]
Message-ID: <1116596583.22383.135.camel@hermes> (raw)
In-Reply-To: <32942.10.129.11.162.1116596162.squirrel@www.it.iitb.ac.in>
On Fri, 2005-05-20 at 19:06 +0530, rpai@it.iitb.ac.in wrote:
> hello ........
>
> I have an application that uses data given by the user. So the
> question is how can i get data into the redboot , which format
> of file I should store the data. I am using the RAM file
> system....
>
> Can any one tell me a way to get data into redboot...
Why would you want the data "into RedBoot?" If the application
needs the data, have it fetch it itself, e.g. using TFTP.
If you want the data to be permanent, then you could keep it in
a FLASH image (managed by RedBoot). Since the RAM file system is
dynamic (purely created at runtime), you may need to fetch the
data in some other fashion and then load it into the RAM file system.
Another alternative would be to keep the data in some other form,
e.g. JFFS2 or ROM file system.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
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:[~2005-05-20 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-21 10:48 rpai
2005-05-21 15:03 ` Gary Thomas [this message]
2005-05-23 4:58 ` R. Vamshi Krishna
[not found] ` <428DFA6D.6010003@cse.iitb.ac.in>
2005-05-23 5:02 ` Gary Thomas
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=1116596583.22383.135.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=rpai@it.iitb.ac.in \
/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).