From: "H. Peter Anvin" <hpa@zytor.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Marc Perkel <mperkel@yahoo.com>, Chris Snook <csnook@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: AMD Quad Core clock problem?
Date: Mon, 14 Apr 2008 19:40:43 -0700 [thread overview]
Message-ID: <480415AB.2070308@zytor.com> (raw)
In-Reply-To: <m3lk3fj3gd.fsf@maximus.localdomain>
Krzysztof Halasa wrote:
> "H. Peter Anvin" <hpa@zytor.com> writes:
>
>> It shouldn't really matter, since "below" produces a similar spectrum
>> at a slightly lower frequency.
>
> Sure for CPU/TSC and similar clocks but in case of well-known (not
> calibrated) frequency it could be a problem. Not sure if there are
> such cases.
There is - the 14.31818 MHz clock, but as previously noted it is
generally not spread. If *that* clock is spread I would expect problems.
-hpa
next prev parent reply other threads:[~2008-04-15 2:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 18:27 AMD Quad Core clock problem? Marc Perkel
2008-04-11 18:35 ` H. Willstrand
2008-04-11 18:38 ` Chris Snook
2008-04-11 20:28 ` Marc Perkel
2008-04-11 21:11 ` Chris Snook
2008-04-11 21:36 ` Marc Perkel
2008-04-11 21:38 ` Lennart Sorensen
2008-04-13 19:35 ` H. Peter Anvin
2008-04-14 15:12 ` Lennart Sorensen
2008-04-14 16:23 ` H. Peter Anvin
2008-04-14 16:29 ` Lennart Sorensen
2008-04-15 1:11 ` Krzysztof Halasa
2008-04-15 1:24 ` H. Peter Anvin
2008-04-15 1:45 ` Krzysztof Halasa
2008-04-15 2:40 ` H. Peter Anvin [this message]
2008-04-11 21:46 ` Krzysztof Halasa
2008-04-11 22:09 ` Marc Perkel
2008-04-13 8:19 ` Bart Van Assche
2008-04-12 1:04 ` Marc Perkel
2008-04-14 19:16 ` Chris Snook
2008-04-14 20:46 ` Marc Perkel
2008-04-15 6:11 ` Bart Van Assche
2008-04-16 21:44 ` Marc Perkel
2008-04-17 6:17 ` Bart Van Assche
2008-04-17 18:03 ` Marc Perkel
2008-04-18 11:56 ` Bart Van Assche
2008-06-17 21:09 ` Marc Perkel
2008-04-14 13:40 ` Marc Perkel
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=480415AB.2070308@zytor.com \
--to=hpa@zytor.com \
--cc=csnook@redhat.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=mperkel@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.