Re: [oe-commits] org.oe.dev conf/machine/include/tune-ppc405.inc : Move TARGET_FPU = "soft" to the tune file so its

Re: [oe-commits] org.oe.dev conf/machine/include/tune-ppc405.inc : Move TARGET_FPU = "soft" to the tune file so its

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

ifaistos commit schreef:
> conf/machine/include/tune-ppc405.inc : Move TARGET_FPU    =  "soft" to the tune file so its 
> get used by all machines that have a amcc405 cpu

If the ppc kernel has a floating point emulator, this setting should be
moved to the distrobution, since it's policy.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHI0/OMkyGM64RGpERAhaJAJ45iudeERW/KCWNIDG8trBIp0rFvgCfSb86
XUXK0oRevc8E/wMXQPaRiRg=
=O3km
-----END PGP SIGNATURE-----

Re: [oe-commits] org.oe.dev conf/machine/include/tune-ppc405.inc : Move TARGET_FPU = "soft" to the tune file so its

[Stelios Koroneos]

ok, point taken.
It should default to TARGET_FPU = "soft" only if the
distro/machine/local.conf don't define it differently
i.e TARGET_FPU ?= "soft"

Stelios S. Koroneos

Digital OPSiS - Embedded Intelligence
http://www.digital-opsis.com


> -----Original Message-----
> From: openembedded-devel-bounces@openembedded.org
> [mailto:openembedded-devel-bounces@openembedded.org]On Behalf Of Koen Kooi
> Sent: Saturday, October 27, 2007 5:49 PM
> To: Using the OpenEmbedded metadata to build Distributions
> Subject: Re: [oe] [oe-commits] org.oe.dev
> conf/machine/include/tune-ppc405.inc : Move TARGET_FPU = "soft"
> to the tune file so its
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> ifaistos commit schreef:
> > conf/machine/include/tune-ppc405.inc : Move TARGET_FPU    =
> "soft" to the tune file so its
> > get used by all machines that have a amcc405 cpu
>
> If the ppc kernel has a floating point emulator, this setting should be
> moved to the distrobution, since it's policy.
>
> regards,
>
> Koen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFHI0/OMkyGM64RGpERAhaJAJ45iudeERW/KCWNIDG8trBIp0rFvgCfSb86
> XUXK0oRevc8E/wMXQPaRiRg=
> =O3km
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: [oe-commits] org.oe.dev conf/machine/include/tune-ppc405.inc : Move TARGET_FPU = "soft" to the tune file so its

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stelios Koroneos schreef:
> ok, point taken.
> It should default to TARGET_FPU = "soft" only if the
> distro/machine/local.conf don't define it differently
> i.e TARGET_FPU ?= "soft"

In OE when TARGET_FPU is unset, it means 'hardfloat', so their shouldn't
be any mention of TARGET_FPU in a machine.conf.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHJa6CMkyGM64RGpERAt3gAJkBYy9k1Dl0eAwzVXc8zP7H0elnSACeOhBZ
j3XmEsMtX8NkgZyI1OT7WiY=
=2DFG
-----END PGP SIGNATURE-----

Re: [oe-commits] org.oe.dev conf/machine/include/tune-ppc405.inc : Move TARGET_FPU = "soft" to the tune file so its

[Stelios Koroneos]

Although this is getting OT :)

Buidling with hardfloat for a cpu that does not have an fpu means that
1) You need to have a kernel that supports fp emulation (and actually
provides correct fp results)
2) Have it enabled by default in OE
3) Be prepared to pay the processing penalty as every fp instruction is
going to generate an exeption that needs to be handled by the kernel.

IMHO when you tune to a specific cpu then you make a decision what
"features" you want and let it up to the distro/local.conf to change
something if they have a reason to do so.

Stelios S. Koroneos

Digital OPSiS - Embedded Intelligence
http://www.digital-opsis.com


> -----Original Message-----
> From: openembedded-devel-bounces@openembedded.org
> [mailto:openembedded-devel-bounces@openembedded.org]On Behalf Of Koen Kooi
> Sent: Monday, October 29, 2007 11:57 AM
> To: openembedded-devel@openembedded.org
> Subject: Re: [oe] [oe-commits] org.oe.dev
> conf/machine/include/tune-ppc405.inc : Move TARGET_FPU = "soft"
> to the tune file so its
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Stelios Koroneos schreef:
> > ok, point taken.
> > It should default to TARGET_FPU = "soft" only if the
> > distro/machine/local.conf don't define it differently
> > i.e TARGET_FPU ?= "soft"
>
> In OE when TARGET_FPU is unset, it means 'hardfloat', so their shouldn't
> be any mention of TARGET_FPU in a machine.conf.
>
> regards,
>
> Koen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFHJa6CMkyGM64RGpERAt3gAJkBYy9k1Dl0eAwzVXc8zP7H0elnSACeOhBZ
> j3XmEsMtX8NkgZyI1OT7WiY=
> =2DFG
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: [oe-commits] org.oe.dev conf/machine/include/tune-ppc405.inc : Move TARGET_FPU = "soft" to the tune file so its

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stelios Koroneos schreef:
> Although this is getting OT :)
> 
> Buidling with hardfloat for a cpu that does not have an fpu means that
> 1) You need to have a kernel that supports fp emulation (and actually
> provides correct fp results)
> 2) Have it enabled by default in OE
> 3) Be prepared to pay the processing penalty as every fp instruction is
> going to generate an exeption that needs to be handled by the kernel.

Right, that's how we have done it in OE for the ARMs without FPU for the
past 4 years. On ARM it's a 10x-50x slowdown, but still very popular,
i.e. debian/arm is still using hardfloat. I'm not saying it makes sense,
I'm saying that this is how it has been done for the past 4 years :)

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHJdD7MkyGM64RGpERAiYEAJ9o15AwGFUlIekx/CrlnqVfwhkKFgCgoN4N
7anBacFs+gt5jg0dRLl0aKg=
=BOhh
-----END PGP SIGNATURE-----