From: Sean MacLennan <smaclennan@pikatech.com>
To: "Kostas Nakos" <knakos@inaccessnetworks.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] ndfc driver
Date: Mon, 5 Jan 2009 20:23:40 -0500 [thread overview]
Message-ID: <20090105202340.7fd0f8c1@lappy.seanm.ca> (raw)
In-Reply-To: <4958AD4E.8090608@inaccessnetworks.com>
On Mon, 29 Dec 2008 12:58:22 +0200
"Kostas Nakos" <knakos@inaccessnetworks.com> wrote:
> Alright, with:
>
> <0 0 2000> ->
>
> __ioremap(): phys addr 0x0 is RAM lr c0008c94
> ndfc 0.ndfc: failed to get memory
> ndfc: probe of 0.ndfc failed with error -5
>
> I notice that the 0xd0000000 value is also defined in the (our)
> platform include for our platform in u-boot (include/configs/...):
>
> #define CFG_NAND_ADDR 0xd0000000
That is where the NAND is on the warp. Could you post the complete dts?
Cheers,
Sean
next prev parent reply other threads:[~2009-01-06 1:23 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
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 [this message]
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=20090105202340.7fd0f8c1@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