From: Miquel Raynal <miquel.raynal@bootlin.com>
To: u-boot@lists.denx.de
Subject: porting marvell-nand driver for u-boot
Date: Wed, 11 Mar 2020 10:28:23 +0100 [thread overview]
Message-ID: <20200311102823.453a0e34@xps13> (raw)
In-Reply-To: <BN8PR10MB3379C0726BA1441C76938B268CFE0@BN8PR10MB3379.namprd10.prod.outlook.com>
Hi Zak,
Zak Hays <zak.hays@lexmark.com> wrote on Mon, 9 Mar 2020 14:27:15 +0000:
> Hi Miqu?l,
>
> Thanks for the quick response!
>
> >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.
>
> Yes, I am aware of this and have other plans to save away the contents
> of the NAND device and rewrite with the new block sizing.
>
> >Otherwise, I think subpage access are supported by the pxa driver.
>
> Can you clarify this a little more? It looks like the u-boot pxa
> driver sets the NAND_NO_SUBPAGE_WRITE option by default in
> alloc_nand_resource(). That decides the value of mtd->subpage_sft in
> nand_base which ultimately leads to the UBI error I get below. Does
> the NO_SUBPAGE_WRITE automatically imply that SUBPAGE_READ is not
> allowed as well? Is there some other way to bypass this flag?
I think subpage_read are still allowed if the NAND part supports it.
But anyway, if they are enabled in Linux, they should be enabled in
U-Boot otherwise UBI will complain I suppose...
Thanks,
Miqu?l
prev parent reply other threads:[~2020-03-11 9:28 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
2020-03-09 14:27 ` Zak Hays
2020-03-11 9:28 ` 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=20200311102823.453a0e34@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 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.