[meta-intel] Fwd: [yocto] DEFAULTTUNE="core2-64" in D2550 & MACHINE="intel-core2-32"

Mon Apr 13 00:21:14 PDT 2015

C.C.

---------- Forwarded message ----------
From: J.J. Garcia <sm0ketst at gmail.com>
Date: 2015-04-13 9:18 GMT+02:00
Subject: Re: [yocto] [meta-intel] DEFAULTTUNE="core2-64" in D2550 &
MACHINE="intel-core2-32"
To: Saul Wold <sgw at linux.intel.com>

Morning Saul,

I'm using the Dizzy release for poky and intel-meta.

Local.conf only is modified as follows:

============================================================
MACHINE ?= "intel-core2-32"
# 64 works fine
#DEFAULTTUNE = "core2-64"
# x32 fails
#DEFAULTTUNE = "core2-64-x32"
PREFERRED_PROVIDER_virtual/kernel = "linux-ourpatchedkernel"
PACKAGE_CLASSES ?= "package_deb"
============================================================

Rest is the default content, target machine is an Atom D2550.
We have added a new layer for our stuff, defined also our own image recipe
(.bb) where we select to use the open-ssh server.

bblayers.conf is the default one plus our own layer.

Base Linux is a Debian 7.8.

Build Configuration:
BB_VERSION        = "1.24.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Debian-7.8"
TARGET_SYS        = "x86_64-poky-linux"
MACHINE           = "intel-core2-32"
DISTRO            = "poky"
DISTRO_VERSION    = "1.7.1"
TUNE_FEATURES     = "mx32 core2"
TARGET_FPU        = ""
meta
meta-yocto
meta-yocto-bsp    = "dizzy:ec75238f6cc2d2d8d40e0268f6d2acc070cbe9a4"
meta-intel        = "dizzy:c90fb613745cb31694144f6d2c240b4dda32ee58"
meta-ownlayer  = "blabla..."

Please let me know if you need more details,

TIA

Regards

JJ

2015-04-10 18:18 GMT+02:00 Saul Wold <sgw at linux.intel.com>:

