From: Vitaly Wool <vwool@ru.mvista.com>
To: yuri.golovach@mindspeed.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] treat OOB as a single chunk of oobavail bytes
Date: Tue, 24 Jan 2006 16:02:05 +0300 [thread overview]
Message-ID: <43D6254D.4000408@ru.mvista.com> (raw)
In-Reply-To: <OFFED20C5C.C2FC40DE-ON882570FF.005D6B36-C22570FF.005ED903@mindspeed.com>
Hello Yuri,
can you please specify what patches you did apply and what flash you're
using. Thanks!
Vitaly
yuri.golovach@mindspeed.com wrote:
>Good day Vitaly.
>
>I've tried your patches which modifies nand_base.c, other mtdfiles and
>mtdutils to be compatible with yaffs2.
>
>Unfortunately, I've some issues with them.
>
>1)
> my version of mtd is newer then your and I was unable to patch
>nand_base.c with your patch. So, I add this patch manually (but I'm not
>sure - have I done some mistakes or not).
>
>2) After the kernel compiling with your patches I've started it and
>receive a long list of
> Bad eraseblock1 ... at ...x..................
>
> After "mount" and "df" commands I saw that there is no free space
>on flash because all bloks were marked as "bad block" .
> Than I've tried patched version of flash_eraseall but it was not
>able to see blocks also.
>
>
>3) I've changed nand_bbt.c file (in the patched kernel) where simply
>comment the bad blocks checking. Have booted from it and _successfully_
>used patched flash_eraseall.
>
>4) Than I've start the patched kernel _with bad blocks checking_ but these
>(previously erased blocks) were marked like "bad blocks" again (in a
>kernel booting procedure).
>
>
>So, can you, please, provide your vision what should I do to run your
>patch. Or you can send the link on the mtd line which supports yaffs2,
>because I was unable to find your updates in CVS mainline :(
>
>Thank you,
> Yuri Golovach
>
>
>
>
next parent reply other threads:[~2006-01-24 13:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFFED20C5C.C2FC40DE-ON882570FF.005D6B36-C22570FF.005ED903@mindspeed.com>
2006-01-24 13:02 ` Vitaly Wool [this message]
[not found] <OF1F9E1072.64E03318-ON88257102.0060A9BE-C2257102.0060ED3A@mindspeed.com>
2006-01-28 9:15 ` [PATCH] treat OOB as a single chunk of oobavail bytes Vitaly Wool
2006-01-29 15:19 ` Vitaly Wool
[not found] <OFD870B79D.90A804FE-ON88257101.0037ED08-C2257101.0037DF6B@mindspeed.com>
2006-01-26 12:51 ` Vitaly Wool
2006-01-26 22:26 ` Charles Manning
2006-01-28 9:19 ` 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=43D6254D.4000408@ru.mvista.com \
--to=vwool@ru.mvista.com \
--cc=linux-mtd@lists.infradead.org \
--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