From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bay0-omc2-s2.bay0.hotmail.com (bay0-omc2-s2.bay0.hotmail.com [65.54.246.138]) by ozlabs.org (Postfix) with ESMTP id ED057DDF78 for ; Thu, 5 Jun 2008 00:43:49 +1000 (EST) Message-ID: Content-Type: multipart/alternative; boundary="_085e05ad-0c85-4a84-944b-00112108744b_" From: - Reyneke To: Subject: FP and signal 4 Date: Wed, 4 Jun 2008 14:43:48 +0000 MIME-Version: 1.0 List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --_085e05ad-0c85-4a84-944b-00112108744b_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, Has anyone come across any floating point issues in the new powerpc kernel = branch with regards to 44x? I'm seeing programs (i.e. init/busybox) generat= ing signal 4 (illegal instruction) exceptions. If I compile a 2.6.25 kernel= with the CONFIG_MATH_EMULATION option set, then everything works OK.=20 Using a 440EPx (has a onchip FPU) with the ELDK 4.0 ppc_4xxFP toolchain for= all apps/kernel/fs.=20 Kind of follows on from this thread: http://ozlabs.org/pipermail/linuxppc-e= mbedded/2007-June/027363.html Regards Jan _________________________________________________________________ http://clk.atdmt.com/UKM/go/msnnkmgl0010000009ukm/direct/01/= --_085e05ad-0c85-4a84-944b-00112108744b_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all,

Has anyone come across any floating point issues in the new = powerpc kernel branch with regards to 44x? I'm seeing programs (i.e. init/b= usybox) generating signal 4 (illegal instruction) exceptions. If I compile = a 2.6.25 kernel with the CONFIG_MATH_EMULATION option set, then everything = works OK.

Using a 440EPx (has a onchip FPU) with the ELDK 4.0 ppc_4= xxFP toolchain for all apps/kernel/fs.

Kind of follows on from this= thread: http://ozlabs.org/pipermail/linuxppc-embedded/2007-June/027363.htm= l

Regards
Jan

