From: diekema@bucks.si.com (diekema_jon)
To: linuxppc-embedded@lists.linuxppc.org
Cc: dan@netx4.com, r36232@email.sps.mot.com
Subject: What is the status of the Linux MPC8240/MPC8260 port?
Date: Mon, 13 Dec 1999 12:47:04 -0500 (EST) [thread overview]
Message-ID: <m11xZYu-001SzVC@bucks> (raw)
* What is the status of the Linux MPC8240/MPC8260 port?
My first query about this subject was on 11/5/1999. Dan Malek
(dan@netx4.com) stated that he has nearly completed the MPC8260
port, but hasn't updated CVS. Does Dan have an estimate of
when this might be done?
Since that time, Dennis Kung (r36232@email.sps.mot.com) from
Motorola Asia-Pacific reports LinuxPPC running the Sandpoint
MPC8240 reference platform. Are these changes going to be
released? If so, does Dennis have an estimate of when this
might be done?
What CVS root is capturing the 82xx development activity?
------------------\\----------------------\\----------------------------
Jon Diekema | | Smiths Industries
(616) 241-8310 | | 3290 Patterson Avenue, SE
diekema_jon@si.com \\ \\ Grand Rapids, MI 49512-1991
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-12-13 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-13 17:47 diekema_jon [this message]
1999-12-13 20:07 ` What is the status of the Linux MPC8240/MPC8260 port? 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=m11xZYu-001SzVC@bucks \
--to=diekema@bucks.si.com \
--cc=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=r36232@email.sps.mot.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).