public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm•de>
To: Robert Woodworth <rwoodworth@securics•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Xilinx Virtex4 FX PPC
Date: Wed, 22 Aug 2007 00:14:22 +0200	[thread overview]
Message-ID: <46CB63BE.2050700@anagramm.de> (raw)
In-Reply-To: <1187630817.6336.34.camel@PisteOff>

Hi, Robert, Josh

>>> Question 1:
>>> Do I need a special glibc for the Xilinx PPC 405????  
>>> Does a normal PPC glibc have more "advanced" instructions compiled in
>>> that will not work on a Xilinx PPC 405??

Have a look at the eglibc project (embedded glibc) at http://www.eglibc.org
I think they support all kind of soft-fp configurations.
(i.e. The stuff seems to work fine on my MPC8540 e500 core with soft-fp)

>> Make sure you're building glibc with soft-fp, or make sure you have
>> CONFIG_MATH_EMULATION enabled in your kernel.  The PPC 405 doesn't have
>> an FPU.
>>
>> josh
> 
> CONFIG_MATH_EMULATION fixed it!!
> 
> What are the opinions out there? 
> Kernel fp or glibc soft-fp??

AFAICT: soft-fp in (e)glibc. They should be faster / hopefully more
optimized to your specific cpu.

Regards,
-- 
Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany

http://www.anagramm-technology.com
Phone: +49-89-741518-50
Fax: +49-89-741518-19

  parent reply	other threads:[~2007-08-21 22:14 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
2007-08-21 22:14     ` Clemens Koller [this message]
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=46CB63BE.2050700@anagramm.de \
    --to=clemens.koller@anagramm$(echo .)de \
    --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