From: Neil Wilson <NWILSON@Airspan.com>
To: "'Dan Malek'" <dan@mvista.com>,
James F Dougherty <jfd@GigabitNetworks.COM>
Cc: linuxppc-embedded@lists.linuxppc.org, cort@cs.nmt.edu
Subject: RE: ppc-linux EPIC (OpenPIC) and Interrupts on MPC8240
Date: Tue, 10 Jul 2001 08:34:10 +0100 [thread overview]
Message-ID: <E69FF45ADA3BD511A25900047623CC4F12AA8D@JUPITER> (raw)
If anyone has those patches are to hand I wouldn't mind them for my
Sandpoint X3 7450, thanks.
Neil
> -----Original Message-----
> From: Dan Malek [SMTP:dan@mvista.com]
> Sent: Monday, July 09, 2001 6:58 PM
> To: James F Dougherty
> Cc: linuxppc-embedded@lists.linuxppc.org; cort@cs.nmt.edu
> Subject: Re: ppc-linux EPIC (OpenPIC) and Interrupts on MPC8240
>
>
> James F Dougherty wrote:
>
> > The board is essentially a Motorola Sandpoint design variant, so
> > I have started with the MontaVista Sandpoint port of linux-2.3.1
>
> What is linux-2.3.1? Which version of the Sandpoint?
>
> If it is the old Sandpoint X2, and you are using the EPIC with
> discrete interrups (IRQ0 - IRQ4) the latest MontaVista HHL 2.0
> should be used (it should be used in any case). The code in
> the public BK trees should also match this release. If you are
> using a Sandpoint X3 with the serial mode interrupt EPIC, there
> are some patches I'll have to send you.
>
>
> -- Dan
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-07-10 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 7:34 Neil Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-12 18:03 ppc-linux EPIC (OpenPIC) and Interrupts on MPC8240 James F Dougherty
2001-07-09 21:57 James F Dougherty
2001-07-09 22:27 ` Andrew Johnson
2001-07-09 23:46 ` Tom Rini
2001-07-06 21:39 James F Dougherty
2001-07-09 17:57 ` Dan Malek
2001-07-09 20:00 ` Andrew Johnson
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=E69FF45ADA3BD511A25900047623CC4F12AA8D@JUPITER \
--to=nwilson@airspan.com \
--cc=cort@cs.nmt.edu \
--cc=dan@mvista.com \
--cc=jfd@GigabitNetworks.COM \
--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