linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Allen Curtis" <acurtis@onz.com>
To: "Gabriel Paubert" <paubert@iram.es>,
	"Jean-Denis Boyer" <jdboyer@mediatrix.com>
Cc: "Troy Benjegerdes" <hozer@drgw.net>,
	"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
	<linuxppc-embedded@lists.linuxppc.org>,
	"Paul Mackerras" <paulus@samba.org>
Subject: RE: Bogomips and loops_per_jiffy
Date: Fri, 10 May 2002 07:39:25 -0700	[thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFMEMKDGAA.acurtis@onz.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0205101627540.23021-100000@gra-lx1.iram.es>


I thought that this discussion was regarding BogoMips. If so, then you do
not need the RTC, use the 1 second timer. If your concern is returning and
maintaining TOD, then that is RTC.

Right?

> >
> > > I'm afraid that this is a symptom of lost timekeeping
> > > after reading the RTC and that you simply cure the symptom.
> >
> > My platform uses an 8260 processor, and AFAIK there is no RTC.
> The function
> > __USE_RTC() returns 0.
>
> OOPs, sorry for the confusion, by RTC I meant the chip with a battery
> which keeps time across reboots and that we read to initially set the
> system time.
>


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

  reply	other threads:[~2002-05-10 14:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-10 14:10 Bogomips and loops_per_jiffy Jean-Denis Boyer
2002-05-10 14:23 ` Allen Curtis
2002-05-10 15:06   ` Jerry Van Baren
2002-05-10 14:27 ` Gabriel Paubert
2002-05-10 14:29 ` Gabriel Paubert
2002-05-10 14:39   ` Allen Curtis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-10 14:54 Jean-Denis Boyer
2002-05-10 20:15 ` Gabriel Paubert
2002-05-10 21:16   ` Benjamin Herrenschmidt
2002-05-11  2:08     ` Gabriel Paubert
2002-05-10 14:46 Jean-Denis Boyer
2002-05-10 14:15 Petersen, David (MED, GEMS-IT)
2002-05-08 18:30 Jean-Denis Boyer
2002-05-08 16:53 Jean-Denis Boyer
2002-05-08 17:43 ` Benjamin Herrenschmidt
2002-05-08 22:13   ` Gabriel Paubert
2002-05-09 15:08     ` Troy Benjegerdes
2002-05-09 16:16       ` Gabriel Paubert
2002-05-08 18:06 ` Troy Benjegerdes
2002-05-06 21:17 Jean-Denis Boyer
2002-05-08  0:48 ` Troy Benjegerdes
2002-04-22 15:57 Jean-Denis Boyer
2002-04-19 11:57 Jim Thompson

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=NCBBIINEHIPFGJPLBEIFMEMKDGAA.acurtis@onz.com \
    --to=acurtis@onz.com \
    --cc=benh@kernel.crashing.org \
    --cc=hozer@drgw.net \
    --cc=jdboyer@mediatrix.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=paubert@iram.es \
    --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).