From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: BCM5301X: Fix NAND ECC parameters for Linksys Panamera
Date: Mon, 12 Mar 2018 15:52:27 -0700 [thread overview]
Message-ID: <2ef6e4fc-cce7-372e-e35f-578fd6ada9ca@gmail.com> (raw)
In-Reply-To: <20180311100313.znonhesgh462rz65@osboxes>
On 03/11/2018 03:03 AM, Vivek Unune wrote:
> Hi Rafa?,
>
> On Sat, Mar 10, 2018 at 10:41:04PM +0100, Rafa? Mi?ecki wrote:
>> On 10 March 2018 at 18:12, Vivek Unune <npcomplete13@gmail.com> wrote:
>>> Using BCH8 gives ecc errors and makes the router unsuable.
>>> Switching to BCH1 fixes these errors.
>>
>> Can you provide CFE's log messages starting with
>> "Decompressing...done" and up to the "Press Ctrl+C to stop in CFE"
>> please? I'd like to see what NAND info CFE prints there.
>
> See below. It does say BCH-8, however I can't get it to work.
>
> CFE log:
>
> Decompressing...done
> Found a Toshiba NAND flash:
> Total size: 128MB
> Block size: 128KB
> Page Size: 2048B
> OOB Size: 64B
> Sector size: 512B
> Spare size: 16B
> ECC level: 8 (8-bit)
> Device ID: 0x98 0xf1 0x80 0x15 0xf2 0x16
> find_devinfo: devinfo block found at 0x00180000!
>
> Press Ctrl+C to stop in CFE
What kind of error are you getting in Linux with BCH-8?
--
--
Florian
WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com>
To: "Vivek Unune" <npcomplete13@gmail.com>,
"Rafał Miłecki" <zajec5@gmail.com>
Cc: Hauke Mehrtens <hauke@hauke-m.de>,
Jon Mason <jonmason@broadcom.com>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: BCM5301X: Fix NAND ECC parameters for Linksys Panamera
Date: Mon, 12 Mar 2018 15:52:27 -0700 [thread overview]
Message-ID: <2ef6e4fc-cce7-372e-e35f-578fd6ada9ca@gmail.com> (raw)
In-Reply-To: <20180311100313.znonhesgh462rz65@osboxes>
On 03/11/2018 03:03 AM, Vivek Unune wrote:
> Hi Rafał,
>
> On Sat, Mar 10, 2018 at 10:41:04PM +0100, Rafał Miłecki wrote:
>> On 10 March 2018 at 18:12, Vivek Unune <npcomplete13@gmail.com> wrote:
>>> Using BCH8 gives ecc errors and makes the router unsuable.
>>> Switching to BCH1 fixes these errors.
>>
>> Can you provide CFE's log messages starting with
>> "Decompressing...done" and up to the "Press Ctrl+C to stop in CFE"
>> please? I'd like to see what NAND info CFE prints there.
>
> See below. It does say BCH-8, however I can't get it to work.
>
> CFE log:
>
> Decompressing...done
> Found a Toshiba NAND flash:
> Total size: 128MB
> Block size: 128KB
> Page Size: 2048B
> OOB Size: 64B
> Sector size: 512B
> Spare size: 16B
> ECC level: 8 (8-bit)
> Device ID: 0x98 0xf1 0x80 0x15 0xf2 0x16
> find_devinfo: devinfo block found at 0x00180000!
>
> Press Ctrl+C to stop in CFE
What kind of error are you getting in Linux with BCH-8?
--
--
Florian
next prev parent reply other threads:[~2018-03-12 22:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-10 17:12 [PATCH] ARM: BCM5301X: Fix NAND ECC parameters for Linksys Panamera Vivek Unune
2018-03-10 17:12 ` Vivek Unune
2018-03-10 21:41 ` Rafał Miłecki
2018-03-10 21:41 ` Rafał Miłecki
2018-03-11 10:03 ` Vivek Unune
2018-03-11 10:03 ` Vivek Unune
2018-03-12 22:52 ` Florian Fainelli [this message]
2018-03-12 22:52 ` Florian Fainelli
2018-03-13 1:02 ` Vivek Unune
2018-03-13 1:02 ` Vivek Unune
2018-04-25 9:02 ` Rafał Miłecki
2018-04-25 9:02 ` Rafał Miłecki
2018-04-25 9:02 ` Rafał Miłecki
2018-04-27 14:05 ` Vivek Unune
2018-04-27 14:05 ` Vivek Unune
2018-04-27 14:05 ` Vivek Unune
2018-04-28 4:19 ` Vivek Unune
2018-04-28 4:19 ` Vivek Unune
2018-04-28 6:44 ` Rafał Miłecki
2018-04-28 6:44 ` Rafał Miłecki
2018-04-25 8:51 ` Rafał Miłecki
2018-04-25 8:51 ` Rafał Miłecki
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=2ef6e4fc-cce7-372e-e35f-578fd6ada9ca@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.