From: david.hagood@gmail.com
To: "Scott Wood" <scottwood@freescale.com>
Cc: "tiejun.chen" <tiejun.chen@windriver.com>,
david.hagood@gmail.com,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Questions on interrupt vector assignment on MPC8641D
Date: Wed, 13 Oct 2010 12:08:16 -0500 [thread overview]
Message-ID: <1c6d107b01e69a0466fd4e4eb4aaf26e.squirrel@localhost> (raw)
In-Reply-To: <20101013102815.2959fcb6@udp111988uds.am.freescale.net>
Do you have any suggestions on where to find out what parameters I should
pass to mpic_assign_isu() to map the interrupts? It's another of those
charmingly undocumented functions, even in the most recent git pull of the
mainline kernel.
next prev parent reply other threads:[~2010-10-13 17:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 14:12 Questions on interrupt vector assignment on MPC8641D david.hagood
2010-09-21 21:37 ` Anderson, Trevor
2010-09-21 22:07 ` Scott Wood
2010-09-22 0:36 ` Chen, Tiejun
2010-10-07 20:12 ` david.hagood
2010-10-07 20:26 ` Scott Wood
2010-10-07 21:01 ` david.hagood
2010-10-09 15:52 ` david.hagood
2010-10-11 9:51 ` tiejun.chen
2010-10-11 11:30 ` David Hagood
2010-10-11 14:44 ` david.hagood
2010-10-13 1:10 ` Michael Ellerman
2010-10-11 15:51 ` Scott Wood
2010-10-12 1:39 ` tiejun.chen
2010-10-11 15:50 ` Scott Wood
2010-10-11 17:02 ` david.hagood
2010-10-11 17:30 ` Scott Wood
2010-10-12 3:11 ` tiejun.chen
2010-10-09 17:03 ` david.hagood
2010-10-11 9:55 ` tiejun.chen
2010-10-11 17:17 ` Scott Wood
2010-10-12 20:55 ` david.hagood
2010-10-12 21:21 ` Scott Wood
2010-10-13 1:17 ` tiejun.chen
2010-10-13 15:28 ` Scott Wood
2010-10-13 17:08 ` david.hagood [this message]
2010-10-13 19:56 ` Scott Wood
2010-10-13 21:16 ` david.hagood
2010-10-14 1:39 ` tiejun.chen
2010-10-14 3:27 ` tiejun.chen
2010-10-14 15:51 ` Scott Wood
2010-10-14 16:22 ` david.hagood
2010-10-14 16:32 ` Scott Wood
2010-10-14 17:20 ` david.hagood
2010-10-14 17:50 ` Scott Wood
2010-10-14 18:44 ` david.hagood
2010-10-15 1:28 ` tiejun.chen
2010-10-12 3:00 ` tiejun.chen
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=1c6d107b01e69a0466fd4e4eb4aaf26e.squirrel@localhost \
--to=david.hagood@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
--cc=tiejun.chen@windriver.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).