From: Paul Mackerras <paulus@samba.org>
To: Samuel Rydh <samuel@ibrium.se>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] 2.6 timebase synchronization
Date: Sun, 10 Aug 2003 12:09:45 +1000 [thread overview]
Message-ID: <16181.43369.219750.258015@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20030809011305.GA12030@ibrium.se>
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?
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-08-10 2:09 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 [this message]
2003-08-10 9:39 ` Benjamin Herrenschmidt
2003-08-10 16:22 ` Mark Guertin
2003-08-10 21:29 ` Samuel Rydh
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=16181.43369.219750.258015@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=samuel@ibrium.se \
/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).