From: Kumar Gala <galak@kernel.crashing.org>
To: tglx@linutronix.de, mingo@elte.hu
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
linux-kernel Kernel <linux-kernel@vger.kernel.org>,
Peters Ted <Ted.Peters@freescale.com>
Subject: sharing an interrupt between a cascaded/chained pic and another device
Date: Tue, 27 Jan 2009 08:57:54 -0600 [thread overview]
Message-ID: <0D5BDAF5-E5FD-42FC-977C-B83664FE4C78@kernel.crashing.org> (raw)
Thomas, Ingo,
Do we have any support in the kernel today to deal with a IRQ on the
root PIC being used for both a chained PIC and shared with another HW
device. We have a board that guys went and did it and as I look at
the kernel code it doesn't seem like this crazy situation is currently
supported.
- k
reply other threads:[~2009-01-27 14:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0D5BDAF5-E5FD-42FC-977C-B83664FE4C78@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=Ted.Peters@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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).