From: Cort Dougan <cort@fsmlabs.com>
To: Tim Moloney <moloney@mrsl.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Interrupt handling via OpenPIC
Date: Wed, 11 Apr 2001 13:56:10 -0600 [thread overview]
Message-ID: <20010411135610.A1276@ftsoj.fsmlabs.com> (raw)
In-Reply-To: <00bf01c0c2ac$54b6e650$6c125acf@mrsl.com>; from moloney@mrsl.com on Wed, Apr 11, 2001 at 01:24:57PM -0400
You'll have to talk to synergy about that one. I'm not sure how the PMC
interrupts are routed on that board (I've never tested a PMC card on it).
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-11 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-11 17:24 Interrupt handling via OpenPIC Tim Moloney
2001-04-11 19:56 ` Cort Dougan [this message]
2001-04-11 23:48 ` Tim Moloney
-- strict thread matches above, loose matches on Subject: below --
2001-04-11 17:00 Tim Moloney
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=20010411135610.A1276@ftsoj.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=moloney@mrsl.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).