From: Johnnie Peters <jpeters@phx.mcd.mot.com>
To: Mark Lin <mlin@MPI-Softtech.Com>
Cc: Michael Meissner <meissner@cygnus.com>,
Adrian Cox <apc@agelectronics.co.uk>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Support for Motorola Platforms
Date: Fri, 04 Jun 1999 14:33:44 -0700 [thread overview]
Message-ID: <37584638.340D9D11@phx.mcd.mot.com> (raw)
In-Reply-To: Pine.SOL.4.05.9906041418520.24129-100000@mpi.mpi-softtech.com
Mark Lin wrote:
>
> Where did you get these patches? Are they available to the public?
I did most of the work but a few others have had contributions to
these. Motorola has allowed me to release these particular changes
to the web at this time.
Johnnie
>
> --
> Mark Lin
> MPI Software Technology, Inc.
>
> On Fri, 4 Jun 1999, Michael Meissner wrote:
>
> >
> > On Fri, Jun 04, 1999 at 03:37:13PM +0100, Adrian Cox wrote:
> > >
> > > Johnnie Peters wrote:
> > > > Motorola has a new version of the MVME2400 with the MAX processor and
> > > > as soon as I can get my hands on one I will do the work to get Linux
> > > > to run on it. Plans are also underway for new versions of the MTX
> > > > series
> > > > supporting the MAX processor.
> > >
> > > Has anybody started work on GNU tools and kernel porting for Altivec
> > > processors? The issues I see are:
> > > (1) Altivec intructions in gas, so I don't have to enter the codes by
> > > hand.
> > > (2) Linux Kernel patches to load/save Altivec registers. These are large
> > > enough that a lazy load/save might be useful.
> > > (3) (Questionable) Patches to EGCS to support the C extensions that
> > > Motorola specify in the Altivec PIM. I detest C extensions that add the
> > > keyword "vector", but all Motorola's example code uses them.
> >
> > I have patches from Motorola to add Altivec support to egcs 1.0.3. I haven't
> > been in PowerPC mode recently and haven't looked at them.
> >
> > > All of these can be done based on documentation from Motorola's website.
> > > I suspect that (1) has already happened inside some RTOS vendors, but
> > > will take a long time to filter into the standard releases.
> > >
> > > - Adrian Cox
> >
> >
> > --
> > Michael Meissner, Cygnus Solutions
> > PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886
> > email: meissner@cygnus.com phone: 978-486-9304 fax: 978-692-4482
[[ 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. ]]
next prev parent reply other threads:[~1999-06-04 21:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-04 14:41 Support for Motorola Platforms Johnnie Peters
1999-06-04 14:37 ` Adrian Cox
1999-06-04 15:59 ` Michael Meissner
1999-06-04 19:19 ` Mark Lin
1999-06-04 21:33 ` Johnnie Peters [this message]
1999-06-04 21:26 ` Mark Lin
1999-06-04 23:18 ` Johnnie Peters
1999-06-04 22:37 ` Daniel Jacobowitz
1999-06-08 1:44 ` Mark Lin
-- strict thread matches above, loose matches on Subject: below --
2006-03-23 16:27 CJ Anderson
1999-06-04 0:52 Johnnie Peters
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=37584638.340D9D11@phx.mcd.mot.com \
--to=jpeters@phx.mcd.mot.com \
--cc=apc@agelectronics.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=meissner@cygnus.com \
--cc=mlin@MPI-Softtech.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).