From: Sascha Hauer <s.hauer@pengutronix.de>
To: Dmitry Lavnikevich <d.lavnikevich@sam-solutions.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] dts:imx6:pfla02: Align nand partitions by 512k
Date: Tue, 27 Jan 2015 09:09:27 +0100 [thread overview]
Message-ID: <20150127080927.GT12209@pengutronix.de> (raw)
In-Reply-To: <1422013735-19774-1-git-send-email-d.lavnikevich@sam-solutions.com>
+ Teresa, Jan and Christian
On Fri, Jan 23, 2015 at 02:48:55PM +0300, Dmitry Lavnikevich wrote:
> NAND chip used on phyFLEX-i.MX6 with 4GB NAND (MT29F32G08AFACAWP) has
> 512k eraseblock size.
>
> Align NAND partitions by 512k to fix erase fails.
>
> Signed-off-by: Dmitry Lavnikevich <d.lavnikevich@sam-solutions.com>
> ---
> arch/arm/dts/imx6qdl-phytec-pfla02.dtsi | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm/dts/imx6qdl-phytec-pfla02.dtsi b/arch/arm/dts/imx6qdl-phytec-pfla02.dtsi
> index 32ce088fee48..52b279057a33 100644
> --- a/arch/arm/dts/imx6qdl-phytec-pfla02.dtsi
> +++ b/arch/arm/dts/imx6qdl-phytec-pfla02.dtsi
> @@ -95,22 +95,22 @@
>
> partition@1 {
> label = "barebox-environment";
> - reg = <0x400000 0x20000>;
> + reg = <0x400000 0x80000>;
> };
>
> partition@2 {
> label = "oftree";
> - reg = <0x420000 0x20000>;
> + reg = <0x480000 0x80000>;
> };
The partition size for barebox-environment and the devicetree used to be
one eraseblock only. Now it's again only one eraseblock at least for the
4k Page size variants. If one of those blocks is bad the board becomes
unusable. I think the partitions should be at least two eraseblocks.
That of course would make them quite big.
Any opinions about this?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-01-27 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 11:41 [PATCH 1/2] memtest: fix 4GB overflow fail Dmitry Lavnikevich
2015-01-23 11:48 ` [PATCH 2/2] dts:imx6:pfla02: Align nand partitions by 512k Dmitry Lavnikevich
2015-01-27 8:09 ` Sascha Hauer [this message]
2015-01-27 9:35 ` Christian Hemp
2015-01-27 9:39 ` Dmitry Lavnikevich
2015-01-26 9:09 ` [PATCH 1/2] memtest: fix 4GB overflow fail Sascha Hauer
2015-01-26 11:09 ` Dmitry Lavnikevich
2015-01-27 8:10 ` Sascha Hauer
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=20150127080927.GT12209@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=d.lavnikevich@sam-solutions.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox