From: Felix Radensky <felix@embedded-sol.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: Long boot delay on 460EX with 2.6.28-rc8
Date: Fri, 19 Dec 2008 22:51:21 -0800 (PST) [thread overview]
Message-ID: <21102440.post@talk.nabble.com> (raw)
In-Reply-To: <20081220003704.26bfb042@lappy.seanm.ca>
Sean MacLennan-2 wrote:
>
> On Fri, 19 Dec 2008 23:23:58 +0200
> "Felix Radensky" <felix@embedded-sol.com> wrote:
>
>> Hi, Sean
>>
>> Do you have any ideas what can cause such delay ?
>
> Sorry, I haven't been following this thread :(
>
> We also use a 256M NAND, although a Spansion S29GL. While there is a
> small delay in u-boot, there is no noticeable during the ndfc startup.
>
> Can you read and write the NAND properly in u-boot? That is always the
> first step. If that works, we can look at what might be different
> between the u-boot and the ndfc driver.
>
> Cheers,
> Sean
>
>
Thanks, Sean
I've found the cause of the delay. It was a stupid error on my part, not
related to ndfc driver, which is fine. Thanks a lot for you work on this.
I apologize for the noise.
Felix.
--
View this message in context: http://www.nabble.com/Long-boot-delay-on-460EX-with-2.6.28-rc8-tp21070179p21102440.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.
next prev parent reply other threads:[~2008-12-20 6:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 10:29 Long boot delay on 460EX with 2.6.28-rc8 Felix Radensky
2008-12-18 16:02 ` Anton Vorontsov
2008-12-18 18:51 ` Kumar Gala
2008-12-18 19:01 ` Anton Vorontsov
2008-12-18 22:57 ` Michael Ellerman
2008-12-18 19:02 ` Josh Boyer
2008-12-19 7:36 ` Felix Radensky
2008-12-19 7:56 ` Stefan Roese
2008-12-19 8:30 ` Felix Radensky
2008-12-19 8:30 ` Felix Radensky
2008-12-19 21:23 ` Felix Radensky
2008-12-20 5:37 ` Sean MacLennan
2008-12-20 6:51 ` Felix Radensky [this message]
2008-12-22 22:22 ` Leon Woestenberg
2008-12-24 21:40 ` Felix Radensky
2008-12-18 20:04 ` Wolfgang Denk
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=21102440.post@talk.nabble.com \
--to=felix@embedded-sol.com \
--cc=linuxppc-dev@ozlabs.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.