From: Sean MacLennan <smaclennan@pikatech.com>
To: "Kostas Nakos" <knakos@inaccessnetworks.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] ndfc driver
Date: Tue, 23 Dec 2008 17:00:40 -0500 [thread overview]
Message-ID: <20081223170040.4e58de3f@lappy.seanm.ca> (raw)
In-Reply-To: <4950D8EA.7010905@inaccessnetworks.com>
On Tue, 23 Dec 2008 14:26:18 +0200
"Kostas Nakos" <knakos@inaccessnetworks.com> wrote:
> Hello list,
>
> with respect to Sean's updated patch (
> http://lists.infradead.org/pipermail/linux-mtd/2008-December/023932.html
> ) of the ndfc driver:
>
> We are using an AMCC PPC440EPx based board which requires the ndfc
> driver to handle the nand memory. We have encountered 2 problems with
> this latest patch:
>
> 1) Kernel oops after of_iomap() of ndfc_probe(). The external nand
> memory is bound to chip select 0. The respective dts "reg" line was
> 'reg = <0 d0000000 2000>;'. Using chip selects greater than zero do
> not crash the kernel.
I am not a DTS expert, I just use it ;) But are you sure the second
value should be d0000000?
> 2) Byte order wrong in ndfc_calculate_ecc(). ecc_code[0] and
> ecc_code[1] have been exchanged in this version of the patch which
> lead to ecc errors being reported during mounting (and of course, a
> failed mount operation).
Are you using u-boot and, if so, what version? The ecc_code was
changed to match u-boot. We are using a heavily modified 1.3.3.
This may need to be a config option, since we cannot guarantee what
version of u-boot they are running.
Cheers,
Sean
next prev parent reply other threads:[~2008-12-23 22:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 12:26 [PATCH] ndfc driver Kostas Nakos
2008-12-23 22:00 ` Sean MacLennan [this message]
2008-12-24 6:58 ` knakos
2008-12-27 1:56 ` Sean MacLennan
2008-12-29 10:58 ` Kostas Nakos
2009-01-06 1:23 ` Sean MacLennan
2009-01-07 9:51 ` Kostas Nakos
2009-01-07 17:21 ` Sean MacLennan
2009-01-08 15:37 ` Kostas Nakos
-- strict thread matches above, loose matches on Subject: below --
2008-12-04 3:28 Sean MacLennan
2008-12-04 14:01 ` Josh Boyer
2008-12-04 17:17 ` Sean MacLennan
2008-12-09 0:34 ` Sean MacLennan
2008-12-09 2:11 ` Anton Vorontsov
2008-12-09 2:45 ` Sean MacLennan
2008-12-09 3:32 ` Josh Boyer
2008-12-09 4:54 ` Sean MacLennan
2008-12-09 7:57 ` Mitch Bradley
2008-12-10 4:01 ` Sean MacLennan
2008-12-10 8:28 ` Mitch Bradley
2008-12-09 6:10 ` Stefan Roese
2008-12-09 11:24 ` Josh Boyer
2008-12-10 23:16 ` Sean MacLennan
2008-12-17 4:14 ` Sean MacLennan
2008-12-17 11:34 ` Josh Boyer
2008-12-17 13:26 ` Josh Boyer
2008-12-09 0:51 ` Sean MacLennan
2008-10-30 6:08 Sean MacLennan
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=20081223170040.4e58de3f@lappy.seanm.ca \
--to=smaclennan@pikatech.com \
--cc=knakos@inaccessnetworks.com \
--cc=linux-mtd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox