public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx•com>
To: "Robert Woodworth" <rwoodworth@securics•com>,
	"Josh Boyer" <jwboyer@jdub•homelinux.org>
Cc: linuxppc-embedded@ozlabs•org
Subject: RE: Xilinx Virtex4 FX PPC
Date: Mon, 20 Aug 2007 10:50:00 -0700	[thread overview]
Message-ID: <20070820175008.9A4AA670056@mail113-blu.bigfish.com> (raw)
In-Reply-To: <1187630817.6336.34.camel@PisteOff>

Note that you should pick one or the other and be consistent.

If you have MATH_EMULATION
in the kernel and use code compiled partly with and partly without
soft-fp,
then you get really strange errors, because (I believe) the soft-fp uses
a different mechanism for emulating the floating point register files
than
the kernel  (I suppose you'll also see the same thing in a system with
floating
point unit and a mixed-up compilation as well).

Steve

> -----Original Message-----
> From:=20
> linuxppc-embedded-bounces+stephen=3Dneuendorffer.name@ozlabs•org
> =20
> [mailto:linuxppc-embedded-bounces+stephen=3Dneuendorffer.name@oz
labs.org] On Behalf Of Robert Woodworth
> Sent: Monday, August 20, 2007 10:27 AM
> To: Josh Boyer
> Cc: linuxppc-embedded@ozlabs•org
> Subject: Re: Xilinx Virtex4 FX PPC
>=20
> On Mon, 2007-08-20 at 11:35 -0500, Josh Boyer wrote:
> > On Mon, 20 Aug 2007 10:00:54 -0600
> > Robert Woodworth <rwoodworth@securics•com> wrote:
> >=20
> > > Problem 2:  Build my own rootfs.
> > > If I try to build my own programs (busybox and bash at=20
> this point) with
> > > shared libc using the same glibc from my toolchain, I get=20
> an "Illegal
> > > instruction" error.  Is my glibc not compatible with my=20
> Xilinx PPC 405??
> > >=20
> > >=20
> > > If I try to build a rootfs with debian ppc packages I=20
> have the same
> > > "Illegal instruction" error.
> > >=20
> > >=20
> > >=20
> > > Question 1:
> > > Do I need a special glibc for the Xilinx PPC 405???? =20
> > > Does a normal PPC glibc have more "advanced" instructions=20
> compiled in
> > > that will not work on a Xilinx PPC 405??
> >=20
> > Make sure you're building glibc with soft-fp, or make sure you have
> > CONFIG_MATH_EMULATION enabled in your kernel.  The PPC 405=20
> doesn't have
> > an FPU.
> >=20
> > josh
>=20
>=20
> CONFIG_MATH_EMULATION fixed it!!
>=20
>=20
>=20
> What are the opinions out there?=20
> Kernel fp or glibc soft-fp??
>=20
> I don't have a need for floating point in my final application anyway.
>=20
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs•org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20
>=20

  parent reply	other threads:[~2007-08-20 17:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 16:00 Xilinx Virtex4 FX PPC Robert Woodworth
2007-08-20 16:35 ` Josh Boyer
2007-08-20 17:26   ` Robert Woodworth
2007-08-20 17:42     ` Grant Likely
2007-08-20 17:50     ` Stephen Neuendorffer [this message]
2007-08-21 22:14     ` Clemens Koller
2007-08-20 17:50 ` Grant Likely
2007-08-21  8:52 ` Stelios Koroneos
2007-08-21 12:57   ` Josh Boyer

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=20070820175008.9A4AA670056@mail113-blu.bigfish.com \
    --to=stephen.neuendorffer@xilinx$(echo .)com \
    --cc=jwboyer@jdub$(echo .)homelinux.org \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    --cc=rwoodworth@securics$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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