From: Philip Rakity <prakity@yahoo.com>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: Do not understand use of oobfree
Date: Tue, 6 Feb 2007 08:10:08 -0800 (PST) [thread overview]
Message-ID: <389628.4664.qm@web58707.mail.re1.yahoo.com> (raw)
In-Reply-To: <1170663762.3628.56.camel@sauron>
I am still a little confused about oobfree and jffs2. So, Jffs2 knows
about the physical layout of the out of band area -- does not treat it
as a logical linear memory area? The driver does not hide the layout
by providing a linear mapping to jffs2 ? oobfree tells jffs2 where it
can put its data ?
Philip
--- Artem Bityutskiy <dedekind@infradead.org> wrote:
> On Sun, 2007-02-04 at 19:58 -0800, Philip Rakity wrote:
> > I am asking because if I have a flash device that does not map per
> the
> > standard includes do I have to touch jffs2 to get things to work.
>
> I've just submitted a patch which teaches UBI to use MTD_OOB_AUTO
> option. Please, make sure your driver supports it and try the patch.
>
> The idea is that it is not application's business to know details of
> OOB
> - where ECC bytes ate stored, BB marker, etc. This is all legacy
> stuff,
> conceptually wrong. We now (thankfully) have the MTD_OOB_AUTO and it
> should be used instead. It represents free OOB bytes as a contiguous
> buffer and allows you read to it and write from it.
>
> The patches are not in Mainline, not even in mtd-2.6.git yet. They
> are
> at
> git://git.infradead.org/~dedekind/dedekind-mtd-2.6.git.
>
> Or web
>
http://git.infradead.org/?p=users/dedekind/dedekind-mtd-2.6.git;a=summary
>
> Try this and send us your success story or the complaint.
>
> P.S. I don't know why we don't remove the legacy OOB-related stuff -
> but
> I am all for it.
>
> --
> Best regards,
> Artem Bityutskiy (ÐиÑÑÑкий ÐÑÑÑм)
>
>
>
____________________________________________________________________________________
Never Miss an Email
Stay connected with Yahoo! Mail on your mobile. Get started!
http://mobile.yahoo.com/services?promote=mail
next prev parent reply other threads:[~2007-02-06 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 3:58 Do not understand use of oobfree Philip Rakity
2007-02-05 8:22 ` Artem Bityutskiy
2007-02-05 9:14 ` Artem Bityutskiy
2007-02-06 16:10 ` Philip Rakity [this message]
2007-02-05 12:46 ` Adrian Hunter
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=389628.4664.qm@web58707.mail.re1.yahoo.com \
--to=prakity@yahoo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox