public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Saritha Yellanki" <ysaritha@broadcom.com>
To: "ecos-discuss@sourceware.org" <ecos-discuss@sourceware.org>
Subject: [ECOS] eCos  RAM FS data integrity
Date: Fri, 24 Jul 2009 10:44:00 -0000	[thread overview]
Message-ID: <3B0AC7A3DE042D478300B74F7E21C128111C6C6D13@SJEXCHCCR01.corp.ad.broadcom.com> (raw)
In-Reply-To: <220349.47323.qm@web94602.mail.in2.yahoo.com>

Hi All,

I am working on having some solution for detecting  the eCos RAM file system across system failures. ( CRC or checksum)

( Note: Here we are using RAMFS for storing data on the flash, so after powerup, we want to detect RAMFS corruption due to flash corruptions etc)

If anyone has inputs or ideas here , could you please give me.

Thanks,
Saritha


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

      reply	other threads:[~2009-07-24 10:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-26 17:31 [ECOS] GUI development abhishek srivastava
2009-07-24 10:44 ` Saritha Yellanki [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=3B0AC7A3DE042D478300B74F7E21C128111C6C6D13@SJEXCHCCR01.corp.ad.broadcom.com \
    --to=ysaritha@broadcom.com \
    --cc=ecos-discuss@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).