From: "Mark A. Greer" <mgreer@mvista.com>
To: James F Dougherty <jfd@GigabitNetworks.COM>
Cc: anj@aps.anl.gov, mporter@mvista.com, dan@mvista.com,
linuxppc-embedded@lists.linuxppc.org, cort@cs.nmt.edu,
jfd@cs.stanford.edu
Subject: Re: MPC8240 EPIC Driver (Attached)
Date: Tue, 14 Aug 2001 10:45:39 -0700 [thread overview]
Message-ID: <3B7963C3.36191B14@mvista.com> (raw)
In-Reply-To: 200108140743.AAA05509@krakatoa.gigabitnetworks.com
James F Dougherty wrote:
> Mark,
>
> Send me your changes and I'll
> gladly test them...
I never finished them. I had some changes in an old 2.4.0-testxxx kernel but never
finished what I started.
This was several months ago so I kinda forget but I was going to make the
initsenses table look something like what gets passed to openpic_initirq plus a
field to specify the offset in from OpenPIC_addr/OpenPIC. I also added a couple
routines to set the epic in serial or direct mode and I think that was about it.
I may have some of this laying around. I'll take a look this afternoon & if its
worth sending, I'll send it to you.
Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-14 17:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 7:43 MPC8240 EPIC Driver (Attached) James F Dougherty
2001-08-14 17:45 ` Mark A. Greer [this message]
2001-08-14 21:37 ` Mark A. Greer
2001-08-14 23:20 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2001-08-15 6:31 James F Dougherty
2001-08-15 6:27 James F Dougherty
2001-08-11 7:18 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
2001-08-13 20:38 ` Mark A. Greer
2001-08-13 21:30 ` Andrew Johnson
2001-08-13 21:47 ` Mark A. Greer
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=3B7963C3.36191B14@mvista.com \
--to=mgreer@mvista.com \
--cc=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=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).