From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH v2 0/5] Add support for PowerPC e500v2/SPE
Date: Wed, 20 Jul 2011 10:05:56 -0700 [thread overview]
Message-ID: <4E270AF4.3050401@linux.intel.com> (raw)
In-Reply-To: <1311097296-17200-1-git-send-email-galak@kernel.crashing.org>
On 07/19/2011 10:41 AM, Kumar Gala wrote:
> The majority of support for the PowerPC e500v2/SPE target already
> exists. However some minor cleans are required to get things working
> completely.
>
> The e500v2 utilizes a unique floating point programming model / ABI from
> other PowerPC targets and thus requires special handling.
>
> - k
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Merged into OE-Core
Thanks
Sau!
next prev parent reply other threads:[~2011-07-20 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 17:41 [PATCH v2 0/5] Add support for PowerPC e500v2/SPE Kumar Gala
2011-07-19 17:41 ` [PATCH v2 1/5] gcc: Add gcc configure for PowerPC e500v2/SPE embedded floating point ABI Kumar Gala
2011-07-19 17:41 ` [PATCH v2 2/5] tclibc-*libc: Utilize TARGET_FPU for gnuspe setting Kumar Gala
2011-07-19 17:41 ` [PATCH v2 3/5] tune-ppce500v2: Add a tune file for PowerPC e500v2 cores Kumar Gala
2011-07-19 17:41 ` [PATCH v2 4/5] openssl: Add handling for linux-gnuspe-powerpc Kumar Gala
2011-07-19 17:41 ` [PATCH v2 5/5] flac: fix build issues with e500v2 (gnuspe) toolchain Kumar Gala
2011-07-20 17:05 ` Saul Wold [this message]
2011-07-20 20:33 ` [PATCH v2 0/5] Add support for PowerPC e500v2/SPE Kumar Gala
2011-07-20 20:49 ` Saul Wold
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=4E270AF4.3050401@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@yoctoproject.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