From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Brezillon Subject: Re: [PATCH v2 3/6] mtd: rawnand: add NVIDIA Tegra NAND Flash controller driver Date: Mon, 28 May 2018 18:57:14 +0200 Message-ID: <20180528185714.0a33bdc7@bbrezillon> References: <20180527215442.14760-4-stefan@agner.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Benjamin Lindqvist Cc: Stefan Agner , Dmitry Osipenko , David Woodhouse , Brian Norris , Marek =?UTF-8?B?VmHFoXV0?= , robh+dt@kernel.org, mark.rutland@arm.com, Thierry Reding , Michael Turquette , sboyd@kernel.org, Lucas Stach , Miquel Raynal , richard@nod.at, Marcel Ziswiler , krzk@kernel.org, jonathanh@nvidia.com, pdeschrijver@nvidia.com, Prashant Gaikwad , Mirza Krak , linux-mtd@lists.infradead.org, linux-tegra@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org List-Id: devicetree@vger.kernel.org On Mon, 28 May 2018 18:41:26 +0200 Benjamin Lindqvist wrote: > Note that it's certainly possible to encode U-Boot and kernel with > RS[4] and still use RS[8] for the rootfs even if the boot rom doesn't > support it. Not if you want to read/write from/to the uboot partition from Linux. Per-partition ECC setup is not supported, so the only solutions we have right now are: 1/ use the same ECC config as the one use by the bootrom 2/ only access uboot partition in raw mode from Linux (that implies generating images containing the ECC bytes so that they can be flashed to the device in raw mode) 3/ never access uboot partitions from Linux (not sure we want that) > This whole 'use-bootable-ecc-only' business seems a bit > overengineered. > Hm, I don't find it over-engineered.