From: tike64 <tike64@yahoo.com>
To: junjiec@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: realtime-preempt and arm
Date: Fri, 1 Dec 2006 01:07:04 -0800 (PST) [thread overview]
Message-ID: <304269.38734.qm@web59207.mail.re1.yahoo.com> (raw)
In-Reply-To: <456eff57.0e1fcf5c.617c.44a6@mx.google.com>
> Hi,
>
> Without the support of High Resolution Timer
> supported, the timer resolution wouldn't change.
Ok, I understand that. I was not expecting more
resolution. I expected only that I would get more
precise 10ms delays. What confuses me is that the
delays roughly doubled.
> With high-resolution-timer supported, our
> arm926-based board could get resolution like
40~50us.
> There are codes you can reference ,may be you should
> just try to implement it.
It is good to know that the problem is not the arm
architecture itself. Thanks to you for that.
The problem must be in the lh7a40x specific code or my
configuration. I am not yet convinced enough that high
resolution timer implementation would solve the
problem. I don't need timing resolution finer than
10ms providing that FB doesn't blow it up to 60ms.
Could you or someone please give a hint where to look
next or give an explanation why the lack of high
resolution timer would behave like that.
--
tike
____________________________________________________________________________________
Cheap talk?
Check out Yahoo! Messenger's low PC-to-Phone call rates.
http://voice.yahoo.com
next prev parent reply other threads:[~2006-12-01 9:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 8:57 tike64
2006-11-30 15:56 ` junjiec
2006-12-01 9:07 ` tike64 [this message]
2006-12-13 18:36 ` Steven Rostedt
2006-12-14 7:21 ` tike64
2006-12-14 10:00 ` Ingo Molnar
2006-12-14 10:26 ` tike64
2006-12-14 12:52 ` Steven Rostedt
2006-12-14 14:23 ` tike64
2006-12-14 15:20 ` Steven Rostedt
2006-12-15 7:15 ` tike64
2006-12-15 9:58 ` Ingo Molnar
2006-12-15 13:00 ` Steven Rostedt
2006-12-16 0:14 Robert Crocombe
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=304269.38734.qm@web59207.mail.re1.yahoo.com \
--to=tike64@yahoo.com \
--cc=junjiec@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®