From: Andrew Johnson <anj@aps.anl.gov>
To: Dan Malek <dan@mvista.com>
Cc: James F Dougherty <jfd@GigabitNetworks.COM>,
linuxppc-embedded@lists.linuxppc.org, cort@cs.nmt.edu,
jfd@cs.stanford.edu
Subject: Re: MPC8240 EPIC Driver (Attached)
Date: Mon, 13 Aug 2001 10:56:09 -0500 [thread overview]
Message-ID: <3B77F899.5964F88F@aps.anl.gov> (raw)
In-Reply-To: 3B75C40B.8BCDDD2B@mvista.com
Dan Malek wrote:
>
> 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.
Not quite - the Sandpoint has an i8259 as well, and the OpenPic code as
shipped with HHL-2.0 assumes that there is one present (at least you have
to link in the i8259 code, although you can arrange that it is never
called). Not all 8240 systems have an 8259 such as the MVME2100, and I
had to #if out some stuff from OpenPic.c to be able to omit the i8259.
Then there's the problem of accessing the 8240's interrupts for I2C, 2 DMA
channels and Message Unit, which are highly dis-contiguous with the other
interrupts; these would appear at IRQs 129, 130, 131 and 134 in the
current scheme (needing a rather large and sparse interrupt senses
table). Oh, and the 4 Global timer interrupts would have to appear at
negative IRQ numbers, so it's a good thing Linux doesn't need to use
these.
I haven't looked at James' code, but the OpenPIC stuff certainly does need
some changes to be truly universal.
- Andrew
--
The world is such a cheerful place when viewed from upside-down
It makes a rise of every fall, a smile of every frown
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-13 15:56 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
2001-08-13 15:56 ` Andrew Johnson [this message]
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=3B77F899.5964F88F@aps.anl.gov \
--to=anj@aps.anl.gov \
--cc=cort@cs.nmt.edu \
--cc=dan@mvista.com \
--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 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).