All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: "Bart Van Assche" <bart.vanassche@gmail.com>
Cc: "linuxppc-dev@ozlabs.org ML" <linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: + ocotea-board-ntpd-complains-that-the-frequency-error-exceeds-the-tolerance.patch added to -mm tree
Date: Fri, 16 Mar 2007 15:40:42 +0100	[thread overview]
Message-ID: <200703161540.44334.sr@denx.de> (raw)
In-Reply-To: <e2e108260703160734o24550c4dp7bef0d7f33bcdcc5@mail.gmail.com>

On Friday 16 March 2007 15:34, Bart Van Assche wrote:
> >   I asked Stefan & Josh to look at this and Stefan believes its a
> > 33.33Mhz clock.  So should this really be 33330000?
>
> I have measured the clock frequency on the two Ocotea boards I have on
> my desk, and both have a clock crystal of 33.3 MHz, not 33.33 MHz.
> What I don't know is whether the same clock crystal is mounted on all
> Ocotea boards.

Hmmm. From what I could read from the schematics, it should be 33.33MHz. But 
here is always a gray zone. I'll ask AMCC, what is equipped right now.

Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk
Office:  Kirchenstr. 5,       D-82194 Groebenzell,            Germany
=====================================================================

  reply	other threads:[~2007-03-16 14:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16 10:52 + ocotea-board-ntpd-complains-that-the-frequency-error-exceeds-the-tolerance.patch added to -mm tree akpm
2007-03-16 14:14 ` Kumar Gala
2007-03-16 14:34   ` Bart Van Assche
2007-03-16 14:40     ` Stefan Roese [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-03-16  2:55 akpm

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=200703161540.44334.sr@denx.de \
    --to=sr@denx.de \
    --cc=akpm@linux-foundation.org \
    --cc=bart.vanassche@gmail.com \
    --cc=linuxppc-dev@ozlabs.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 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.