> On 04/09/2015 03:04 AM, J.J. Garcia wrote:
>
>> Morning all,
>>
>> Tested with failures when building for mx32 (DEFAULT_TUNE="core2-64-x32"
>> and building the virtual/kernel)
>> ====================================================================
>> [...]
>> | x86_64-poky-linux-gnux32-gcc  -mx32 -march=core2 -mtune=core2 -msse3
>> -mfpmath=sse
>> --sysroot=/home/jjgarcia/Development/blabla/build/tmp/
>> sysroots/intel-core2-32
>> -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include  -fPIC
>> -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H
>> -DL_ENDIAN     -DTERMIO  -O2 -pipe -g -feliminate-unused-debug-types -Wall
>> -Wa,--noexecstack -DHAVE_CRYPTODEV -DUSE_CRYPTODEV_DIGESTS
>> -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5
>> -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM
>> -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -c -o
>> x86_64-gcc.o asm/x86_64-gcc.c
>> | asm/x86_64-gcc.c: Assembler messages:
>> | asm/x86_64-gcc.c:214: Error: `(%esi,%r8,8)' is not a valid base/index
>> expression
>> | asm/x86_64-gcc.c:215: Error: `(%edx,%r8,8)' is not a valid base/index
>> expression
>> | asm/x86_64-gcc.c:216: Error: `(%edi,%r8,8)' is not a valid base/index
>> expression
>> | asm/x86_64-gcc.c:238: Error: `(%esi,%r8,8)' is not a valid base/index
>> expression
>> | asm/x86_64-gcc.c:239: Error: `(%edx,%r8,8)' is not a valid base/index
>> expression
>> | asm/x86_64-gcc.c:240: Error: `(%edi,%r8,8)' is not a valid base/index
>> expression
>> | make[2]: *** [x86_64-gcc.o] Error 1
>> | make[2]: Leaving directory
>> `/home/jjgarcia/Development/blabla/build/tmp/work/core2-
>> 64-x32-poky-linux-gnux32/openssl/1.0.1m-r0/openssl-1.0.1m/crypto/bn'
>> | make[1]: *** [subdirs] Error 1
>> | make[1]: Leaving directory
>> `/home/jjgarcia/Development/blabla/build/tmp/work/core2-
>> 64-x32-poky-linux-gnux32/openssl/1.0.1m-r0/openssl-1.0.1m/crypto'
>> | make: *** [build_crypto] Error 1
>> | ERROR: oe_runmake failed
>> | WARNING: exit code 1 from a shell command.
>> | ERROR: Function failed: do_compile (log file is located at
>> /home/jjgarcia/Development/blabla/build/tmp/work/core2-
>> 64-x32-poky-linux-gnux32/openssl/1.0.1m-r0/temp/log.do_compile.11254)
>> ERROR: Task 621
>> (/home/jjgarcia/Development/blabla/build/../poky/meta/
>> recipes-connectivity/openssl/
>> openssl_1.0.1m.bb, do_compile) failed with exit code '1'
>> ====================================================================
>>
>> If now I use DEFAULT_TUNE="core2-64" there is no problem at all building
>> the virtual/kernel.
>>
>>  What is your exact setup, can you share your local.conf changes?  What
> MACHINE and target image or recipe are you building
>
> Also is this master or fido or and older release?
>
> Thanks
> Sau!
>
>
>  Hope it helps.
>>
>> Regards
>>
>> JJ
>>
>>
>>
>>
>>
>>
>>
>> 2015-04-09 10:28 GMT+02:00 J.J. Garcia <sm0ketst at gmail.com>:
>>
>>  Hi Sau!
>>>
>>> Thanks for you quick reply.
>>>
>>> I'm building it with the intel-core2-32 machine and with the core2-64
>>> tune
>>> this morning i'll let you know if there are issues (is it correct to use
>>> the mx32 instead the m64 in this case for the D2550? is there a
>>> noticeable
>>> increase of speed?)
>>>
>>> Im using my own defconfig (64 bits kernel enabled) but I'm wondering if
>>> there is an easy way to select the defconfig for the 32 or 64 kernels
>>> when
>>> using the intel-core2-32 machine since only one defconfig can be
>>> specified.
>>>
>>> I'm using within the files folder two folders:
>>> ./files/intel-core2-32/defconfig (this case I'll have two, one with the
>>> 64
>>> enabled config file and the other 32 bits)
>>> ./files/intel-corei7-64/defconfig
>>>
>>> When using the inte-corei7-64 is easy to provide the 64 defconfig and
>>> accordingly the same for the 32 using the intel-core2-32. But in the
>>> later
>>> case, how to make a distinction between the 32/64 different defconfig
>>> files?
>>>
>>> Again thanks and all the best for the project!
>>>
>>> Regards
>>>
>>> JJ
>>>
>>>
>>>
>>>
>>> 2015-04-08 17:33 GMT+02:00 Saul Wold <sgw at linux.intel.com>:
>>>
>>>  On 04/08/2015 06:28 AM, J.J. Garcia wrote:
>>>>
>>>>  Hi all
>>>>>
>>>>> I'm trying to use the meta-intel/DIZZY branch (MACHINE defined as
>>>>> intel-core2-32) for an Atom D2550 unit.
>>>>>
>>>>> AFAIK the 2550 supports the 64 bits so, which is the best way to build
>>>>> the
>>>>> image for the unit?
>>>>>
>>>>> Is it recommended to go for DEFAULTTUNE="core2-64" in local.conf while
>>>>> using the intel-core2-32 MACHINE?
>>>>>
>>>>>   Yes that should be correct, if you want to use 64 bit instructions
>>>>> with
>>>>>
>>>> that cpu you need to use the core2-64 tune.  Please let us know if you
>>>> have
>>>> any problems with that.
>>>>
>>>> Also for meta-intel related questions please use the
>>>> meta-intel at yoctoproject.org list as it will be seen by the right team
>>>>
>>>> Sau!
>>>>
>>>>   Thanks in advance
>>>>
>>>>>
>>>>> JJ
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-intel/attachments/20150413/fcf1caad/attachment.html>