From: rd.asha22@gmail.com (Asha R)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Problem in timer interrupt handler with Linux 2.6.27 version
Date: Mon, 4 Apr 2011 18:29:49 +0530 [thread overview]
Message-ID: <BANLkTinaZ9VciZqGEfxE2seYGsNuOz+yWg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=p-AQuiUYw2SuEOo19b6JgecW+Hw@mail.gmail.com>
Thanks for your response.
I am opting older version to use the Android cup cake version which is with
Linux 2.6.27.
On debugging more i have found that it is because clock related routines are
different in both versions.
Can someone help me to integrate, if done before?
Regards,
Asha
On Mon, Apr 4, 2011 at 12:00 PM, Mulyadi Santosa
<mulyadi.santosa@gmail.com>wrote:
> On Mon, Apr 4, 2011 at 13:25, Asha R <rd.asha22@gmail.com> wrote:
> > Hi All,
> >
> > I am working on Linux 2.6.27 version.
> > I am facing problem in timer interrupt.
> >
> > I get the timer interrupt but in the handler, evt->event_handler
> generates
> > prefetch abort.
> > The same code works with Linux 2.6.37 version.
>
> I dare to bet that if it was Greg KH that answered this first, you
> will get the famous reply "we don't support old kernel version"....
> and that's true...not that kernel folks abandon old kernel, it's just
> making life so difficult...
>
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110404/51bbb4d0/attachment.html
prev parent reply other threads:[~2011-04-04 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 6:25 Problem in timer interrupt handler with Linux 2.6.27 version Asha R
2011-04-04 6:30 ` Mulyadi Santosa
2011-04-04 12:59 ` Asha R [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=BANLkTinaZ9VciZqGEfxE2seYGsNuOz+yWg@mail.gmail.com \
--to=rd.asha22@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).