From: Segher Boessenkool <segher@kernel.crashing.org>
To: michael@ellerman.id.au
Cc: Scott Wood <scottwood@freescale.com>,
linux-ppc list <linuxppc-dev@ozlabs.org>,
Andre Schwarz <andre.schwarz@matrix-vision.de>
Subject: Re: Question on MPC83xx interrupts
Date: Wed, 23 Apr 2008 18:00:26 +0200 [thread overview]
Message-ID: <49d9febd1f7b8022b6c418b592af2e33@kernel.crashing.org> (raw)
In-Reply-To: <1208905031.6947.0.camel@concordia>
> You can see the mapping between virq and hwirq numbers by turning on
> CONFIG_VIRQ_DEBUG and looking in /sys/kernel/debug/powerpc/virq_mapping
> (after mounting debugfs).
Ooh, nice! Are there plans to move this into some "real" sysfs
nodes?
Segher
prev parent reply other threads:[~2008-04-23 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 16:58 Question on MPC83xx interrupts Andre Schwarz
2008-04-22 17:23 ` Scott Wood
2008-04-22 17:36 ` Andre Schwarz
2008-04-22 17:42 ` Scott Wood
2008-04-22 18:51 ` Andre Schwarz
2008-04-22 18:52 ` Scott Wood
2008-04-22 22:57 ` Michael Ellerman
2008-04-23 7:54 ` André Schwarz
2008-04-23 16:00 ` Segher Boessenkool [this message]
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=49d9febd1f7b8022b6c418b592af2e33@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=andre.schwarz@matrix-vision.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=scottwood@freescale.com \
/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).