linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Rydh <samuel@ibrium.se>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] 2.6 timebase synchronization
Date: Sun, 10 Aug 2003 23:29:42 +0200	[thread overview]
Message-ID: <20030810212942.GB14877@ibrium.se> (raw)
In-Reply-To: <1060508348.13388.20.camel@gaston>


On Sun, Aug 10, 2003 at 11:39:08AM +0200, Benjamin Herrenschmidt wrote:
>
> On Sun, 2003-08-10 at 04:09, Paul Mackerras wrote:
> > Samuel Rydh writes:
> >
> > > Attached is an improved version of the patch.
> >
> > How many SMP machines are there where we don't know how to freeze/thaw
> > the timebase?  We know how to do that on the old powersurge powermacs,
> > on CHRP systems and on at least some of the recent core99 powermacs
> > (those that have a timebase-enable property on the cpu device nodes).
> > What machines are left?
>
> We know how to do it on some core99, though we don't actually do it
> yet ;) We use software sync on all core99 for now.

Btw, the freeze/thaw timebase setting that is done on psurge is lost
since the generic timebase calibration mechanism is still invoked
afterwards (and at that time, the timebases are ticking).

/Samuel


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2003-08-10 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-08  0:15 [PATCH] 2.6 timebase synchronization Samuel Rydh
2003-08-09  1:13 ` Samuel Rydh
2003-08-09  8:58   ` Benjamin Herrenschmidt
2003-08-09 11:48     ` Samuel Rydh
2003-08-10  2:09   ` Paul Mackerras
2003-08-10  9:39     ` Benjamin Herrenschmidt
2003-08-10 16:22       ` Mark Guertin
2003-08-10 21:29       ` Samuel Rydh [this message]

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=20030810212942.GB14877@ibrium.se \
    --to=samuel@ibrium.se \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@samba.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).