All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John Linn" <John.Linn@xilinx.com>
To: "Peter Korsgaard" <jacmet@sunsite.dk>
Cc: git <git@xilinx.com>, linuxppc-embedded@ozlabs.org
Subject: RE: Virtex V5FX PPC 440 Support In Xilinx Git Tree
Date: Wed, 2 Apr 2008 09:23:30 -0600	[thread overview]
Message-ID: <20080402152332.0AF84F08087@mail88-dub.bigfish.com> (raw)
In-Reply-To: <87lk3w8u00.fsf@macbook.be.48ers.dk>

Hi Peter,

We added arch/ppc support because it was the easiest path for us.  We
realize it's going away soon in the mainline.

We are working on getting arch/powerpc more mature for both the 405 and
the 440 as we do believe this is the future for powerpc.

Thanks,
John



-----Original Message-----
From: Peter Korsgaard [mailto:jacmet@gmail.com] On Behalf Of Peter
Korsgaard
Sent: Wednesday, April 02, 2008 3:51 AM
To: John Linn
Cc: linuxppc-embedded@ozlabs.org; git
Subject: Re: Virtex V5FX PPC 440 Support In Xilinx Git Tree

>>>>> "John" =3D=3D John Linn <John.Linn@xilinx.com> writes:

 John> I pushed PowerPC 440 support to the Xilinx Git server with
 John> support for ppc arch and with powerpc arch support coming in
 John> the near future.

Neat, but why have you added arch/ppc support? It's supposed to go
away pretty much by the time the hardware gets in the hand of
developers.

--=20
Bye, Peter Korsgaard

  reply	other threads:[~2008-04-02 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 23:41 Virtex V5FX PPC 440 Support In Xilinx Git Tree John Linn
2008-04-02  4:09 ` Grant Likely
2008-04-02  9:51 ` Peter Korsgaard
2008-04-02 15:23   ` John Linn [this message]
     [not found]   ` <689CB232690D8D4E97DA6C76DA098E6C05FC43ED@XCO-EXCHVS1.xlnx.xilinx.com>
2008-04-02 16:34     ` Stephen Neuendorffer

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=20080402152332.0AF84F08087@mail88-dub.bigfish.com \
    --to=john.linn@xilinx.com \
    --cc=git@xilinx.com \
    --cc=jacmet@sunsite.dk \
    --cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.