linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Yoo. Jonghoon" <yooth@ipone.co.kr>
To: "linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: file system for flash memory?
Date: Fri, 22 Jun 2001 11:17:37 +0900	[thread overview]
Message-ID: <NFBBLHGHILCOPCKBODHAOEPDCAAA.yooth@ipone.co.kr> (raw)


Hi,
my custom board uses one 8-kbytes flash sector to store
environmet variables, various logs and etc...
At this time, I modified sbull(simple block device driver
from 'Linux device driver', O'Reilly) and added flash driver
routine. and made minix file system on it. the minix file
system works well, but has the following problems:

a. if user once calls write() to write 8kbytes on flash, the
  minix file system calls write function of device driver
  for many times - each time writes only 512bytes.
  minix file system cuts 8kbytes into several 512bytes
  blocks and *erasse-write the whole flash sector* occurs
  for each block.

b. It has no power-down reliability.

Can anybody recommend other file system suited in
this case? eg. raw flash which ppcboot does. (I think
concurrency becomes problem in this one) or jffs.
I read a few jffs docs. but I think that's suited for system
using many flash sectors for the file system, not for my
case which uses one or two sectors. Am I right ?

Thanks in advance.

===============================================
Yoo. Jonghoon,        IPone inc.
===============================================
e-mail : yooth@ipone.co.kr
tel : 82-2-02-2222-4631
===============================================


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~2001-06-22  2:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=NFBBLHGHILCOPCKBODHAOEPDCAAA.yooth@ipone.co.kr \
    --to=yooth@ipone.co.kr \
    --cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).