From: Daniel Laird <danieljlaird@hotmail.com>
To: linux-mips@linux-mips.org
Subject: Re: [PATCH][respin] pnx8550: fix system timer support
Date: Wed, 3 Jan 2007 05:37:45 -0800 (PST) [thread overview]
Message-ID: <8140851.post@talk.nabble.com> (raw)
In-Reply-To: <8127168.post@talk.nabble.com>
Daniel Laird wrote:
>
>
Thanks, thats the build problem removed, I now have a kernel that builds
properly! (issues 1 and 2 appear to be closed)
Only issue remaining is that I still have a long hang (10 seconds ish)
after this
Memory: 53540k/57344k available (2156k kernel code, 3744k reserved, 383k
data, 128k init, 0k highmem)
I am investigating but any help is appreciated...
Dan
I have been debugging this and the delay is all due to the calibrate_delay
function.
If I use a preset lpj all works fine (fast start up)
If I let it calculate it using the logic
while ((loops_per_jiffy <<= 1) != 0) {
/* wait for "start of" clock tick */
ticks = jiffies;
while (ticks == jiffies)
/* nothing */;
/* Go .. */
ticks = jiffies;
__delay(loops_per_jiffy);
ticks = jiffies - ticks;
if (ticks)
break;
}
Then I get the hang so it seems this is the culprit function, however as for
why this is happening I am still debugging
Cheers
Dan
--
View this message in context: http://www.nabble.com/-PATCH--respin--pnx8550%3A-fix-system-timer-support-tf2890537.html#a8140851
Sent from the linux-mips main mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-01-03 13:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 14:14 [PATCH][respin] pnx8550: fix system timer support Vitaly Wool
2006-12-28 16:16 ` Atsushi Nemoto
2006-12-28 16:20 ` Vitaly Wool
2007-01-02 14:05 ` Daniel Laird
2007-01-02 16:06 ` Atsushi Nemoto
2007-01-02 17:17 ` Daniel Laird
2007-01-03 13:37 ` Daniel Laird [this message]
2007-01-03 13:57 ` Atsushi Nemoto
2007-01-03 14:34 ` Daniel Laird
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=8140851.post@talk.nabble.com \
--to=danieljlaird@hotmail.com \
--cc=linux-mips@linux-mips.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.