From mboxrd@z Thu Jan 1 00:00:00 1970 From: boris.brezillon@free-electrons.com (Boris Brezillon) Date: Sun, 7 Jan 2018 22:26:05 +0100 Subject: [PATCH 00/12] Marvell NAND controller rework with ->exec_op() In-Reply-To: <20180107221911.51115566@bbrezillon> References: <20171207201814.30411-1-miquel.raynal@free-electrons.com> <20171214070930.0b885f6d@bbrezillon> <877etkecig.fsf@belgarion.home> <20171218092535.2ca1fe13@xps13> <87y3lxccr7.fsf@belgarion.home> <20171220224121.2cb6f690@bbrezillon> <87lghucykr.fsf@belgarion.home> <20171222222441.0fd77df9@bbrezillon> <20171222233730.68d9cb9d@xps13> <87k1xdblxf.fsf@belgarion.home> <20171223155709.2ba16e95@xps13> <87fu81bc45.fsf@belgarion.home> <20180102120326.7a2cf1d1@xps13> <87d12scbiy.fsf@belgarion.home> <20180103084037.422b239a@xps13> <878tded89m.fsf@belgarion.home> <20180103211028.619cd16d@bbrezillon> <20180103215206.5d85b41b@bbrezillon> <874lnxcrsq.fsf@belgarion.home> <20180107220911.31844b3a@xps13> <20180107221911.51115566@bbrezillon> Message-ID: <20180107222605.6dd739b3@bbrezillon> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Sun, 7 Jan 2018 22:19:11 +0100 Boris Brezillon wrote: > On Sun, 7 Jan 2018 22:09:11 +0100 > Miquel RAYNAL wrote: > > > Hi Robert, > > > > On Sun, 07 Jan 2018 21:55:33 +0100 > > Robert Jarzmik wrote: > > > > > Boris Brezillon writes: > > > > > > > On Wed, 3 Jan 2018 21:10:28 +0100 > > > > Boris Brezillon wrote: > > > >> Hm, that's weird. Can you try with the old driver (pxa3xx)? > > > Ah you're right, my NAND was damaged ... > > > > > > > Alternatively, you can type 'nand bad' from uboot to check if it > > > > detects the same bad blocks. > > > Mmmh no, the SPL is barebox in my case. Do you have a command in > > > linux or barebox to do the same thing ? > > > > Not sure, but nand -i should do the trick. > > https://www.barebox.org/doc/latest/commands/hwmanip/nand.html > > > > But I am not sure this is still relevant now we know the NAND was > > damaged by the previous experiments (sorry about that). Can you put the > > NAND in a clean state and report us if it is still failing? > > In order to do that you'll have to scrub the blocks storing the BBT, and > I'm not sure barebox supports that. Linux does not, for sure, so if you > want to forcibly erase bad blocks from linux, you'll have to comment > these lines [1]. Apparently there's a "nand -g " command to mark a block good in barebox. After doing that you should be able to erase the blocks storing the BBT (it should be placed in the last 2 blocks of the NAND). > > [1]http://elixir.free-electrons.com/linux/v4.15-rc6/source/drivers/mtd/nand/nand_base.c#L3056