From: "Grant Likely" <grant.likely@secretlab.ca>
To: Mirek23 <miroslaw.dach@psi.ch>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Interrupts on xilinx ml403
Date: Fri, 20 Jul 2007 09:12:04 -0600 [thread overview]
Message-ID: <fa686aa40707200812w3427c12dwd10b08c8433af2fc@mail.gmail.com> (raw)
In-Reply-To: <11708607.post@talk.nabble.com>
On 7/20/07, Mirek23 <miroslaw.dach@psi.ch> wrote:
> Does it mean that DIP Switches do not use INTC interrupt controller?
> How to handle the DIP Switches interrupt?
> Does the Interrupt handler routine have to acknowledge the interrupt from
> Dip Switches?
It probably means that the GPIO irq out line is not hooked up to your
INTC in the system.mhs file.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-07-20 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 13:52 Interrupts on xilinx ml403 Mirek23
2007-07-20 15:12 ` Grant Likely [this message]
2007-07-24 15:19 ` Mirek23
2007-07-24 7:31 ` Misbah khan
2007-07-24 15:22 ` Mirek23
2007-07-25 4:44 ` Misbah khan
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=fa686aa40707200812w3427c12dwd10b08c8433af2fc@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.org \
--cc=miroslaw.dach@psi.ch \
/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).