All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Wong" <paul.wong@digitalview.com>
To: <tglx@linutronix.de>, <linux-mtd@lists.infradead.org>
Subject: Re: compile error when using MEMREADOOB in do_mounts.c.
Date: Sun, 5 Jan 2003 23:56:56 +0800	[thread overview]
Message-ID: <001801c2b4d3$1571e4c0$b200a8c0@home> (raw)
In-Reply-To: 200301051037.03860.tglx@linutronix.de

Really! this is a good new. I will try this method when I back to office.
Thanks a lots.

Paul

----- Original Message -----
From: "Thomas Gleixner" <tglx@linutronix.de>
To: "Paul Wong" <paul.wong@digitalview.com>; <linux-mtd@lists.infradead.org>
Sent: Sunday, January 05, 2003 5:37 PM
Subject: Re: compile error when using MEMREADOOB in do_mounts.c.


> On Sunday 05 January 2003 09:49, Paul Wong wrote:
> >
> > Yes, I modifed the bootloader (in NOR-Flash) that can load kernel image
in
> > /dev/mtd0 (NAND flash) and bad block handling.  and I also tried the
rootfs
> > in JFFS2, but the customer do not shutdown the system by keyboard, just
> > directly power off the unit. then the JFFS2 may be corrupted and cannot
> > boot up again. The ramdisk is a good solution for this case.   So, I
want
> > to modify the do_mounts.c to check the bad block to load the rootfs
image
> > to ramdisk.
> JFFS2 can handle a direct power down. The only way you can loose data, is
if
> you are writing to a file exactly in the moment, when you power down. This
> does not lead to a fs corruption. JFFS2 can handle this.
>
> --
> Thomas
> ________________________________________________________________________
> linutronix - competence in embedded & realtime linux
> http://www.linutronix.de
> mail: tglx@linutronix.de
>
>
>

      reply	other threads:[~2003-01-05 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03  7:56 compile error when using MEMREADOOB in do_mounts.c Paul Wong
2003-01-03  8:52 ` Thomas Gleixner
2003-01-03  9:22   ` Paul Wong
2003-01-04 20:32     ` Thomas Gleixner
2003-01-05  8:49       ` Paul Wong
2003-01-05  9:37         ` Thomas Gleixner
2003-01-05 15:56           ` Paul Wong [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='001801c2b4d3$1571e4c0$b200a8c0@home' \
    --to=paul.wong@digitalview.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    /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.