From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Andrea Scian <andrea.scian@dave.eu>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: R: mtd_nandbitserr and seed using pl35x NAND controller
Date: Thu, 08 Jan 2026 18:15:15 +0100 [thread overview]
Message-ID: <875x9cyqjg.fsf@bootlin.com> (raw)
In-Reply-To: <MI2P293MB026440FB793D2D9D1E59ADA797A8A@MI2P293MB0264.ITAP293.PROD.OUTLOOK.COM> (Andrea Scian's message of "Thu, 18 Dec 2025 11:11:19 +0000")
Hi Andrea,
> root@sw0005-devel:~# nandflipbits /dev/mtd0 5@0
> root@sw0005-devel:~# nanddump -c -s 0 --length=100 /dev/mtd0 | head
> ECC failed: 0
> ECC corrected: 2
> Number of bad blocks: 0
> Number of bbt blocks: 4
> Block size 131072, page size 2048, OOB size 64
> Dumping data starting at 0x00000000 and ending at 0x00000064...
> ECC: 1 corrected bitflip(s) at offset 0x00000000
> 0x00000000: 65 42 49 23 01 00 00 00 00 00 00 00 00 00 00 02 |eBI#............|
> 0x00000010: 00 00 08 00 00 00 10 00 00 00 00 00 00 00 00 00 |................|
> 0x00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 0x00000030: 00 00 00 00 00 00 00 00 00 00 00 00 40 93 2d 8c |............@.-.|
> 0x00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 0x00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 0x00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 0x00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 0x00000080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
> 0x00000090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
>
> I'm wondering how the author if this driver (you, IIUC) has tested it initially,
> especially regarding ECC functionality.
I was using nandbiterrs -i, but I was on a mainline kernel, I never
tested the backports, even though if they picked the driver entirely
there are little chances this could be a problem.
Subpage writes are normally completely orthogonal to ECC handling, so I
still do not understand what you get here. Maybe you can track the
register statuses and look at what is different.
Good luck and sorry but I have no idea what is wrong here.
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2026-01-08 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 10:12 mtd_nandbitserr and seed using pl35x NAND controller Andrea Scian
2025-12-11 16:02 ` Miquel Raynal
[not found] ` <MI2P293MB026440FB793D2D9D1E59ADA797A8A@MI2P293MB0264.ITAP293.PROD.OUTLOOK.COM>
2026-01-08 17:15 ` 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=875x9cyqjg.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=andrea.scian@dave.eu \
--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