From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Ezaul Zillmer <ezaulzillmer@gmail.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
linux-kernel@vger.kernel.org, yassinjaffer@gmail.com,
linux-sunxi@googlegroups.com, robh+dt@kernel.org,
linux-mtd@lists.infradead.org, galak@codeaurora.org,
maxime.ripard@free-electrons.com, computersforpeace@gmail.com,
dwmw2@infradead.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 2/2] mtd: nand: add sunxi NFC dt bindings doc
Date: Tue, 21 Oct 2014 18:01:03 +0200 [thread overview]
Message-ID: <20141021180103.37ca7357@bbrezillon> (raw)
In-Reply-To: <89bb5f8e-2fb0-4012-a8b2-fdd618da8f11@googlegroups.com>
On Tue, 21 Oct 2014 08:03:57 -0700 (PDT)
Ezaul Zillmer <ezaulzillmer@gmail.com> wrote:
> results
> {"K9GBG08U0A 32G 3.3V 8-bit",
> { .id = {0xec, 0xd7, 0x94, 0x7a, 0x54, 0x43} },
> SZ_8K, SZ_4K, SZ_1M, 0, 6, 640, NAND_ECC_INFO(24, SZ_1K) },
>
>
> Start this in the attached image
> ..................................................................
>
> [ 20.127045] Bad eraseblock 2900 at 0x0000b54fe000
> [ 20.134025] Bad eraseblock 2901 at 0x0000b55fe000
> [ 20.140993] Bad eraseblock 2902 at 0x0000b56fe000
> [ 20.147973] Bad eraseblock 2903 at 0x0000b57fe000
> [ 20.154952] Bad eraseblock 2904 at 0x0000b58fe000
> [ 20.161932] Bad eraseblock 2905 at 0x0000b59fe000
> [ 20.168900] Bad eraseblock 2906 at 0x0000b5afe000
> [ 20.175878] Bad eraseblock 2907 at 0x0000b5bfe000
> [ 20.182861] Bad eraseblock 2908 at 0x0000b5cfe000
> [ 20.189828] Bad eraseblock 2909 at 0x0000b5dfe000
> [ 20.196810] Bad eraseblock 2910 at 0x0000b5efe000
> [ 20.203790] Bad eraseblock 2911 at 0x0000b5ffe000
> [ 20.210758] Bad eraseblock 2912 at 0x0000b60fe000
> [ 20.217742] Bad eraseblock 2913 at 0x0000b61fe000
> [ 20.224723] Bad eraseblock 2914 at 0x0000b62fe000
> [ 20.231702] Bad eraseblock 2915 at 0x0000b63fe000
> [ 20.238669] Bad eraseblock 2916 at 0x0000b64fe000
> [ 20.245649] Bad eraseblock 2917 at 0x0000b65fe000
> [ 20.252618] Bad eraseblock 2918 at 0x0000b66fe000
> [ 20.259585] Bad eraseblock 2919 at 0x0000b67fe000
> [ 20.266565] Bad eraseblock 2920 at 0x0000b68fe000
> [ 20.273546] Bad eraseblock 2921 at 0x0000b69fe000
> [ 20.280512] Bad eraseblock 2922 at 0x0000b6afe000
> [ 20.287490] Bad eraseblock 2923 at 0x0000b6bfe000
> [ 20.294468] Bad eraseblock 2924 at 0x0000b6cfe000
> [ 20.301437] Bad eraseblock 2925 at 0x0000b6dfe000
> [ 20.312741] Bad eraseblock 2928 at 0x000. ok
>
>
> I thought this docs of this samsung nand "K9GBG08U0A" that talves be useful
> since you have more knowledge about it! so I can help you make the tests of
> your support in nand cubieboard2.
You have to force bad block erasure to get rid of AW's libnand layout
(which is overriding bad block markers).
Please follow these steps:
1) apply this patch [1]
2) boot on your new kernel and launch
$ flash_erase /dev/mtd0 0 0
3) revert the patch
4) Boot on your new kernel
Most of your bad blocks should be gone after that...
[1]http://code.bulix.org/k2v1hx-87237
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 2/2] mtd: nand: add sunxi NFC dt bindings doc
Date: Tue, 21 Oct 2014 18:01:03 +0200 [thread overview]
Message-ID: <20141021180103.37ca7357@bbrezillon> (raw)
In-Reply-To: <89bb5f8e-2fb0-4012-a8b2-fdd618da8f11@googlegroups.com>
On Tue, 21 Oct 2014 08:03:57 -0700 (PDT)
Ezaul Zillmer <ezaulzillmer@gmail.com> wrote:
> results
> {"K9GBG08U0A 32G 3.3V 8-bit",
> { .id = {0xec, 0xd7, 0x94, 0x7a, 0x54, 0x43} },
> SZ_8K, SZ_4K, SZ_1M, 0, 6, 640, NAND_ECC_INFO(24, SZ_1K) },
>
>
> Start this in the attached image
> ..................................................................
>
> [ 20.127045] Bad eraseblock 2900 at 0x0000b54fe000
> [ 20.134025] Bad eraseblock 2901 at 0x0000b55fe000
> [ 20.140993] Bad eraseblock 2902 at 0x0000b56fe000
> [ 20.147973] Bad eraseblock 2903 at 0x0000b57fe000
> [ 20.154952] Bad eraseblock 2904 at 0x0000b58fe000
> [ 20.161932] Bad eraseblock 2905 at 0x0000b59fe000
> [ 20.168900] Bad eraseblock 2906 at 0x0000b5afe000
> [ 20.175878] Bad eraseblock 2907 at 0x0000b5bfe000
> [ 20.182861] Bad eraseblock 2908 at 0x0000b5cfe000
> [ 20.189828] Bad eraseblock 2909 at 0x0000b5dfe000
> [ 20.196810] Bad eraseblock 2910 at 0x0000b5efe000
> [ 20.203790] Bad eraseblock 2911 at 0x0000b5ffe000
> [ 20.210758] Bad eraseblock 2912 at 0x0000b60fe000
> [ 20.217742] Bad eraseblock 2913 at 0x0000b61fe000
> [ 20.224723] Bad eraseblock 2914 at 0x0000b62fe000
> [ 20.231702] Bad eraseblock 2915 at 0x0000b63fe000
> [ 20.238669] Bad eraseblock 2916 at 0x0000b64fe000
> [ 20.245649] Bad eraseblock 2917 at 0x0000b65fe000
> [ 20.252618] Bad eraseblock 2918 at 0x0000b66fe000
> [ 20.259585] Bad eraseblock 2919 at 0x0000b67fe000
> [ 20.266565] Bad eraseblock 2920 at 0x0000b68fe000
> [ 20.273546] Bad eraseblock 2921 at 0x0000b69fe000
> [ 20.280512] Bad eraseblock 2922 at 0x0000b6afe000
> [ 20.287490] Bad eraseblock 2923 at 0x0000b6bfe000
> [ 20.294468] Bad eraseblock 2924 at 0x0000b6cfe000
> [ 20.301437] Bad eraseblock 2925 at 0x0000b6dfe000
> [ 20.312741] Bad eraseblock 2928 at 0x000. ok
>
>
> I thought this docs of this samsung nand "K9GBG08U0A" that talves be useful
> since you have more knowledge about it! so I can help you make the tests of
> your support in nand cubieboard2.
You have to force bad block erasure to get rid of AW's libnand layout
(which is overriding bad block markers).
Please follow these steps:
1) apply this patch [1]
2) boot on your new kernel and launch
$ flash_erase /dev/mtd0 0 0
3) revert the patch
4) Boot on your new kernel
Most of your bad blocks should be gone after that...
[1]http://code.bulix.org/k2v1hx-87237
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Ezaul Zillmer <ezaulzillmer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
pawel.moll-5wv7dgnIgG8@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org,
galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
yassinjaffer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org
Subject: Re: [PATCH v6 2/2] mtd: nand: add sunxi NFC dt bindings doc
Date: Tue, 21 Oct 2014 18:01:03 +0200 [thread overview]
Message-ID: <20141021180103.37ca7357@bbrezillon> (raw)
In-Reply-To: <89bb5f8e-2fb0-4012-a8b2-fdd618da8f11-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
On Tue, 21 Oct 2014 08:03:57 -0700 (PDT)
Ezaul Zillmer <ezaulzillmer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> results
> {"K9GBG08U0A 32G 3.3V 8-bit",
> { .id = {0xec, 0xd7, 0x94, 0x7a, 0x54, 0x43} },
> SZ_8K, SZ_4K, SZ_1M, 0, 6, 640, NAND_ECC_INFO(24, SZ_1K) },
>
>
> Start this in the attached image
> ..................................................................
>
> [ 20.127045] Bad eraseblock 2900 at 0x0000b54fe000
> [ 20.134025] Bad eraseblock 2901 at 0x0000b55fe000
> [ 20.140993] Bad eraseblock 2902 at 0x0000b56fe000
> [ 20.147973] Bad eraseblock 2903 at 0x0000b57fe000
> [ 20.154952] Bad eraseblock 2904 at 0x0000b58fe000
> [ 20.161932] Bad eraseblock 2905 at 0x0000b59fe000
> [ 20.168900] Bad eraseblock 2906 at 0x0000b5afe000
> [ 20.175878] Bad eraseblock 2907 at 0x0000b5bfe000
> [ 20.182861] Bad eraseblock 2908 at 0x0000b5cfe000
> [ 20.189828] Bad eraseblock 2909 at 0x0000b5dfe000
> [ 20.196810] Bad eraseblock 2910 at 0x0000b5efe000
> [ 20.203790] Bad eraseblock 2911 at 0x0000b5ffe000
> [ 20.210758] Bad eraseblock 2912 at 0x0000b60fe000
> [ 20.217742] Bad eraseblock 2913 at 0x0000b61fe000
> [ 20.224723] Bad eraseblock 2914 at 0x0000b62fe000
> [ 20.231702] Bad eraseblock 2915 at 0x0000b63fe000
> [ 20.238669] Bad eraseblock 2916 at 0x0000b64fe000
> [ 20.245649] Bad eraseblock 2917 at 0x0000b65fe000
> [ 20.252618] Bad eraseblock 2918 at 0x0000b66fe000
> [ 20.259585] Bad eraseblock 2919 at 0x0000b67fe000
> [ 20.266565] Bad eraseblock 2920 at 0x0000b68fe000
> [ 20.273546] Bad eraseblock 2921 at 0x0000b69fe000
> [ 20.280512] Bad eraseblock 2922 at 0x0000b6afe000
> [ 20.287490] Bad eraseblock 2923 at 0x0000b6bfe000
> [ 20.294468] Bad eraseblock 2924 at 0x0000b6cfe000
> [ 20.301437] Bad eraseblock 2925 at 0x0000b6dfe000
> [ 20.312741] Bad eraseblock 2928 at 0x000. ok
>
>
> I thought this docs of this samsung nand "K9GBG08U0A" that talves be useful
> since you have more knowledge about it! so I can help you make the tests of
> your support in nand cubieboard2.
You have to force bad block erasure to get rid of AW's libnand layout
(which is overriding bad block markers).
Please follow these steps:
1) apply this patch [1]
2) boot on your new kernel and launch
$ flash_erase /dev/mtd0 0 0
3) revert the patch
4) Boot on your new kernel
Most of your bad blocks should be gone after that...
[1]http://code.bulix.org/k2v1hx-87237
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Ezaul Zillmer <ezaulzillmer@gmail.com>
Cc: linux-sunxi@googlegroups.com, computersforpeace@gmail.com,
dwmw2@infradead.org, linux-mtd@lists.infradead.org,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, yassinjaffer@gmail.com,
maxime.ripard@free-electrons.com
Subject: Re: [PATCH v6 2/2] mtd: nand: add sunxi NFC dt bindings doc
Date: Tue, 21 Oct 2014 18:01:03 +0200 [thread overview]
Message-ID: <20141021180103.37ca7357@bbrezillon> (raw)
In-Reply-To: <89bb5f8e-2fb0-4012-a8b2-fdd618da8f11@googlegroups.com>
On Tue, 21 Oct 2014 08:03:57 -0700 (PDT)
Ezaul Zillmer <ezaulzillmer@gmail.com> wrote:
> results
> {"K9GBG08U0A 32G 3.3V 8-bit",
> { .id = {0xec, 0xd7, 0x94, 0x7a, 0x54, 0x43} },
> SZ_8K, SZ_4K, SZ_1M, 0, 6, 640, NAND_ECC_INFO(24, SZ_1K) },
>
>
> Start this in the attached image
> ..................................................................
>
> [ 20.127045] Bad eraseblock 2900 at 0x0000b54fe000
> [ 20.134025] Bad eraseblock 2901 at 0x0000b55fe000
> [ 20.140993] Bad eraseblock 2902 at 0x0000b56fe000
> [ 20.147973] Bad eraseblock 2903 at 0x0000b57fe000
> [ 20.154952] Bad eraseblock 2904 at 0x0000b58fe000
> [ 20.161932] Bad eraseblock 2905 at 0x0000b59fe000
> [ 20.168900] Bad eraseblock 2906 at 0x0000b5afe000
> [ 20.175878] Bad eraseblock 2907 at 0x0000b5bfe000
> [ 20.182861] Bad eraseblock 2908 at 0x0000b5cfe000
> [ 20.189828] Bad eraseblock 2909 at 0x0000b5dfe000
> [ 20.196810] Bad eraseblock 2910 at 0x0000b5efe000
> [ 20.203790] Bad eraseblock 2911 at 0x0000b5ffe000
> [ 20.210758] Bad eraseblock 2912 at 0x0000b60fe000
> [ 20.217742] Bad eraseblock 2913 at 0x0000b61fe000
> [ 20.224723] Bad eraseblock 2914 at 0x0000b62fe000
> [ 20.231702] Bad eraseblock 2915 at 0x0000b63fe000
> [ 20.238669] Bad eraseblock 2916 at 0x0000b64fe000
> [ 20.245649] Bad eraseblock 2917 at 0x0000b65fe000
> [ 20.252618] Bad eraseblock 2918 at 0x0000b66fe000
> [ 20.259585] Bad eraseblock 2919 at 0x0000b67fe000
> [ 20.266565] Bad eraseblock 2920 at 0x0000b68fe000
> [ 20.273546] Bad eraseblock 2921 at 0x0000b69fe000
> [ 20.280512] Bad eraseblock 2922 at 0x0000b6afe000
> [ 20.287490] Bad eraseblock 2923 at 0x0000b6bfe000
> [ 20.294468] Bad eraseblock 2924 at 0x0000b6cfe000
> [ 20.301437] Bad eraseblock 2925 at 0x0000b6dfe000
> [ 20.312741] Bad eraseblock 2928 at 0x000. ok
>
>
> I thought this docs of this samsung nand "K9GBG08U0A" that talves be useful
> since you have more knowledge about it! so I can help you make the tests of
> your support in nand cubieboard2.
You have to force bad block erasure to get rid of AW's libnand layout
(which is overriding bad block markers).
Please follow these steps:
1) apply this patch [1]
2) boot on your new kernel and launch
$ flash_erase /dev/mtd0 0 0
3) revert the patch
4) Boot on your new kernel
Most of your bad blocks should be gone after that...
[1]http://code.bulix.org/k2v1hx-87237
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-21 16:01 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 11:45 [PATCH v6 0/2] mtd: nand: add sunxi NAND flash controller support Boris Brezillon
2014-10-20 11:45 ` Boris Brezillon
2014-10-20 11:45 ` Boris Brezillon
2014-10-20 11:45 ` Boris Brezillon
2014-10-20 11:45 ` [PATCH v6 1/2] " Boris Brezillon
2014-10-20 11:45 ` Boris Brezillon
2014-10-20 11:45 ` Boris Brezillon
2014-10-20 11:45 ` Boris Brezillon
2014-10-20 12:01 ` Varka Bhadram
2014-10-20 12:01 ` Varka Bhadram
2014-10-20 12:01 ` Varka Bhadram
2014-10-20 12:01 ` Varka Bhadram
2014-10-20 12:29 ` Boris Brezillon
2014-10-20 12:29 ` Boris Brezillon
2014-10-20 12:29 ` Boris Brezillon
2014-10-20 12:29 ` Boris Brezillon
2014-10-21 2:28 ` Brian Norris
2014-10-21 2:28 ` Brian Norris
2014-10-21 2:28 ` Brian Norris
2014-10-21 2:28 ` Brian Norris
2014-10-20 11:45 ` [PATCH v6 2/2] mtd: nand: add sunxi NFC dt bindings doc Boris Brezillon
2014-10-20 11:45 ` Boris Brezillon
2014-10-20 11:45 ` Boris Brezillon
2014-10-20 11:45 ` Boris Brezillon
2014-10-21 2:41 ` Brian Norris
2014-10-21 2:41 ` Brian Norris
2014-10-21 2:41 ` Brian Norris
2014-10-21 2:41 ` Brian Norris
2014-10-21 12:53 ` Boris Brezillon
2014-10-21 12:53 ` Boris Brezillon
2014-10-21 12:53 ` Boris Brezillon
2014-10-21 12:53 ` Boris Brezillon
2014-10-21 13:13 ` Ezaul Zillmer
[not found] ` <62d54110-9c7f-4342-9201-a1ae23194620-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-10-21 13:15 ` Ezaul Zillmer
2014-10-21 13:48 ` Boris Brezillon
2014-10-21 13:48 ` Boris Brezillon
2014-10-21 13:48 ` Boris Brezillon
2014-10-21 13:58 ` Boris Brezillon
2014-10-21 13:58 ` Boris Brezillon
2014-10-21 13:58 ` Boris Brezillon
2014-10-21 13:58 ` Boris Brezillon
2014-10-21 15:03 ` Ezaul Zillmer
[not found] ` <89bb5f8e-2fb0-4012-a8b2-fdd618da8f11-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-10-21 15:46 ` Ezaul Zillmer
2014-10-21 16:01 ` Boris Brezillon [this message]
2014-10-21 16:01 ` Boris Brezillon
2014-10-21 16:01 ` Boris Brezillon
2014-10-21 16:01 ` Boris Brezillon
2014-10-22 11:17 ` Ezaul Zillmer
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=20141021180103.37ca7357@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=ezaulzillmer@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=yassinjaffer@gmail.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 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.