linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 24 Dec 2008 13:40:12 -0800 (PST)	[thread overview]
Message-ID: <21156958.post@talk.nabble.com> (raw)
In-Reply-To: <c384c5ea0812221422g513d2545m434d2349f32974e4@mail.gmail.com>




Leon Woestenberg-3 wrote:
> 
> Felix,
> 
> On Sat, Dec 20, 2008 at 7:51 AM, Felix Radensky <felix@embedded-sol.com>
> wrote:
>>
>> 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.
>>
> Could you share the error?* (I'm sure I can easily exceed your level
> of stupidity)
> 
> It helps people who are curiously following the thread (either now or
> in two years time, hi there!) learn if it matches their problem.
> 
> 
> Regards,
> -- 
> Leon
> 
> * unless of course, it was really really really stupid in the first
> place and will cost you your daytime job. Then you are excused.
> 
> 

Well, I was simply using the wrong kernel for testing :) I did all work
on 2.6.26, and backported ndfc driver to it. At this stage of the project
it was too risky to use 2.6.28. But I did the minimal porting work, to see
how 2.8.28 behaves on this hardware, and I thought that I saw this long
delay on 2.6.28 as well as on 2.6.26. I was wrong. The reason for long
delay on 2.6.26 is nand ecc code, which was since completely rewritten.
After I've copied  new drivers/mtd/nand/nand_ecc,c to 2.6.26,  the delay
disappeared.

Felix.
-- 
View this message in context: http://www.nabble.com/Long-boot-delay-on-460EX-with-2.6.28-rc8-tp21070179p21156958.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.

  reply	other threads:[~2008-12-24 21:40 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
2008-12-22 22:22             ` Leon Woestenberg
2008-12-24 21:40               ` Felix Radensky [this message]
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=21156958.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 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).