linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Sébastien Chrétien" <sebastien.chretien.enseirb@gmail.com>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [machdep_calls] IRQ
Date: Fri, 22 Aug 2008 11:48:56 +0200	[thread overview]
Message-ID: <319b0ac50808220248x3e8b7db3s46b88b328aba9c0a@mail.gmail.com> (raw)
In-Reply-To: <1219382445.7861.60.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]

Ok thank you, I will begin to implement the irq functions

2008/8/22, Michael Ellerman <michael@ellerman.id.au>:
>
> On Thu, 2008-08-21 at 10:23 +0200, Sébastien Chrétien wrote:
> > Exactly, I mean ppc_md.init_IRQ().
>
> > Ok. What have I to setup in this function ? I set the mask and other
> > registers. Is it right ?  How do I chose the mask ?
>
>
> It totally depends on your platform, I really can't tell you. You can
> look at similar platform code if there is some, otherwise the reference
> manual for your hardware or similar should have what you need.
>
>
> > At the end of this funtion, IRQ are disable. Is that right ? So who
> > does enable IRQs ?
>
>
> Yes, irqs get enabled a bit later in start_kernel().
>
>
> cheers
>
> --
> Michael Ellerman
> OzLabs, IBM Australia Development Lab
>
> wwweb: http://michael.ellerman.id.au
> phone: +61 2 6212 1183 (tie line 70 21183)
>
> We do not inherit the earth from our ancestors,
> we borrow it from our children. - S.M.A.R.T Person
>
>

[-- Attachment #2: Type: text/html, Size: 1391 bytes --]

      reply	other threads:[~2008-08-22  9:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21  7:13 [machdep_calls] IRQ Sébastien Chrétien
2008-08-21  8:02 ` Michael Ellerman
2008-08-21  8:23   ` Sébastien Chrétien
2008-08-22  5:20     ` Michael Ellerman
2008-08-22  9:48       ` Sébastien Chrétien [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=319b0ac50808220248x3e8b7db3s46b88b328aba9c0a@mail.gmail.com \
    --to=sebastien.chretien.enseirb@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    /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).