linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: sumedh tirodkar <sumedhtirodkar@gmail.com>
To: Matt Gessner <mgessner@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Problem with decrementer interrupt
Date: Mon, 23 Feb 2009 22:34:25 +0530	[thread overview]
Message-ID: <d2b9ccd90902230904h148827fey293aebd2962c892a@mail.gmail.com> (raw)
In-Reply-To: <85a5c2010902230648m72b63eeds70b4e7a5ec4d8c51@mail.gmail.com>

Alright...I am trying to develop a system of my own..
Consider that i am not using any linux kernel...I m writing some
program right from scratch.........
The major steps that i have taken are...

1. Started with a assembly file...
2. Have relocated the interrupt handlers to there respective
positions...The interrupt handlers are written in assembly language...
3. Initialised Decrementer register to get an interrupt after some interval...
4. Jump to some function using

    bl <function_name_main>

    function_name_main which will have a infinite while loop..
This works fine i.e. the interrupts(decrementer interrupt to be more
specific) work fine...I have initialised serial port to get the
output...

Now, the problem that i am facing....

If in interrupt handler of the decrementer, i make a call to some C
function in some other C file...using the follwing statement...

Dec_handler:  /* I have relocated this to interrupt vector address of
decrementer interrupt*/
     /*code to print using serial port*/
     bla <function_name_handler> /*code to call some function in C file*/
     /*code to print using serial port---but i m never able to see this output*/
     RFI

This starts creating a problem...somehow we dont return to this code
after the end of the function_name_handler...
Consider the following code for the function_name_handler:
void function_name_handler(void)
{
   /*Some action*/
}

So, if its possible for anyone to help me with this...please reply...

Regards,
Sumedh


On Mon, Feb 23, 2009 at 8:18 PM, Matt Gessner <mgessner@gmail.com> wrote:
>
>
> On Mon, Feb 23, 2009 at 8:03 AM, sumedh tirodkar <sumedhtirodkar@gmail.com>
> wrote:
>>
>> I am using PowerPC 7447A...I am trying to port SA-RTL on PowerPC...
>
> What I said earlier was: You need to tell people what cpu you're using, what
> linux kernel, etc etc etc.
>
> Fine, we know the CPU.  What kernel are you using?  Is it ancient?
>
> I doubt the information below is going to be useful...
>
>>
>> I am using
>>
>> bla <function_name>
>>
>> from the assembly code to call the function in C file...This i am
>> doing from interrupt handler of the decrementer...
>> If any more details are required, please let me know...
>
>

  reply	other threads:[~2009-02-23 17:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23  7:54 Problem with decrementer interrupt sumedh tirodkar
     [not found] ` <85a5c2010902230439n1096196dr519462513bc3910d@mail.gmail.com>
2009-02-23 13:03   ` sumedh tirodkar
2009-02-23 14:48     ` Matt Gessner
2009-02-23 17:04       ` sumedh tirodkar [this message]
2009-02-23 17:33         ` sjoyeau
2009-02-23 18:02           ` sumedh tirodkar
2009-02-24  7:54             ` sjoyeau
2009-02-24 11:53               ` sumedh tirodkar
2009-02-24 17:32                 ` sumedh tirodkar

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=d2b9ccd90902230904h148827fey293aebd2962c892a@mail.gmail.com \
    --to=sumedhtirodkar@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mgessner@gmail.com \
    /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).