From: Kent Borg <kentborg@borg.org>
To: bhupinder sahran <bhup_sah@yahoo.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Shared Interrupts Question (2.4)
Date: Thu, 8 May 2003 16:28:14 -0400 [thread overview]
Message-ID: <20030508162814.B18714@borg.org> (raw)
In-Reply-To: <20030508202012.37047.qmail@web41503.mail.yahoo.com>; from bhup_sah@yahoo.com on Thu, May 08, 2003 at 01:20:12PM -0700
On Thu, May 08, 2003 at 01:20:12PM -0700, bhupinder sahran wrote:
> SO in the do_irq routine u will have to read the
> interrupt controller registers & find out who has
> caused the interrupt & then invoke interrupt handler
> corressponding to the interrupt number.
Yes, but how do I enable the interrupt in the first place? (Disable
too.) I mean, I know how to set the bit, but where is the best place
to do so? In the case of a serial port, I figure I could turn it on
in startup() in serial.c. But then how do I know which of two
possible interrupts it is? I could do something hacky, like look at
the UART address and infer from there, but that looks nasty...
Thanks,
-kb, the Kent who, if has to muck with existing kernel files, wants to
do so in an acceptable way.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-08 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 20:08 Shared Interrupts Question (2.4) Kent Borg
2003-05-08 20:20 ` bhupinder sahran
2003-05-08 20:28 ` Kent Borg [this message]
2003-05-08 21:14 ` Dale Farnsworth
2003-05-09 17:34 ` Kent Borg
2003-05-10 2:00 ` Dale Farnsworth
-- strict thread matches above, loose matches on Subject: below --
2003-05-08 21:48 Kent Borg
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=20030508162814.B18714@borg.org \
--to=kentborg@borg.org \
--cc=bhup_sah@yahoo.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 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).