linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: ashish anand <ashisha@india.infogain.com>
To: "Prasad, Siva" <Siva.Prasad@smartm.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: EPIC <=> OpenPIC
Date: Thu, 04 Oct 2001 05:17:33 +0530	[thread overview]
Message-ID: <3BBBA395.3B812898@india.infogain.com> (raw)
In-Reply-To: 35C119252057D511BB9F0003476BF8A208E5DB@freexc01.smartm.com


Yah..it is already available.
Epic has been ported for MPC 107 and MPC 106 as well.
for mpc 106 can refer montavista port .
I assume we have for mpc107 and 750 board.
I will find that and would give you for refrence.
you can't use directly openpic structure as there is small deviation.
try to adjust your openpic structure as per epic manual.
set appropiately the triggering and polarity mode for irq lines
from winbond bridge and for shared pci slots.
refer the epic chapter and eumbbar chapter (for epic base)
in MPC 107 manual for correct programming

> Is there code written or ported to EPIC (Embedded programmable interrupt
> controller - MPC 107)?.
>
> EPIC is adopted from OpenPIC.
>
> Our PPC 750 based board uses MPC107 as PCI bridge, and direct interrupts.
> Since I can't use OpenPIC directly, it would be great if some one can share
> the code for EPIC.
>
> If it is already available some place... I would appreciate the pointer.

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

  parent reply	other threads:[~2001-10-03 23:47 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
2001-10-03 23:47 ` ashish anand [this message]
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=3BBBA395.3B812898@india.infogain.com \
    --to=ashisha@india.infogain.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).