All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ext2 for read-only file system on UBI
Date: Mon, 19 May 2008 17:44:03 +1000	[thread overview]
Message-ID: <20080519074403.GA17911@cloud.net.au> (raw)
In-Reply-To: <1211180904.27243.27.camel@sauron>

On Mon, May 19, 2008 at 10:08:24AM +0300, Artem Bityutskiy wrote:
> On Mon, 2008-05-19 at 16:56 +1000, Hamish Moffatt wrote:
> > > No, should be fine. Well, you'll still have WL across whole NAND chip,
> > > yes. You'll still have bit-flip handling.
> > 
> > So, is there a benefit to Nancy's proposed ubi block layer as opposed to
> > gluebi + mtdblock?
> > ( http://lists.infradead.org/pipermail/linux-mtd/2008-May/021609.html )
> 
> Yes, her layer is assumed to be R/W block device.
> 
> You could want to glance here as well:
> 
> http://www.linux-mtd.infradead.org/faq/general.html#L_ext2_mtd
> http://www.linux-mtd.infradead.org/faq/ubi.html#L_ext2_over_ubi

Thanks for the links. So, read-write with mtdblock is dangerous
(regardless of UBI) because it must erase and rewrite a whole block,
right? Proposed ubiblk (linked from above) would use UBI ops to make the
update operation safe.

Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  reply	other threads:[~2008-05-19  7:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19  6:21 ext2 for read-only file system on UBI Hamish Moffatt
2008-05-19  6:37 ` Artem Bityutskiy
2008-05-19  6:56   ` Hamish Moffatt
2008-05-19  7:08     ` Artem Bityutskiy
2008-05-19  7:44       ` Hamish Moffatt [this message]
2008-05-19  7:54         ` Artem Bityutskiy
2008-05-19  7:57           ` Artem Bityutskiy

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=20080519074403.GA17911@cloud.net.au \
    --to=hamish@cloud.net.au \
    --cc=dedekind@infradead.org \
    --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 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.