From: Brian Waite <waite@skycomputers.com>
To: Linux PPC <linuxppc-dev@lists.linuxppc.org>
Subject: Platform support for db64360
Date: Wed, 6 Aug 2003 13:58:17 -0400 [thread overview]
Message-ID: <200308061358.17279.waite@skycomputers.com> (raw)
Hi all,
There have been a few threads about support for the db64360 Evaluation
board.
I have been using the _devel tree for a while now with a port from the
_galileo tree. I have also put together the MPSC driver and support for
u-boot. Here is a rundown of the known working things:
I've tried to break down the patches into logical order for readability. Let
me know if I can make it any better.
Dink32 bootloader (may need to move around CPU mappings in db64360.h)
uBoot bootloader
PCI/PCI-X
Gigabit Ethernet
Duart serial port
MPSC as uart
Internal SRAM
HW cache coherency
SW cache coherency
SMP (untested by me)
I realized that I can't post the patches here as they are large and are
getting rejected. What is the best way to get them out to people and into the
linuxppc_2_4_devel tree? Sorry for the noise.
Thanks
Brian
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-08-06 17:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200308061358.17279.waite@skycomputers.com \
--to=waite@skycomputers.com \
--cc=linuxppc-dev@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;
as well as URLs for NNTP newsgroup(s).