From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Ezequiel Garcia <elezegarcia@gmail.com>,
Artem Bityutskiy <dedekind1@gmail.com>,
richard.weinberger@gmail.com,
Michael Opdenacker <michael.opdenacker@free-electrons.com>,
linux-mtd@lists.infradead.org, Tim Bird <tim.bird@am.sony.com>
Subject: Re: [RFC/PATCH v2] ubi: Add ubiblock read-write driver
Date: Fri, 19 Apr 2013 09:27:43 -0300 [thread overview]
Message-ID: <20130419122742.GA2459@localhost> (raw)
In-Reply-To: <201304182128.19518.vapier@gentoo.org>
On Thu, Apr 18, 2013 at 09:28:16PM -0400, Mike Frysinger wrote:
> On Thursday 18 April 2013 20:13:00 Ezequiel Garcia wrote:
> > On Thu, Apr 18, 2013 at 04:30:55PM -0400, Mike Frysinger wrote:
> > > i wonder if the write support should be put behind a CONFIG option.
> > > personally, the write support is kind of neat and semi-useful for
> > > development, but i don't plan on shipping anything on that :). i just
> > > want read-only support to load an ext2 fs on top of UBI.
> >
> > Mmm... good input. Maybe putting write support behind a CONFIG and
> > showing a big fat warning when the module loads will do?
> > (something to prevent regular users from using this carelessly).
> >
> > May I ask why would you want to put ext2 fs? Have you considered f2fs?
>
> well, unless i misread things, f2fs is designed for consumer flash
> (mmc/cf/etc...) where the flash (e.g. NAND) is behind a FTL. the device i'm
> interested isn't behind a FTL (the NAND is connected directly to the NAND
> controller in the SoC),
Indeed f2fs is designed for flash behind FTL. The thing is the ubi+ubiblock
should act as a FTL, providing bad block management and wear leveling.
So that's why I've been wondering about using f2fs. Probably I should
give it a try and post the results, instead of just wondering.
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-04-19 12:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 12:21 [RFC/PATCH v2] ubi: Add ubiblock read-write driver Ezequiel Garcia
2012-12-12 15:21 ` richard -rw- weinberger
2012-12-12 15:50 ` Gregory CLEMENT
2012-12-12 16:14 ` richard -rw- weinberger
2012-12-12 16:30 ` Greg KH
2012-12-12 16:32 ` richard -rw- weinberger
2012-12-12 16:18 ` Ezequiel Garcia
2012-12-12 16:35 ` Ezequiel Garcia
2012-12-12 17:26 ` Michael Opdenacker
2012-12-12 19:50 ` Tim Bird
2013-04-18 20:30 ` Mike Frysinger
2013-04-18 20:58 ` Peter Korsgaard
2013-04-19 0:13 ` Ezequiel Garcia
2013-04-19 1:28 ` Mike Frysinger
2013-04-19 7:10 ` Gupta, Pekon
2013-04-19 11:57 ` Mike Frysinger
2013-04-19 12:31 ` Artem Bityutskiy
2013-04-19 12:31 ` Bityutskiy, Artem
2013-04-19 12:53 ` Mike Frysinger
2013-04-19 12:55 ` Matthieu CASTET
2013-04-24 16:27 ` Mike Frysinger
2013-04-19 12:56 ` Artem Bityutskiy
2013-04-19 15:02 ` Ezequiel Garcia
2013-04-19 17:05 ` Tim Bird
2013-04-20 18:12 ` Brian Norris
2013-05-13 7:44 ` Artem Bityutskiy
2013-04-20 7:50 ` richard -rw- weinberger
2013-05-13 7:49 ` Artem Bityutskiy
2013-05-13 9:23 ` richard -rw- weinberger
2013-04-19 12:27 ` Ezequiel Garcia [this message]
2013-05-13 7:28 ` 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=20130419122742.GA2459@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=dedekind1@gmail.com \
--cc=elezegarcia@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=michael.opdenacker@free-electrons.com \
--cc=richard.weinberger@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tim.bird@am.sony.com \
--cc=vapier@gentoo.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).