From: Dag Nygren <dag@newtech•fi>
To: James F Dougherty <jfd@krakatoa•gigabitnetworks.com>
Cc: dan@embeddededge•com, dag@newtech•fi, sparc64@rediffmail•com,
ashisha@india•infogain.com, linuxppc-embedded@lists•linuxppc.org,
dag@newtech•fi
Subject: Re: "OpenPIC versus EPIC" in MPC8240 !
Date: Tue, 13 Nov 2001 09:17:01 +0200 [thread overview]
Message-ID: <20011113071701.21257.qmail@dag.newtech.fi> (raw)
In-Reply-To: Message from James F Dougherty <jfd@krakatoa.gigabitnetworks.com> of "Mon, 12 Nov 2001 22:42:04 PST." <200111130642.fAD6g4Zp019615@krakatoa.gigabitnetworks.com>
>
> I've been watching this thread for quite some
> time now. I spoke with Dan about adding some
> changes to this code last summer. I ran into
> some issues with OpenPIC as well on our MPC8240
> platform.
>
>
> If you guys would like to forward me your changes,
> I can merge your changes into mine (or see if they
> are relevant) and give you an interim release.
>
> Might I ask, could you describe the architecture
> of your MPC8240 IRQ mapping and IO devices?
My changes doesn't specifically touch the MPC8240 code
but are included in my port for ths VG4-board.
This board uses a MPC107, which also is an EPIC.
The stuff was posted in this NG (and also linux-developers)
and I think you can find it there. If not give me another
mail , and I will send it to you.
What it does is really only changing the interface to
openpic_init() to something more versatile/generic/useful(?).
The interface structure could/should probably be further
abstracted to multilevel cascades (any of those out there ?)
as Dan sort of pointed out, but this is a start anyway.
The appropriate files for you from the port should be
the following:
openpic2.c and openpic2.h.
You could check the vg4_setup.c for an example of
how to use the interface.
Your mileage may vary, but it works perfectly on my board.
BRGDS
Dag
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-13 7:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 6:42 "OpenPIC versus EPIC" in MPC8240 ! James F Dougherty
2001-11-13 7:17 ` Dag Nygren [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-12 8:41 Sarnath Kannan
2001-11-12 16:41 ` Dan Malek
2001-11-12 16:51 ` Dag Nygren
2001-11-12 16:58 ` Dan Malek
2001-11-12 18:00 ` Dag Nygren
2001-11-07 14:11 Sarnath Kannan
2001-11-11 23:56 ` ashish anand
2001-11-01 10:13 Sarnath Kannan
2001-11-01 17:13 ` 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=20011113071701.21257.qmail@dag.newtech.fi \
--to=dag@newtech$(echo .)fi \
--cc=ashisha@india$(echo .)infogain.com \
--cc=dan@embeddededge$(echo .)com \
--cc=jfd@krakatoa$(echo .)gigabitnetworks.com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=sparc64@rediffmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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