All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark Chambers" <markc@mail.com>
To: "Bret Indrelee" <Bret.Indrelee@qlogic.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Hardware interrupts routines
Date: Wed, 16 Jun 2004 10:24:58 -0400	[thread overview]
Message-ID: <009501c453ad$b6be50f0$0301a8c0@chuck2> (raw)
In-Reply-To: Pine.LNX.4.44.0406160847040.10492-100000@spider.ancor.com


But isn't he going to have to write a device driver in order to call
request_irq()?  You can't just call request_irq() from an application, can
you?  If not, is there any way to grab an interrupt other than writing a
device driver?

Mark Chambers

----- Original Message -----
From: "Bret Indrelee" <Bret.Indrelee@qlogic.com>
To: "Garcia Jérémie" <GARCIAJ@3il.fr>
> On Wed, 16 Jun 2004, [Windows-1252] Garcia Jérémie wrote:
> [ nnip ]
> > The only hardware interrupts routine I found through my investigations
> > is the request_irq(...). But the problem is that request_irq do not
> > allow me to pass an argument to the handler... So is there a routine
> > that allows it or is there a way to adapt the request_irq() to my case.
>
> The last parameter of request_irq() gets passed as the second parameter
> to the interrupt routine when it is called.
>
> -Bret
>
> --
> Bret Indrelee                 QLogic Corporation
> Bret.Indrelee@qlogic.com      6321 Bury Drive, St 13, Eden Prairie, MN
55346
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-06-16 14:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 14:28 Hardware interrupts routines Garcia Jérémie
2004-06-16 13:46 ` Jeff Angielski
2004-06-16 13:49 ` Bret Indrelee
2004-06-16 14:24   ` Mark Chambers [this message]
2004-06-16 14:52     ` Bret Indrelee
2004-06-16 14:24 ` Jaap-Jan Boor
2004-06-16 14:59 ` Jean-Christophe Dubois

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='009501c453ad$b6be50f0$0301a8c0@chuck2' \
    --to=markc@mail.com \
    --cc=Bret.Indrelee@qlogic.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.