From: "Brian Norris" <norris@broadcom.com>
To: "Abdoulaye Walsimou GAYE" <awg@embtoolkit.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
"mike@it-loops.com" <mike@it-loops.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH] mtd: nand: Fix regression in BBM detection
Date: Wed, 18 Aug 2010 17:04:35 -0700 [thread overview]
Message-ID: <4C6C7513.2080603@broadcom.com> (raw)
In-Reply-To: <4C6C34DE.2050904@embtoolkit.org>
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
WARNING: multiple messages have this Message-ID (diff)
From: "Brian Norris" <norris@broadcom.com>
To: "Abdoulaye Walsimou GAYE" <awg@embtoolkit.org>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Artem Bityutskiy" <dedekind1@gmail.com>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"mike@it-loops.com" <mike@it-loops.com>,
"David Woodhouse" <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: nand: Fix regression in BBM detection
Date: Wed, 18 Aug 2010 17:04:35 -0700 [thread overview]
Message-ID: <4C6C7513.2080603@broadcom.com> (raw)
In-Reply-To: <4C6C34DE.2050904@embtoolkit.org>
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
next prev parent reply other threads:[~2010-08-19 0:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 11:36 [BUG] Nand support broken with v2.6.36-rc1 Michael Guntsche
2010-08-17 17:00 ` Brian Norris
2010-08-17 17:47 ` Michael Guntsche
2010-08-17 18:49 ` Brian Norris
2010-08-17 20:05 ` Michael Guntsche
2010-08-17 20:06 ` Michael Guntsche
2010-08-17 21:42 ` Brian Norris
2010-08-18 5:53 ` Michael Guntsche
2010-08-17 20:59 ` Abdoulaye Walsimou GAYE
2010-08-17 22:07 ` Brian Norris
2010-08-18 18:25 ` [PATCH] mtd: nand: Fix regression in BBM detection Brian Norris
2010-08-18 18:25 ` Brian Norris
2010-08-18 19:30 ` Abdoulaye Walsimou GAYE
2010-08-18 19:30 ` Abdoulaye Walsimou GAYE
2010-08-19 0:04 ` Brian Norris [this message]
2010-08-19 0:04 ` Brian Norris
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=4C6C7513.2080603@broadcom.com \
--to=norris@broadcom.com \
--cc=awg@embtoolkit.org \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mike@it-loops.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.