linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Felix Radensky <felix@embedded-sol.com>
Cc: linuxppc-dev@ozlabs.org, Sean MacLennan <smaclennan@pikatech.com>
Subject: Re: Long boot delay on 460EX with 2.6.28-rc8
Date: Fri, 19 Dec 2008 23:23:58 +0200	[thread overview]
Message-ID: <494C10EE.1040305@embedded-sol.com> (raw)
In-Reply-To: <200812190856.19482.sr@denx.de>

Stefan Roese wrote:
> On Friday 19 December 2008, Felix Radensky wrote:
>   
>> Thanks a lot to everyone who replied. I've managed to identify the cause
>> of the delay. The board is equipped with 256 MiB Samsung NAND flash.
>> Since NAND support is a must for this platform, I've intergated the ndfc
>> driver recently posted by Sean McLennan. With this driver enabled the delay
>> is present, without it messages appear on the console immediately.
>>
>> Is this an expected behavior - detection of 256 MiB NAND flash
>> takes around 20 seconds. The ndfc driver works fine after boot.
>>     
>
> No, 20 seconds is definitely too long. Something must be wrong with the ndfc 
> driver or the NAND dts entries.
>
> Best regards,
> Stefan
>   
Hi, Sean

Do you have any ideas what can cause such delay ?

Thanks.

Felix.

  parent reply	other threads:[~2008-12-19 22:02 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 [this message]
2008-12-20  5:37         ` Sean MacLennan
2008-12-20  6:51           ` Felix Radensky
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=494C10EE.1040305@embedded-sol.com \
    --to=felix@embedded-sol.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=smaclennan@pikatech.com \
    /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;
as well as URLs for NNTP newsgroup(s).