From: Eugene Surovegin <ebs@ebshome.net>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Wall clock accuracy
Date: Tue, 9 Aug 2005 11:56:49 -0700 [thread overview]
Message-ID: <20050809185648.GB30956@gate.ebshome.net> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B85941C@ismail.innsys.innovsys.com>
On Tue, Aug 09, 2005 at 01:52:33PM -0500, Rune Torgersen wrote:
>
>
> > -----Original Message-----
> > From: Eugene Surovegin [mailto:ebs@ebshome.net]
> > Sent: Tuesday, August 09, 2005 13:35
> > To: Rune Torgersen
> > Cc: linuxppc-embedded@ozlabs.org
> > Subject: Re: Wall clock accuracy
> >
> > On Tue, Aug 09, 2005 at 01:21:09PM -0500, Rune Torgersen wrote:
> > >
> > > A proper fix would be for platfrom code to have a way to
> > set time_nsec
> > > instead of having it set by a constant.
> >
> > Or configure CLOCK_TICK_RATE in board/CPU specific fashion, e.g. like
> > ARM does.
>
> Then it would have to be a constant,
Why?
> and it would be much better to just
> use the clockrate given to the kernel than have to hardcode it into the
> kernel.
Nothing prevents you from defining this macro as a function call for
example. If this is needed for your CPU/board port. Probably common
case will be a constant, though.
--
Eugene
next prev parent reply other threads:[~2005-08-09 18:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 18:52 Wall clock accuracy Rune Torgersen
2005-08-09 18:56 ` Eugene Surovegin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-09 19:11 Rune Torgersen
2005-08-09 18:21 Rune Torgersen
2005-08-09 18:34 ` Eugene Surovegin
2005-08-09 17:04 Rune Torgersen
2005-08-09 17:20 ` Eugene Surovegin
2005-08-09 16:57 Rune Torgersen
2005-08-09 16:59 ` Eugene Surovegin
2005-08-09 17:02 ` Eugene Surovegin
2005-08-09 15:23 Rune Torgersen
2005-08-09 16:41 ` Eugene Surovegin
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=20050809185648.GB30956@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=runet@innovsys.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).