linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Ran Shalit <ranshalit@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: use interrupt without clearing ?
Date: Mon, 12 Oct 2015 13:53:55 +1100	[thread overview]
Message-ID: <1444618435.7194.2.camel@ellerman.id.au> (raw)
In-Reply-To: <CAJ2oMhLMi2PZvQoFU7JuYSsJM_UbuTsOaRfQKxqsJQq=KDG9vQ@mail.gmail.com>

On Sun, 2015-10-11 at 15:13 +0300, Ran Shalit wrote:
> Hello,
> 
> Is it possible to register an interrupt (in linux), without using the
> automatic clear of interrupt.
> I need this just for testing.

Hi Ran,

You need to give us much more info than that before anyone will be able to
answer your question. Linux runs on lots of different powerpc machines, so
without knowing what hardware you're talking about it's impossible to
answer.

cheers

  reply	other threads:[~2015-10-12  2:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-11 12:13 use interrupt without clearing ? Ran Shalit
2015-10-12  2:53 ` Michael Ellerman [this message]
2015-10-12 21:14   ` Ran Shalit

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=1444618435.7194.2.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=ranshalit@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).