Get fish-slap= ping on Messenger! Play Now = --_085e05ad-0c85-4a84-944b-00112108744b_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "e33.co.us.ibm.com", Issuer "Equifax" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id F3BA9DDDE6 for ; Thu, 5 Jun 2008 12:31:38 +1000 (EST) Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e33.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id m552VZeM024539 for ; Wed, 4 Jun 2008 22:31:35 -0400 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m552VYow079234 for ; Wed, 4 Jun 2008 20:31:35 -0600 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m552VYUj032646 for ; Wed, 4 Jun 2008 20:31:34 -0600 Date: Wed, 4 Jun 2008 21:31:23 -0500 From: Josh Boyer To: - Reyneke Subject: Re: FP and signal 4 Message-ID: <20080604213123.4e53f813@zod.rchland.ibm.com> In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 4 Jun 2008 14:43:48 +0000 - Reyneke wrote: > > Hi all, > > Has anyone come across any floating point issues in the new powerpc kernel branch with regards to 44x? I'm seeing programs (i.e. init/busybox) generating signal 4 (illegal instruction) exceptions. If I compile a 2.6.25 kernel with the CONFIG_MATH_EMULATION option set, then everything works OK. I've not seen that. > Using a 440EPx (has a onchip FPU) with the ELDK 4.0 ppc_4xxFP toolchain for all apps/kernel/fs. 440EPx should get the FPU enabled at runtime. We use a virtual PVR to do the APU/FPU init. What does your cpu node look like in your DTS file for your board? josh From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.174]) by ozlabs.org (Postfix) with ESMTP id 592AEDDF12 for ; Thu, 5 Jun 2008 14:59:38 +1000 (EST) From: Stefan Roese To: linuxppc-embedded@ozlabs.org Subject: Re: FP and signal 4 Date: Thu, 5 Jun 2008 06:59:30 +0200 References: <20080604213123.4e53f813@zod.rchland.ibm.com> In-Reply-To: <20080604213123.4e53f813@zod.rchland.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-Id: <200806050659.30499.sr@denx.de> Cc: - Reyneke List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thursday 05 June 2008, Josh Boyer wrote: > > Has anyone come across any floating point issues in the new powerpc > > kernel branch with regards to 44x? I'm seeing programs (i.e. > > init/busybox) generating signal 4 (illegal instruction) exceptions. If I > > compile a 2.6.25 kernel with the CONFIG_MATH_EMULATION option set, then > > everything works OK. > > I've not seen that. > > > Using a 440EPx (has a onchip FPU) with the ELDK 4.0 ppc_4xxFP toolchain > > for all apps/kernel/fs. > > 440EPx should get the FPU enabled at runtime. We use a virtual PVR to > do the APU/FPU init. What does your cpu node look like in your DTS > file for your board? And please use the dtc "-b 0" option for creating the dtb file. Without it the virtual PVR setup doesn't work. Best regards, Stefan ===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office@denx.de ===================================================================== From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bay0-omc2-s38.bay0.hotmail.com (bay0-omc2-s38.bay0.hotmail.com [65.54.246.174]) by ozlabs.org (Postfix) with ESMTP id 8FC2BDDF3A for ; Thu, 5 Jun 2008 17:50:53 +1000 (EST) Message-ID: From: - Reyneke To: Stefan Roese , Subject: RE: FP and signal 4 Date: Thu, 5 Jun 2008 07:50:51 +0000 In-Reply-To: <200806050659.30499.sr@denx.de> References: <20080604213123.4e53f813@zod.rchland.ibm.com> <200806050659.30499.sr@denx.de> Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Aaah - looks like that was it. Works OK now with CONFIG_MATH_EMULATION un-s= et. For the record - cpu node looks as follows: cpu@0 { device_type =3D "cpu"; model =3D "PowerPC,440EPx"; reg =3D ; clock-frequency =3D ; /* Filled in by u-boot */ timebase-frequency =3D ; /* Filled in by u-boot */ i-cache-line-size =3D ; d-cache-line-size =3D ; i-cache-size =3D ; d-cache-size =3D ; dcr-controller; dcr-access-method =3D "native"; }; Thanks for the help. > > On Thursday 05 June 2008, Josh Boyer wrote: >>> Has anyone come across any floating point issues in the new powerpc >>> kernel branch with regards to 44x? I'm seeing programs (i.e. >>> init/busybox) generating signal 4 (illegal instruction) exceptions. If = I >>> compile a 2.6.25 kernel with the CONFIG_MATH_EMULATION option set, then >>> everything works OK. >> >> I've not seen that. >> >>> Using a 440EPx (has a onchip FPU) with the ELDK 4.0 ppc_4xxFP toolchain >>> for all apps/kernel/fs. >> >> 440EPx should get the FPU enabled at runtime. We use a virtual PVR to >> do the APU/FPU init. What does your cpu node look like in your DTS >> file for your board? > > And please use the dtc "-b 0" option for creating the dtb file. Without i= t the > virtual PVR setup doesn't work. > > Best regards, > Stefan > _________________________________________________________________ http://clk.atdmt.com/UKM/go/msnnkmgl0010000007ukm/direct/01/= From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.174]) by ozlabs.org (Postfix) with ESMTP id E1ECFDDF90 for ; Thu, 5 Jun 2008 18:29:41 +1000 (EST) From: Stefan Roese To: - Reyneke Subject: Re: FP and signal 4 Date: Thu, 5 Jun 2008 10:29:36 +0200 References: <200806050659.30499.sr@denx.de> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-Id: <200806051029.36558.sr@denx.de> Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thursday 05 June 2008, - Reyneke wrote: > Aaah - looks like that was it. Works OK now with CONFIG_MATH_EMULATION > un-set. Great. I hope "-b 0" is set by default in recent dtc versions. If not we should really do this (I already mentioned this to David Gibson before). This is a nasty bug on 440EPx which was not so easy to find. Best regards, Stefan ===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office@denx.de ===================================================================== From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from jdl.com (jdl.com [208.123.74.7]) by ozlabs.org (Postfix) with ESMTP id EBE3FDDFF4 for ; Fri, 6 Jun 2008 01:13:07 +1000 (EST) To: linuxppc-embedded@ozlabs.org Subject: Re: FP and signal 4 In-Reply-To: <200806051029.36558.sr@denx.de> Date: Thu, 05 Jun 2008 09:28:01 -0500 From: Jon Loeliger Message-Id: Cc: sr@denx.de, reynekejunk@hotmail.com List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Also sprach Zarathustra und Stefan Roese: > > I hope "-b 0" is set by default in recent dtc versions. Und Git antwortete: commit 548767f42eb00a2bac6f2a1361b7fd49f7b76908 Author: David Gibson Date: Fri May 16 13:22:57 2008 +1000 dtc: Rework handling of boot_cpuid_phys Currently, dtc will put the nonsense value 0xfeedbeef into the boot_cpuid_phys field of an output blob, unless explicitly given another value with the -b command line option. As well as being a totally unuseful default value, this also means that dtc won't properly preserve the boot_cpuid_phys field in -I dtb -O dtb mode. This patch reworks things to improve the boot_cpuid handling. The new semantics are that the output's boot_cpuid_phys value is: the value given on the command line if -b is used otherwise the value from the input, if in -I dtb mode otherwise 0 Implementation-wise we do the following: - boot_cpuid_phys is added to struct boot_info, so that structure now contains all of the blob's semantic information. - dt_to_blob() and dt_to_asm() output the cpuid given in boot_info - dt_from_blob() fills in boot_info based on the input blob - The other dt_from_*() functions just record 0, but we can change this easily if e.g. we invent a way of specifying the boot cpu in the source format. - main() overrides the cpuid in the boot_info between input and output if -b is given We add some testcases to check this new behaviour. Signed-off-by: David Gibson