lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 25 Mar 2015 15:02:28 +0100
From:	Richard Weinberger <richard@....at>
To:	linux-mtd@...ts.infradead.org
Cc:	linux-kernel@...r.kernel.org, dwmw2@...radead.org,
	computersforpeace@...il.com
Subject: [RFC] On-die ECC support

Some Micron NAND chips offer an on-die ECC (AKA internal ECC) feature,
in this mode all ECC is automatically performed by the NAND chips itself.
Most user are happy with software ECC or hardware ECC performed by the
NFC (NAND flash controller).
But there are situations where multi-bit hardware ECC is not available,
some AT91 based SoCs for example, and due to CPU limitations
software ECC is not feasible. In such situations on-die ECC can help.
People are using that feature in the wild for years.
As this feature is not supported in mainline these guys are using out-of-tree
patches of doubtful quality. That's why I did that patch series.

This series is based on patches by David Mosberger and in-house patches
by a customer.

Currently I'm not happy with patch 2/3.
To allow raw access (access without ECC) we have to disable/enable
on-die ECC mode in various NAND core functions.
I could also think of dropping support for raw access completely.

I'd like to thank Ammonit Measurement GmbH for making this contribution to the MTD community happen!

[PATCH 1/3] mtd: nand: Add on-die ECC support
[PATCH 2/3] mtd: nand: Add support for raw access when using on-die
[PATCH 3/3] mtd: nand: Wire up on-die ECC support

Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