public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] itc sync & clock_*
Date: Mon, 29 Oct 2001 18:10:44 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805407@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805400@msgid-missing>

On Mon, 29 Oct 2001, David Mosberger wrote:

> The first thing to do is to get this into the firmware.  Linux needs a
> way to detect when the ITCs are not driven off the same clock (i.e.,
> when there is a chance for the ITCs to drift).  There also needs to be
> a way for detecting when the clock frequencies are different, but I
> believe the info provided by PAL/SAL is sufficient (my only worry are
> rounding errors...).

Ok, we'll work on getting this pushed back, so at least the kernel can
figure out what to do.  Regarding glibc though: we really don't want to
have a different version just for our systems, so I'd like to come up with
a generic solution.  Maybe an ia64 specific clock driver that glibc could
map in to read synchronized clock info?  Is there a platform independent
way of doing this?  I'll poke around glibc some more to see if any of the
other arches deal with tis problem, but I'm sure there are people that are
already familiar with these sorts of issues that might be able to help
out.  Anyone?

Thanks a lot,
Jesse



  parent reply	other threads:[~2001-10-29 18:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-26 17:09 [Linux-ia64] itc sync & clock_* Jesse Barnes
2001-10-29 15:54 ` David Mosberger
2001-10-29 18:10 ` Jesse Barnes [this message]
2001-10-29 18:28 ` David Mosberger
2001-10-29 18:33 ` Jack Steiner
2001-10-29 18:52 ` David Mosberger
2001-10-29 21:27 ` David Mosberger
2001-10-31 19:41 ` Jesse Barnes
2001-11-06  1:03 ` David Mosberger
2001-11-06  1:03 ` Jesse Barnes
2001-11-09  1:31 ` Mallick, Asit K
2001-11-09  2:06 ` David Mosberger

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=marc-linux-ia64-105590698805407@msgid-missing \
    --to=jbarnes@sgi.com \
    --cc=linux-ia64@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