[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4C6C7513.2080603@broadcom.com>
Date: Wed, 18 Aug 2010 17:04:35 -0700
From: "Brian Norris" <norris@...adcom.com>
To: "Abdoulaye Walsimou GAYE" <awg@...toolkit.org>
cc: "linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
"Artem Bityutskiy" <dedekind1@...il.com>,
"Linux Kernel" <linux-kernel@...r.kernel.org>,
"mike@...loops.com" <mike@...loops.com>,
"David Woodhouse" <dwmw2@...radead.org>
Subject: Re: [PATCH] mtd: nand: Fix regression in BBM detection
On 08/18/2010 12:30 PM, Abdoulaye Walsimou GAYE wrote:
> Brian,
> Sorry for the long delay!
> I tested the above patch unfortunately it does not help in my case!
Understood. That makes sense. In fact, your problem is most likely *not*
related to this commit. As I mentioned before, please try narrowing down
what specifically caused this; if I read correctly, you jumped from
2.6.33 to 2.6.36-rc1. There have been several important changes between
those releases. Notably, this commit may be giving Samsung chips problems:
426c457a3216fac74e
This thread is covering a few problems with Samsung:
http://lists.infradead.org/pipermail/linux-mtd/2010-August/031590.html
> And when I go further and put a JFFS2 in that partition and boot the
> board I have
<snip>
> Despite these errors I can actually use the board (no kernel panic)!
> The part is Samsung K9F1208U0C - PCB0
Unless you really know what you're doing, I wouldn't be writing/erasing
the flash if it's not detecting bad blocks properly.
Let me know if you have trouble with narrowing down to the problem commit.
Brian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists