linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vineeth <vneethv@gmail.com>
To: linux-embedded@vger.kernel.org, linuxppc-embedded@ozlabs.org,
	linuxppc-dev@lists.ozlabs.org
Subject: Timer interrupt on Linux 3.0.3
Date: Fri, 16 Sep 2011 17:13:06 +0530	[thread overview]
Message-ID: <CAFbQSaD-c=QqSsq__VtBEcMCJabnBi4AP4KunDNV7u7xXAuaTw@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 626 bytes --]

Hi,

We are porting Linux on MPC7410 based board. As there was some issue with
the processor DECrementer and timebase registers, we were using an external
count down timer as our DECementer. We used timer_interrupt() function in
arch/powerpc/kernel/time.c as our interrupt handler. Things were working
fine.

lately we moved to Linux 3.0.3. What we found was even without a proper
timer, the kernel with initramfs worked (except the calls like sleep,delay
ofcourse); Is there any major difference in the scheduler ? or the way
context switch happens ? is it not depended on the timer interrupt or the
timer ??

Thanks
Vineeth

[-- Attachment #1.2: Type: text/html, Size: 660 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

             reply	other threads:[~2011-09-16 11:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-16 11:43 Vineeth [this message]
2011-09-16 17:03 ` Timer interrupt on Linux 3.0.3 Scott Wood
2011-09-21  6:56   ` Vineeth
2011-09-21 19:41     ` Scott Wood
2011-09-22  6:22       ` MohanReddy koppula
2011-09-26  9:11         ` Vineeth

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='CAFbQSaD-c=QqSsq__VtBEcMCJabnBi4AP4KunDNV7u7xXAuaTw@mail.gmail.com' \
    --to=vneethv@gmail.com \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).