From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mehmet Fide <mehmet.fide@gmail.com>
Cc: Stefan Agner <stefan@agner.ch>,
Vignesh Raghavendra <vigneshr@ti.com>,
Boris Brezillon <bbrezillon@kernel.org>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Mehmet Fide <mehmet.fide@screeningeagle.com>
Subject: Re: [PATCH v3 0/2] mtd: rawnand: vf610_nfc: fix reads on chips with more than 64 bytes of OOB
Date: Fri, 04 Sep 2026 19:38:31 +0200 [thread overview]
Message-ID: <178854351111.1467647.6175697246102601569.b4-ty@bootlin.com> (raw)
In-Reply-To: <20260901073907.2443698-1-mehmet.fide@gmail.com>
On Tue, 01 Sep 2026 09:39:05 +0200, Mehmet Fide wrote:
> From: Mehmet Fide <mehmet.fide@screeningeagle.com>
>
> The driver only implements the 64-byte OOB format the controller
> transfers, so chips with a larger OOB (the Colibri VF61's MX30LF4G28AC
> has 112 bytes) stopped working when nanddev_init() began restoring
> mtd->oobsize after ->attach_chip(): the parity moved and every
> ECC-protected read failed, including the BBT and everything UBI needs.
>
> [...]
Applied to mtd/fixes, thanks!
[1/2] mtd: rawnand: vf610_nfc: fix reads on chips with more than 64 bytes of OOB
commit: 1400e88023f4551032df6a3397a376dcdf67f3d4
[2/2] mtd: rawnand: vf610_nfc: fix false bitflips on reads of erased pages
commit: 8d40b1261e2c967173b88c2f5d1c97cfeed1a2e5
Patche(s) should be available on mtd/linux.git and will be
part of the next PR (provided that no robot complains by then).
Kind regards,
Miquèl
prev parent reply other threads:[~2026-09-04 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 7:39 Mehmet Fide
2026-09-01 7:39 ` [PATCH v3 1/2] " Mehmet Fide
2026-09-01 7:39 ` [PATCH v3 2/2] mtd: rawnand: vf610_nfc: fix false bitflips on reads of erased pages Mehmet Fide
2026-09-04 17:38 ` Miquel Raynal [this message]
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=178854351111.1467647.6175697246102601569.b4-ty@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=bbrezillon@kernel.org \
--cc=frieder.schrempf@kontron.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mehmet.fide@gmail.com \
--cc=mehmet.fide@screeningeagle.com \
--cc=stefan@agner.ch \
--cc=vigneshr@ti.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
all inboxes | Powered by JetHome®