From: "Liu Yu-B13201" <Yu.Liu@freescale.com>
To: "derekzheng" <zhengxiang9@163.com>,
"linuxppc-dev" <linuxppc-dev@ozlabs.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: who know's what is "TestFloat cases" and how to test this feature onthe Freescale MPC8536DS board
Date: Mon, 20 Apr 2009 15:41:02 +0800 [thread overview]
Message-ID: <0A1FE637C2C7E148B9573BB60CC630E520FC0A@zch01exm26.fsl.freescale.net> (raw)
In-Reply-To: <003001c9c0d0$c6919510$53b4bf30$@com>
> -----Original Message-----
> From: linuxppc-dev-bounces+b13201=freescale.com@ozlabs.org
> [mailto:linuxppc-dev-bounces+b13201=freescale.com@ozlabs.org]
> On Behalf Of derekzheng
> Sent: Sunday, April 19, 2009 5:25 PM
> To: 'linuxppc-dev'; microblaze-uclinux@itee.uq.edu.au;
> linux-kernel@vger.kernel.org
> Subject: who know's what is "TestFloat cases" and how to test
> this feature onthe Freescale MPC8536DS board
>
> Hi all guys:
>
> The Freescale MPC8536DS board Integrated TestFloat cases, and
> I do not know how to test this feature on this board.
> Please tell me how to test it if you known
>
You can find the user manual "E500v2 SPE Floating Point" in BSP iso.
WARNING: multiple messages have this Message-ID (diff)
From: "Liu Yu-B13201" <Yu.Liu@freescale.com>
To: "derekzheng" <zhengxiang9@163.com>,
"linuxppc-dev" <linuxppc-dev@ozlabs.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: who know's what is "TestFloat cases" and how to test this feature onthe Freescale MPC8536DS board
Date: Mon, 20 Apr 2009 15:41:02 +0800 [thread overview]
Message-ID: <0A1FE637C2C7E148B9573BB60CC630E520FC0A@zch01exm26.fsl.freescale.net> (raw)
In-Reply-To: <003001c9c0d0$c6919510$53b4bf30$@com>
> -----Original Message-----
> From: linuxppc-dev-bounces+b13201=3Dfreescale.com@ozlabs.org=20
> [mailto:linuxppc-dev-bounces+b13201=3Dfreescale.com@ozlabs.org]=20
> On Behalf Of derekzheng
> Sent: Sunday, April 19, 2009 5:25 PM
> To: 'linuxppc-dev'; microblaze-uclinux@itee.uq.edu.au;=20
> linux-kernel@vger.kernel.org
> Subject: who know's what is "TestFloat cases" and how to test=20
> this feature onthe Freescale MPC8536DS board
>=20
> Hi all guys:
>=20
> The Freescale MPC8536DS board Integrated TestFloat cases, and=20
> I do not know how to test this feature on this board.
> Please tell me how to test it if you known
>=20
You can find the user manual "E500v2 SPE Floating Point" in BSP iso.
next prev parent reply other threads:[~2009-04-20 7:41 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 9:56 Microblaze fixes for revision monstr
2009-04-16 9:56 ` [PATCH 01/11] microblaze: Remove unneded per cpu SYSCALL_SAVE variable monstr
2009-04-16 9:56 ` [PATCH 02/11] microblaze: Remove while(1) loop from show_regs function monstr
2009-04-16 9:56 ` [PATCH 03/11] microblaze: Remove uncache shadow condition monstr
2009-04-16 9:56 ` [PATCH 04/11] microblaze: Rename kernel_mode to pt_mode in pt_regs monstr
2009-04-16 9:56 ` [PATCH 05/11] microblaze: Move task_pt_regs up monstr
2009-04-16 9:56 ` [PATCH 06/11] microblaze: Remove sparse error in traps.c monstr
2009-04-16 9:56 ` [PATCH 07/11] microblaze: Add missing declaration for die and _exception func monstr
2009-04-16 9:56 ` [PATCH 08/11] microblaze: Add missing preadv and pwritev syscalls monstr
2009-04-16 9:56 ` [PATCH 09/11] microblaze: Move start_thread to process.c monstr
2009-04-16 9:56 ` [PATCH 10/11] microblaze: Remove redundant variable monstr
2009-04-16 9:56 ` [PATCH 11/11] microblaze: Kconfig: Enable drivers for Microblaze monstr
2009-04-17 5:01 ` [microblaze-uclinux] " John Williams
2009-04-17 6:52 ` Grant Likely
2009-04-17 17:21 ` Stephen Neuendorffer
2009-04-17 17:06 ` Stephen Neuendorffer
2009-04-18 5:49 ` Grant Likely
2009-04-18 5:49 ` Grant Likely
2009-04-19 2:41 ` Stephen Neuendorffer
2009-04-19 23:03 ` John Williams
2009-04-19 23:03 ` John Williams
2009-04-20 5:51 ` Stephen Neuendorffer
[not found] ` <977C41F842E66D4CB2E41332313B6150069D3D27@XSJ-EXCHVS1.xlnx.xilinx.com>
2009-04-20 14:36 ` John Linn
2009-04-20 14:36 ` John Linn
2009-04-20 14:48 ` Grant Likely
2009-04-20 14:48 ` Grant Likely
2009-04-21 2:24 ` John Williams
2009-04-21 2:24 ` John Williams
2009-04-24 10:49 ` Arnd Bergmann
2009-04-19 9:25 ` who know's what is "TestFloat cases" and how to test this feature on the Freescale MPC8536DS board derekzheng
2009-04-19 9:25 ` derekzheng
2009-04-19 16:40 ` Kumar Gala
2009-04-20 5:29 ` zhengxiang9
2009-04-20 7:41 ` Liu Yu-B13201 [this message]
2009-04-20 7:41 ` who know's what is "TestFloat cases" and how to test this feature onthe " Liu Yu-B13201
2009-04-17 4:57 ` [microblaze-uclinux] [PATCH 10/11] microblaze: Remove redundant variable John Williams
2009-04-17 4:57 ` [microblaze-uclinux] [PATCH 09/11] microblaze: Move start_thread to process.c John Williams
2009-04-17 4:56 ` [microblaze-uclinux] [PATCH 08/11] microblaze: Add missing preadv and pwritev syscalls John Williams
2009-04-17 4:55 ` [microblaze-uclinux] [PATCH 07/11] microblaze: Add missing declaration for die and _exception func John Williams
2009-04-17 4:55 ` [microblaze-uclinux] [PATCH 06/11] microblaze: Remove sparse error in traps.c John Williams
2009-04-17 2:25 ` [microblaze-uclinux] [PATCH 02/11] microblaze: Remove while(1) loop from show_regs function John Williams
2009-04-20 20:31 ` Microblaze fixes for revision Andrew Morton
2009-04-21 6:30 ` Michal Simek
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=0A1FE637C2C7E148B9573BB60CC630E520FC0A@zch01exm26.fsl.freescale.net \
--to=yu.liu@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=zhengxiang9@163.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 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.