linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: "dibacco@inwind.it" <dibacco@inwind.it>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: system tick in PPC
Date: Sun, 12 Feb 2006 10:33:30 -0800	[thread overview]
Message-ID: <20060212183330.GB32060@gate.ebshome.net> (raw)
In-Reply-To: <IUL5ER$96FFE4CFF38D6FFE5A07D5798F74338C@libero.it>

On Sun, Feb 12, 2006 at 06:47:15PM +0100, dibacco@inwind.it wrote:
> Someone knows how the jiffies is incremented in PPC?
> Using PIT, Decrementer or what?

I think you should be looking at include/asm-powerpc/time.h, 
set_dec() & get_dec() functions. 

timer_interrupt() uses set_dec().

In short, usually PPC uses decrementer, but some sub-archs are special.

-- 
Eugene

      reply	other threads:[~2006-02-12 18:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 17:47 system tick in PPC dibacco
2006-02-12 18:33 ` Eugene Surovegin [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=20060212183330.GB32060@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=dibacco@inwind.it \
    --cc=linuxppc-embedded@ozlabs.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).