From: John Crispin <blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
To: Boris Brezillon
<boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: "Steven Liu (劉人豪)"
<steven.liu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
erin.lo-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org,
"Sean Wang (王志亘)"
<sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
"Jorge Ramirez-Ortiz"
<jorge.ramirez-ortiz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: MTK Smart Device Gen1 NAND Driver - Testing on MT7623
Date: Wed, 27 Apr 2016 10:41:31 +0200 [thread overview]
Message-ID: <869e6090-04fd-0f99-f248-af68e948362e@openwrt.org> (raw)
In-Reply-To: <20160427100627.63b148c3@bbrezillon>
Hi Boris,
>>
>> the devicetree i am using is this
>>
>> &nandc {
>> status = "okay";
>> pinctrl-names = "default";
>> pinctrl-0 = <&nand_pins_default>;
>> nand@0 {
>> reg = <0>;
>> spare_per_sector = <64>;
>
> If I understood the meaning of spare_per_sector correctly, this should
> be 32 (you have 2K pages and 1024 bytes sectors, so you have 2 sectors
> and want to equally assign the 64 OOB bytes to those sectors =>
> 64 / 2 = 32).
>
> Anyway, hopefully all this complexity will be gone in the next version
> along with the need to define nand-ecc-strength and nand-ecc-step-size
> (which should be part of the NAND chip detection unless you really
> need to overload them).
>
thanks for the info. i tried that aswell as some other settings but none
makes the flash work. lets see if Jorge has some ideas. otherwise i will
wait for V4.
John
>> nand-on-flash-bbt;
>> nand-ecc-mode = "hw";
>> nand-ecc-strength = <12>;
>> nand-ecc-step-size = <1024>;
>> partitions {
>> compatible = "fixed-partitions";
>> #address-cells = <1>;
>> #size-cells = <1>;
>>
>> partition@C0000 {
>> label = "uboot-env";
>> reg = <0xC0000 0x40000>;
>> };
>>
>> partition@100000 {
>> label = "factory";
>> reg = <0x100000 0x40000>;
>> };
>>
>> partition@140000 {
>> label = "kernel";
>> reg = <0x140000 0x2000000>;
>> };
>>
>> partition@2140000 {
>> label = "recovery";
>> reg = <0x2140000 0x2000000>;
>> };
>>
>> partition@4140000 {
>> label = "rootfs";
>> reg = <0x4140000 0x1000000>;
>> };
>> };
>> };
>> };
>
>
next prev parent reply other threads:[~2016-04-27 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 6:36 MTK Smart Device Gen1 NAND Driver - Testing on MT7623 John Crispin
[not found] ` <e397161c-2fe8-7e9d-c34f-adf5e91a99d7-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2016-04-27 8:06 ` Boris Brezillon
2016-04-27 8:41 ` John Crispin [this message]
[not found] ` <869e6090-04fd-0f99-f248-af68e948362e-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2016-04-27 11:43 ` Jorge Ramirez
[not found] ` <5720A5F5.8060602-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-04-27 11:47 ` John Crispin
[not found] ` <1461814664.8414.112.camel@mhfsdcap03>
2016-04-28 12:13 ` John Crispin
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=869e6090-04fd-0f99-f248-af68e948362e@openwrt.org \
--to=blogic-p3rkhjxn3npafugrpc6u6w@public.gmane.org \
--cc=boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
--cc=erin.lo-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=jorge.ramirez-ortiz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
--cc=steven.liu-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org \
/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