From: Andrew Johnson <anj@aps.anl.gov>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: Matt Porter <mporter@mvista.com>, Dan Malek <dan@mvista.com>,
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 14:56:08 -0500 [thread overview]
Message-ID: <3B7830D8.3D9E4C45@aps.anl.gov> (raw)
In-Reply-To: 3B7815BC.8F2F180C@mvista.com
"Mark A. Greer" wrote:
>
> The changes to the openpic code for supporting serial interrupt mode are very minor.
Actually IIRC they're already present in the version shipped with
HHL-2.0. I don't remember making any changes for that at all on the
MVME2100 support, but my memory has been known to be faulty.
> What I mean is a table where you specify the irq, the offset fo the regs from the base
> address, the sensitivity, and the polarity all separately. Also the appropriate
> extensions to support serial interrupt mode (e.g., MVME2100 uses that). With a table
> format something like that, you can avoid the sparse and negative irq's on the
> 8240/107 and still keep things pretty clean looking.
That sounds right. It could also use the NIRQ field of the Feature
Reporting Register to cross-check that the table given is the correct size
for the chip it's controlling, and have some way of specifying the
presence or absensce of a cascaded i8259 (presumably with its own table).
- 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 19: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
2001-08-13 12:54 ` Matt Porter
2001-08-13 18:00 ` Mark A. Greer
2001-08-13 19:56 ` Andrew Johnson [this message]
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=3B7830D8.3D9E4C45@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 \
--cc=mgreer@mvista.com \
--cc=mporter@mvista.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).