All of lore.kernel.org
 help / color / mirror / Atom feed
From: <markus.stockhausen@gmx.de>
To: "'Miquel Raynal'" <miquel.raynal@bootlin.com>
Cc: <vigneshr@ti.com>, <richard@nod.at>, <tudor.ambarus@linaro.org>,
	<linux-mtd@lists.infradead.org>,
	"'Chris Packham'" <Chris.Packham@alliedtelesis.co.nz>
Subject: AW: AW: AW: NAND ECC errors
Date: Fri, 8 Aug 2025 15:21:40 +0200	[thread overview]
Message-ID: <05e301dc0867$6195e760$24c1b620$@gmx.de> (raw)
In-Reply-To: <87ikiy9e9n.fsf@bootlin.com>

> Von: linux-mtd <linux-mtd-bounces@lists.infradead.org> Im Auftrag von Miquel Raynal
> Gesendet: Freitag, 8. August 2025 14:42
> 
> On 08/08/2025 at 14:25:18 +02, <markus.stockhausen@gmx.de> wrote:
> Just to fully understand, you are trying to replicate what the software
> BCH engine of your realtek SPI controller does?
>
> If so, why not just configuring the engine directly and use it? It will
> be much faster and easier to do.
>
> Otherwise, if you're trying to do in software what the hardware does,
> you must be prepared to more maths:
> https://bootlin.com/blog/supporting-a-misbehaving-nand-ecc-engine/

Idea was to start with something I have fully understood. Wantet to
leave Hardware for later as ECC is a total new area now (as it was with 
NAND the last week). Had a short look at the hardware engine GPL 
code. The most basic parts look straight forward with three functions

- Prepare to to encoded data
- Prepare to be decoded data
- Kick engine

ecc-mtk seems tightly integrated into the nand contoller while 
ecc-mxic seems to be some passthrough/pipeline integration.

What would be your advise for the most simple enhancement 
for our existing Realtek spi-mem controller?

Markus


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2025-08-08 13:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-07 15:16 NAND ECC errors markus.stockhausen
2025-08-07 20:36 ` Chris Packham
2025-08-07 21:23   ` AW: " markus.stockhausen
2025-08-07 21:32     ` Chris Packham
2025-08-08  8:41       ` Miquel Raynal
2025-08-08 12:25         ` AW: " markus.stockhausen
2025-08-08 12:41           ` Miquel Raynal
2025-08-08 13:21             ` markus.stockhausen [this message]
2025-08-08 13:31               ` AW: " Miquel Raynal
2025-08-08  8:37   ` Miquel Raynal

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='05e301dc0867$6195e760$24c1b620$@gmx.de' \
    --to=markus.stockhausen@gmx.de \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=tudor.ambarus@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.