From: Felix Radensky <felix@embedded-sol.com>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: GPIO interrupt on AMCC 460EX
Date: Fri, 29 Aug 2008 00:47:48 +0300 [thread overview]
Message-ID: <48B71D04.4080805@embedded-sol.com> (raw)
In-Reply-To: <200808281720.13138.sr@denx.de>
Hi, Stefan
Stefan Roese wrote:
> arch/powerpc now used virtual interrupts. You need to include this hardware
> interrupt number into your device-tree (create a new node for your CPLD) and
> extract the virtual irq number from there by calling irq_of_parse_and_map().
>
>
That works fine, thank you.
Felix.
next prev parent reply other threads:[~2008-08-28 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 14:11 GPIO interrupt on AMCC 460EX Felix Radensky
2008-08-28 15:20 ` Stefan Roese
2008-08-28 21:47 ` Felix Radensky [this message]
2008-08-29 15:31 ` MPC8568MDS RAMDISK Problem SETTE AGOSTINO - technolabs
2008-08-29 18:03 ` Bhupender Saharan
2008-08-29 21:45 ` Anatolij Gustschin
2008-09-01 9:02 ` SETTE AGOSTINO - technolabs
2008-09-02 10:10 ` Anatolij Gustschin
2008-09-02 13:18 ` SETTE AGOSTINO - technolabs
2008-09-02 21:27 ` Anatolij Gustschin
2008-09-03 9:30 ` SETTE AGOSTINO - technolabs
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=48B71D04.4080805@embedded-sol.com \
--to=felix@embedded-sol.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sr@denx.de \
/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).