* MPC8240
@ 1999-03-19 20:56 Dave Baukus
1999-03-22 16:48 ` MPC8240 Matt Porter
0 siblings, 1 reply; 2+ messages in thread
From: Dave Baukus @ 1999-03-19 20:56 UTC (permalink / raw)
To: linuxppc-dev
Is there any support for linux on the PPC - MPC 8240.
It is suppose to be a 603e processor core w/ embedded IO controlers (PCI, DMA,
I2O, ...)
Anybody tried this thing out yet ?
--
Dave Baukus
Inet Technologies Inc.
dbaukus@inetinc.com
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: MPC8240
1999-03-19 20:56 MPC8240 Dave Baukus
@ 1999-03-22 16:48 ` Matt Porter
0 siblings, 0 replies; 2+ messages in thread
From: Matt Porter @ 1999-03-22 16:48 UTC (permalink / raw)
To: Dave Baukus; +Cc: linuxppc-dev
On Fri, 19 Mar 1999, Dave Baukus wrote:
> Is there any support for linux on the PPC - MPC 8240.
> It is suppose to be a 603e processor core w/ embedded IO controlers (PCI, DMA,
> I2O, ...)
>
> Anybody tried this thing out yet ?
I haven't been able to touch our 8240-based VME board yet since others are
doing a VxWorks port, however I've already looked a bit at what's needed.
1) Yes, it's a 603e core so nothing new there like the 8xx MPUs. I see
memory speed rated at 66mhz/83mhz but I heard that a 100mhz fsb version
may exist. Clock speeds should go to 400mhz.
2) The PCI bridge is very similar to a MPC106 so no surprises there. It's
a bit limited from my perspective since Raven/Hawk are very versatile in
their memory map programming whereas the MPC106 only allows hardcoded maps
A&B (PReP and CHRP).
3) The EPIC is OpenPIC compliant, allowing passthrough mode if your system
has legacy I/O. You just need the OpenPIC patch (there are two versions
of this) and some mods to detect the EPIC to support it.
4) DMA controller is a new design AFAIK, you'd have to do some support for
that if you need that feature.
5) There is an I2C controller that needs support so you can gather
assuming you are bringing a system up from scratch and need to access the
SPD data in the SDRAMs.
6) I2O registers are of little interest. They are simply compliant with
the spec.
For our board, I know the only thing I need to do is patch the Raven
OpenPIC support so it handles an EPIC. The rest of the board is just a
16550, Universe II, and DEC21143.
--
Matt Porter
mmporter@home.com
This is Linux Country. On a quiet night, you can hear Windows reboot.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~1999-03-22 16:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1999-03-19 20:56 MPC8240 Dave Baukus
1999-03-22 16:48 ` MPC8240 Matt Porter
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).