linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: "Prasad, Siva" <Siva.Prasad@smartm.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: EPIC <=> OpenPIC
Date: Wed, 03 Oct 2001 14:16:46 -0700	[thread overview]
Message-ID: <3BBB803E.63B9239@mvista.com> (raw)
In-Reply-To: 3BBB7DB6.7BD2C503@mvista.com


"Mark A. Greer" wrote:

> "Prasad, Siva" wrote:
>
> > Hi,
> >
> > Is there code written or ported to EPIC (Embedded programmable interrupt
> > controller - MPC 107)?.
>
> Yes, mpc10x_common.c.  Examples of its use are in the code.

I'll add a little more.  You can use the openpic code with the EPIC if you're
careful.  Look at sandpoint_setup.c for an example.  Your EPIC IRQs *must*
start at 16 and resist the urge to set the offset param to anything but 0.

Mark


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-10-03 21:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03 20:28 EPIC <=> OpenPIC Prasad, Siva
2001-10-03 21:05 ` Mark A. Greer
2001-10-03 21:16   ` Mark A. Greer [this message]
2001-10-03 23:47 ` ashish anand
2001-10-04 16:46   ` Dan Malek

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=3BBB803E.63B9239@mvista.com \
    --to=mgreer@mvista.com \
    --cc=Siva.Prasad@smartm.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).