From: Dan Malek <dan@mvista.com>
To: James F Dougherty <jfd@GigabitNetworks.COM>
Cc: linuxppc-embedded@lists.linuxppc.org, cort@cs.nmt.edu,
jfd@cs.stanford.edu
Subject: Re: MPC8240 EPIC Driver (Attached)
Date: Sat, 11 Aug 2001 19:47:23 -0400 [thread overview]
Message-ID: <3B75C40B.8BCDDD2B@mvista.com> (raw)
In-Reply-To: 200108110718.AAA01730@krakatoa.gigabitnetworks.com
James F Dougherty wrote:
>
> A while ago, I posted some questions on getting the OpenPIC driver working
> correctly for the EPIC (Embedded Programmable Interrupt Controller) internal
> to the MPC8240. After several attempts on open_pic.*, I gave up, and ported a
> an existing driver.
Ummm, I'm confused. The existing PowerPC OpenPIC works just fine with
the 8240/8245/MPC107 EPICs, at least on the Sandpoint. I can't believe
there would be much of anything needed for a custom board. I have some
Sandpoint X3 patches that enables the serial mode control lines as well.
I think there could be a few minor improvements, but it is certainly
functional. All you should need are the interrupt senses table for
the OpenPIC initialization and the proper routing table for the PCI
setup.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-11 23:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-11 7:18 MPC8240 EPIC Driver (Attached) James F Dougherty
2001-08-11 23:47 ` Dan Malek [this message]
2001-08-13 15:56 ` Andrew Johnson
2001-08-13 12:54 ` Matt Porter
2001-08-13 18:00 ` Mark A. Greer
2001-08-13 19:56 ` Andrew Johnson
2001-08-13 20:38 ` Mark A. Greer
2001-08-13 21:30 ` Andrew Johnson
2001-08-13 21:47 ` Mark A. Greer
-- strict thread matches above, loose matches on Subject: below --
2001-08-14 7:43 James F Dougherty
2001-08-14 17:45 ` Mark A. Greer
2001-08-14 21:37 ` Mark A. Greer
2001-08-14 23:20 ` Dan Malek
2001-08-15 6:27 James F Dougherty
2001-08-15 6:31 James F Dougherty
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=3B75C40B.8BCDDD2B@mvista.com \
--to=dan@mvista.com \
--cc=cort@cs.nmt.edu \
--cc=jfd@GigabitNetworks.COM \
--cc=jfd@cs.stanford.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.