From: Timo Ketola <Timo.Ketola@exertus.fi>
To: Fabio Estevam <festevam@gmail.com>
Cc: Han Xu <han.xu@nxp.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: Power cut leads to "corrupt empty space"
Date: Sat, 29 Feb 2020 14:20:10 +0000 [thread overview]
Message-ID: <ceddefa5-3525-8649-3be1-f47f4047b401@exertus.fi> (raw)
In-Reply-To: <92909395-0b0b-da7f-a896-a6c1f11a678f@exertus.fi>
On 29.2.2020 14.46, Timo Ketola wrote:
> I had to put 'nand-ecc-strength = <8>;
> nand-ecc-step-size = <512>;' into the device tree
Actually, I tried these but they didn't help. They are not there any more.
> and make this change
> in drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c:
>
>> @@ -507,11 +507,11 @@ static int common_nfc_set_geometry(struct gpmi_nand_data *this)
That was needed.
> Still, it seems to erase correct blocks when trying to write BBTs.
This might not be true
>> Transfer from/to chip 1, pio[0] 930006, naddr 5, addr 00 00 C0 FF 07
I tried the same in my v4.9 kernel and saw very (exactly?) similar
transactions and it works:
> Transfer from/to chip 0, pio[0] 830006, len 6, cmd 00 00 00 C0 FF 07
> Transfer from/to chip 0, pio[0] 830001, len 1, cmd 30
> Transfer from/to chip 1, pio[0] 930006, len 6, cmd 00 00 00 C0 FF 07
> Transfer from/to chip 1, pio[0] 930001, len 1, cmd 30
> Bad block table found at page 524224, version 0x01
> Bad block table found at page 1048512, version 0x01
--
Timo
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-02-29 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 13:04 Power cut leads to "corrupt empty space" Timo Ketola
2020-02-27 13:08 ` Fabio Estevam
2020-02-27 13:42 ` Timo Ketola
2020-02-27 15:16 ` Fabio Estevam
2020-02-29 12:46 ` Timo Ketola
2020-02-29 13:13 ` Fabio Estevam
2020-02-29 14:20 ` Timo Ketola [this message]
2020-03-01 21:28 ` Richard Weinberger
2020-03-02 12:57 ` Timo Ketola
2020-03-02 21:02 ` Richard Weinberger
2020-03-03 6:27 ` Timo Ketola
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=ceddefa5-3525-8649-3be1-f47f4047b401@exertus.fi \
--to=timo.ketola@exertus.fi \
--cc=festevam@gmail.com \
--cc=han.xu@nxp.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.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;
as well as URLs for NNTP newsgroup(s).