From: Charles Manning <manningc2@actrix.gen.nz>
To: linux-mtd@lists.infradead.org, yaffs@stoneboat.aleph1.co.uk
Cc: yuri.golovach@mindspeed.com, Vitaly Wool <vwool@ru.mvista.com>
Subject: Re: [PATCH] treat OOB as a single chunk of oobavail bytes
Date: Fri, 27 Jan 2006 11:26:23 +1300 [thread overview]
Message-ID: <200601271126.23808.manningc2@actrix.gen.nz> (raw)
In-Reply-To: <43D8C5E1.4010600@ru.mvista.com>
On Friday 27 January 2006 01:51, Vitaly Wool wrote:
> Hi Yuri,
>
> well, lemme just summarize what you hafta do in order to make YAFFS2
> work with my patches.
>
> 1. Apply the following patch to the mtd code:
> http://lists.infradead.org/pipermail/linux-mtd/2005-December/014648.html
> (yes, it's a single patch!)
> 2. Modify the fs/yaffs2/yaffs_mtdif2.c to use read_oobfree/write_oobfree
> where appropriate.
>
> Hope that helps,
>
> Vitaly
Hi Vitaly
Is this in CVS yet? If not, I hope it will be there soon.
From what I see, this is going to be just what we need.
YAFFS2 does not need to write_oobfree as a seperate function (it is always
written as a single page write). YAFFS2 only needs read_oobfree.
However, YAFFS1 could use the write_oobfree function at some future date if
YAFFS1 gets moved to this interface to remove the current reliance on hanging
the ugly ECC parameter stuff through the interface.
I am pretty busy right now, but will try get the YAFFS2 side sorted ASAP. If
the YAFFS2 stuff is CVSed before the mtd then I'll just point people to this
patch.
Thanx!
Charles
next prev parent reply other threads:[~2006-01-26 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFD870B79D.90A804FE-ON88257101.0037ED08-C2257101.0037DF6B@mindspeed.com>
2006-01-26 12:51 ` [PATCH] treat OOB as a single chunk of oobavail bytes Vitaly Wool
2006-01-26 22:26 ` Charles Manning [this message]
2006-01-28 9:19 ` Vitaly Wool
[not found] <OF1F9E1072.64E03318-ON88257102.0060A9BE-C2257102.0060ED3A@mindspeed.com>
2006-01-28 9:15 ` Vitaly Wool
2006-01-29 15:19 ` Vitaly Wool
[not found] <OFFED20C5C.C2FC40DE-ON882570FF.005D6B36-C22570FF.005ED903@mindspeed.com>
2006-01-24 13:02 ` Vitaly Wool
2005-11-29 15:02 Vitaly Wool
2005-11-29 22:12 ` Charles Manning
2005-11-30 8:54 ` Vitaly Wool
2005-12-01 22:03 ` Charles Manning
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=200601271126.23808.manningc2@actrix.gen.nz \
--to=manningc2@actrix.gen.nz \
--cc=linux-mtd@lists.infradead.org \
--cc=vwool@ru.mvista.com \
--cc=yaffs@stoneboat.aleph1.co.uk \
--cc=yuri.golovach@mindspeed.com \
/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