public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Abraham vd Merwe <abraham@2d3d.co.za>
To: MTD for Linux <linux-mtd@lists.infradead.org>
Subject: Re: safe flash filesystem
Date: Fri, 22 Jun 2001 10:22:38 +0200	[thread overview]
Message-ID: <20010622102238.F1828@crystal.2d3d.co.za> (raw)
In-Reply-To: <3B32668F.8020000@asu.edu>; from Russ.Dill@asu.edu on Thu, Jun 21, 2001 at 14:26:39 -0700

[-- Attachment #1: Type: text/plain, Size: 963 bytes --]

Hi Russ!

> If its just a config file, why make all this so complicated?
> 
> struct node {
> 
> 	u32 magic;
> 	char valid;
> 	u32 version;
> 	u32 data_crc;
> 	u32 hdr_crc;
> 	char data[DATA_SIZE];
> };

Yes, this is something in the lines I was thinking of. But what complicates
things is if you start taking things like avoiding damaged blocks into
account, wear levelling (this is fairly easy to solve) and keeping the flash
unfragmented.

-- 

Regards
 Abraham

Walking on water wasn't built in a day.
		-- Jack Kerouac

__________________________________________________________
 Abraham vd Merwe - 2d3D, Inc.

 Device Driver Development, Outsourcing, Embedded Systems

  Cell: +27 82 565 4451         Snailmail:
   Tel: +27 21 761 7549            Block C, Antree Park
   Fax: +27 21 761 7648            Doncaster Road
 Email: abraham@2d3d.co.za         Kenilworth, 7700
  Http: http://www.2d3d.com        South Africa


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-06-22  8:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21 10:54 safe flash filesystem Abraham vd Merwe
2001-06-21 13:43 ` Vipin Malik
2001-06-21 13:57   ` Abraham vd Merwe
2001-06-21 14:29     ` Vipin Malik
2001-06-21 14:35       ` Abraham vd Merwe
2001-06-21 15:05         ` Vipin Malik
2001-06-21 15:36           ` Chris Read
2001-06-21 15:09         ` Joakim Tjernlund
2001-06-21 15:34           ` Vipin Malik
2001-06-21 19:34             ` Joakim Tjernlund
2001-06-21 19:47             ` Joakim Tjernlund
2001-06-21 15:11         ` Herman Oosthuysen
2001-06-21 17:54           ` Tim Riker
2001-06-21 19:43             ` Vipin Malik
2001-06-21 19:35               ` Tim Riker
2001-06-21 19:56                 ` Vipin Malik
2001-06-21 21:17                   ` Kyle Harris
2001-07-03 23:53                     ` On the "safe filesystem" and write() topic Bjorn Wesen
2001-07-04 14:10                       ` Vipin Malik
2001-07-05 18:16                         ` Bjorn Wesen
2001-07-06 13:40                           ` Vipin Malik
2001-07-07  9:25                             ` Bjorn Wesen
2001-07-07 13:06                               ` Vipin Malik
2001-06-21 21:26         ` safe flash filesystem Russ Dill
2001-06-22  8:22           ` Abraham vd Merwe [this message]
     [not found]           ` <20010622102154.E1828@crystal.2d3d.co.za>
2001-06-22 17:23             ` Russ Dill
2001-06-25  7:45               ` Abraham vd Merwe
2001-06-25  7:59                 ` Russ Dill
2001-06-25 14:11                   ` Vipin Malik
  -- strict thread matches above, loose matches on Subject: below --
2001-06-21 16:05 Vipin Malik

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=20010622102238.F1828@crystal.2d3d.co.za \
    --to=abraham@2d3d.co.za \
    --cc=linux-mtd@lists.infradead.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