From: Miquel Raynal <miquel.raynal@bootlin.com>
To: u-boot@lists.denx.de
Subject: porting marvell-nand driver for u-boot
Date: Fri, 6 Mar 2020 09:48:18 +0100 [thread overview]
Message-ID: <20200306094818.37d10986@xps13> (raw)
In-Reply-To: <BN8PR10MB33796155FF3F5C08909EB3EB8CE20@BN8PR10MB3379.namprd10.prod.outlook.com>
Hi Zak,
Zak Hays <zak.hays@lexmark.com> wrote on Thu, 5 Mar 2020 19:09:54 +0000:
> Hello all!
>
> I've recently run into an issue where I have enabled on-die ECC in Linux which required the block sizing I had been using to change from 2048 to 512. This is now causing UBI to throw the following error:
You know that you cannot do that and keep the content of your NAND
device right? You are basically enabling subpage access and UBI does
not support subpage changes.
Otherwise, I think subpage access are supported by the pxa driver.
> ubi0 error: ubi_io_read: error -74 (ECC error) while reading 64 bytes from PEB 0:0, read 64 bytes
> ubi0 error: validate_ec_hdr: bad VID header offset 512, expected 2048
> ubi0 error: validate_ec_hdr: bad EC header
>
> As far as I can tell, the 2048 value is hard-coded in the current pxa nand driver I had been using in u-boot. It seems like the preferred path to proceed would be to port the current marvell-nand driver from Linux into u-boot but that seems a little more involved as it will require changes to the core nand driver as well. Are there any current plans to adapt these changes from v4.16+ of Linux? If so, is there a patch set somewhere that I could pull in to start testing?
>
> Thanks!
> Zak Hays
Thanks,
Miqu?l
next prev parent reply other threads:[~2020-03-06 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 19:09 porting marvell-nand driver for u-boot Zak Hays
2020-03-06 8:48 ` Miquel Raynal [this message]
2020-03-09 14:27 ` Zak Hays
2020-03-11 9:28 ` 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=20200306094818.37d10986@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=u-boot@lists.denx.de \
/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