From: Roland Stigge <stigge@antcom.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-mtd@lists.infradead.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: mxc_nand.c on mach-imx/imx53
Date: Mon, 03 Sep 2012 11:10:27 +0200 [thread overview]
Message-ID: <50447403.4010003@antcom.de> (raw)
In-Reply-To: <20120903085517.GE26594@pengutronix.de>
On 09/03/2012 10:55 AM, Sascha Hauer wrote:
> On Fri, Aug 31, 2012 at 12:57:37PM +0200, Roland Stigge wrote:
>> On 08/31/2012 11:05 AM, Roland Stigge wrote:
>>> I tried to port this on top of Sascha's patches for imx53, only for mxc v3 for now, as below.
>>>
>>> Unfortunately, I still get:
>>>
>>> ...
>>> UnCorrectable RS-ECC Error
>>> UnCorrectable RS-ECC Error
>>> UnCorrectable RS-ECC Error
>>> UnCorrectable RS-ECC Error
>>> UnCorrectable RS-ECC Error
>
> Have you written the data you are unable to read with this driver?
No, maybe that's one of the reasons. The bootloader also seems to
implement a different on-flash layout. But as written, the problem is
gone with the below fix.
>> --- linux-2.6.orig/drivers/mtd/nand/mxc_nand.c
>> +++ linux-2.6/drivers/mtd/nand/mxc_nand.c
>> @@ -1141,14 +1141,14 @@ static void mxc_nand_command(struct mtd_
>> host->devtype_data->send_cmd(host, command, true);
>> mxc_do_addr_cycle(mtd, column, page_addr);
>> host->devtype_data->send_read_id(host);
>> - host->buf_start = column;
>> + host->buf_start = 0;
>> break;
>>
>> case NAND_CMD_PARAM:
>> host->devtype_data->send_cmd(host, command, true);
>> mxc_do_addr_cycle(mtd, column, page_addr);
>> host->devtype_data->send_read_param(host);
>> - host->buf_start = column;
>> + host->buf_start = 0;
>
> On what tree are you working? I cannot find a handling of
> NAND_CMD_PARAM in my tree.
That's on top of the patch I ported from Eric's barebox driver (other
mail, but only for imx53/v3 for now). Sorry for the confusion.
I can prepare a single patch, but maybe Eric's more knowledgeable on
this driver (including v1/v2 that I can't test), he announced a patch
for this week.
Roland
WARNING: multiple messages have this Message-ID (diff)
From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: mxc_nand.c on mach-imx/imx53
Date: Mon, 03 Sep 2012 11:10:27 +0200 [thread overview]
Message-ID: <50447403.4010003@antcom.de> (raw)
In-Reply-To: <20120903085517.GE26594@pengutronix.de>
On 09/03/2012 10:55 AM, Sascha Hauer wrote:
> On Fri, Aug 31, 2012 at 12:57:37PM +0200, Roland Stigge wrote:
>> On 08/31/2012 11:05 AM, Roland Stigge wrote:
>>> I tried to port this on top of Sascha's patches for imx53, only for mxc v3 for now, as below.
>>>
>>> Unfortunately, I still get:
>>>
>>> ...
>>> UnCorrectable RS-ECC Error
>>> UnCorrectable RS-ECC Error
>>> UnCorrectable RS-ECC Error
>>> UnCorrectable RS-ECC Error
>>> UnCorrectable RS-ECC Error
>
> Have you written the data you are unable to read with this driver?
No, maybe that's one of the reasons. The bootloader also seems to
implement a different on-flash layout. But as written, the problem is
gone with the below fix.
>> --- linux-2.6.orig/drivers/mtd/nand/mxc_nand.c
>> +++ linux-2.6/drivers/mtd/nand/mxc_nand.c
>> @@ -1141,14 +1141,14 @@ static void mxc_nand_command(struct mtd_
>> host->devtype_data->send_cmd(host, command, true);
>> mxc_do_addr_cycle(mtd, column, page_addr);
>> host->devtype_data->send_read_id(host);
>> - host->buf_start = column;
>> + host->buf_start = 0;
>> break;
>>
>> case NAND_CMD_PARAM:
>> host->devtype_data->send_cmd(host, command, true);
>> mxc_do_addr_cycle(mtd, column, page_addr);
>> host->devtype_data->send_read_param(host);
>> - host->buf_start = column;
>> + host->buf_start = 0;
>
> On what tree are you working? I cannot find a handling of
> NAND_CMD_PARAM in my tree.
That's on top of the patch I ported from Eric's barebox driver (other
mail, but only for imx53/v3 for now). Sorry for the confusion.
I can prepare a single patch, but maybe Eric's more knowledgeable on
this driver (including v1/v2 that I can't test), he announced a patch
for this week.
Roland
WARNING: multiple messages have this Message-ID (diff)
From: Roland Stigge <stigge@antcom.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "Eric Bénard" <eric@eukrea.com>,
linux-mtd@lists.infradead.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: mxc_nand.c on mach-imx/imx53
Date: Mon, 03 Sep 2012 11:10:27 +0200 [thread overview]
Message-ID: <50447403.4010003@antcom.de> (raw)
In-Reply-To: <20120903085517.GE26594@pengutronix.de>
On 09/03/2012 10:55 AM, Sascha Hauer wrote:
> On Fri, Aug 31, 2012 at 12:57:37PM +0200, Roland Stigge wrote:
>> On 08/31/2012 11:05 AM, Roland Stigge wrote:
>>> I tried to port this on top of Sascha's patches for imx53, only for mxc v3 for now, as below.
>>>
>>> Unfortunately, I still get:
>>>
>>> ...
>>> UnCorrectable RS-ECC Error
>>> UnCorrectable RS-ECC Error
>>> UnCorrectable RS-ECC Error
>>> UnCorrectable RS-ECC Error
>>> UnCorrectable RS-ECC Error
>
> Have you written the data you are unable to read with this driver?
No, maybe that's one of the reasons. The bootloader also seems to
implement a different on-flash layout. But as written, the problem is
gone with the below fix.
>> --- linux-2.6.orig/drivers/mtd/nand/mxc_nand.c
>> +++ linux-2.6/drivers/mtd/nand/mxc_nand.c
>> @@ -1141,14 +1141,14 @@ static void mxc_nand_command(struct mtd_
>> host->devtype_data->send_cmd(host, command, true);
>> mxc_do_addr_cycle(mtd, column, page_addr);
>> host->devtype_data->send_read_id(host);
>> - host->buf_start = column;
>> + host->buf_start = 0;
>> break;
>>
>> case NAND_CMD_PARAM:
>> host->devtype_data->send_cmd(host, command, true);
>> mxc_do_addr_cycle(mtd, column, page_addr);
>> host->devtype_data->send_read_param(host);
>> - host->buf_start = column;
>> + host->buf_start = 0;
>
> On what tree are you working? I cannot find a handling of
> NAND_CMD_PARAM in my tree.
That's on top of the patch I ported from Eric's barebox driver (other
mail, but only for imx53/v3 for now). Sorry for the confusion.
I can prepare a single patch, but maybe Eric's more knowledgeable on
this driver (including v1/v2 that I can't test), he announced a patch
for this week.
Roland
next prev parent reply other threads:[~2012-09-03 9:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 9:30 mxc_nand.c on mach-imx/imx53 Roland Stigge
2012-08-23 9:30 ` Roland Stigge
2012-08-29 7:41 ` Sascha Hauer
2012-08-29 7:41 ` Sascha Hauer
2012-08-29 15:20 ` Roland Stigge
2012-08-29 15:20 ` Roland Stigge
2012-08-29 15:28 ` Eric Bénard
2012-08-29 15:28 ` Eric Bénard
2012-08-31 9:05 ` Roland Stigge
2012-08-31 9:05 ` Roland Stigge
2012-08-31 10:57 ` Roland Stigge
2012-08-31 10:57 ` Roland Stigge
2012-09-03 8:55 ` Sascha Hauer
2012-09-03 8:55 ` Sascha Hauer
2012-09-03 8:55 ` Sascha Hauer
2012-09-03 9:10 ` Roland Stigge [this message]
2012-09-03 9:10 ` Roland Stigge
2012-09-03 9:10 ` Roland Stigge
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=50447403.4010003@antcom.de \
--to=stigge@antcom.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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.