Re: [meta-freescale] imxipuvideosink in 3.10.53 on Nitrogex6xlite
On 2015-05-26 12:53, Carlos Rafael Giani wrote: Try to re-run the playbin pipeline with the GST_DEBUG environment variable set to: 2,*imx*:9, and post the log please. Here it is. Am 2015-05-26 um 16:04 schrieb Gary Thomas: On 2015-05-26 07:59, Carlos Rafael Giani wrote: On 05/26/2015 03:50 PM, Gary Thomas wrote: Any ideas on how to get this to work (i.e. fix the broken locking)? Try if building the current master (not 0.10.1) fixes it. That's what I'm running: meta-fsl-arm: f52c9106689f33c78b09496f4929ae1e87d13970 -- Gary Thomas | Consulting for the MLB Associates |Embedded world 0:00:00.134832666 1507 0x1d53580 INFO imxeglplatform_x11 egl_platform_x11.c:114:gst_imx_egl_viv_sink_egl_platform_create: X11 EGL platform initialized, using EGL 1.4 0:00:00.139438000 1507 0x1d53580 WARN basesrc gstbasesrc.c:3470:gst_base_src_start_complete:source pad not activated yet 0:00:00.142412333 1507 0x1d53580 WARN basesrc gstbasesrc.c:3470:gst_base_src_start_complete:source pad not activated yet 0:00:00.239343000 1507 0xabf3cfb0 WARN qtdemux qtdemux_types.c:202:qtdemux_type_get: unknown QuickTime node type iods 0:00:00.239724333 1507 0xabf3cfb0 WARN qtdemux qtdemux_types.c:202:qtdemux_type_get: unknown QuickTime node type pasp 0:00:00.239807667 1507 0xabf3cfb0 WARN qtdemux qtdemux_types.c:202:qtdemux_type_get: unknown QuickTime node type sgpd 0:00:00.239872000 1507 0xabf3cfb0 WARN qtdemux qtdemux_types.c:202:qtdemux_type_get: unknown QuickTime node type sbgp 0:00:00.240018667 1507 0xabf3cfb0 WARN qtdemux qtdemux_types.c:202:qtdemux_type_get: unknown QuickTime node type iods 0:00:00.240146333 1507 0xabf3cfb0 WARN qtdemux qtdemux_types.c:202:qtdemux_type_get: unknown QuickTime node type pasp 0:00:00.247243667 1507 0xabf3cfb0 WARN qtdemux qtdemux_types.c:202:qtdemux_type_get: unknown QuickTime node type sgpd 0:00:00.247285667 1507 0xabf3cfb0 WARN qtdemux qtdemux_types.c:202:qtdemux_type_get: unknown QuickTime node type sbgp 0:00:00.288039333 1507 0xab412f80 INFO imxvpudec decoder.c:666:gst_imx_vpu_dec_start:imxvpudec0 starting VPU decoder 0:00:00.29315 1507 0xab412f80 INFO imxvpudec decoder.c:340:gst_imx_vpu_dec_load: VPU loaded 0:00:00.293204000 1507 0xab412f80 INFO imxvpudec decoder.c:341:gst_imx_vpu_dec_load: VPU firmware version 3.1.1_r46063 0:00:00.293246333 1507 0xab412f80 INFO imxvpudec decoder.c:342:gst_imx_vpu_dec_load: VPU library version 5.4.28 0:00:00.293278000 1507 0xab412f80 INFO imxvpudec decoder.c:343:gst_imx_vpu_dec_load: VPU wrapper version 1.0.58 VPUWRAPPER_ARM_LINUX Build on May 21 2015 10:23:30 0:00:00.29335 1507 0xab412f80 INFO imxvpudec decoder.c:384:gst_imx_vpu_dec_alloc_dec_mem_blocks:imxvpudec0 need to allocate 2 sub blocks for decoding 0:00:00.293384333 1507 0xab412f80 INFO imxvpudec decoder.c:388:gst_imx_vpu_dec_alloc_dec_mem_blocks:imxvpudec0 sub block 0 type: virtual size: 5676 0:00:00.293469000 1507 0xab412f80 INFO imxvpumemblocks mem_blocks.c:50:gst_imx_vpu_alloc_virt_mem_block: allocated 5676 bytes of heap memory at virt addr 0xaaa10010 0:00:00.293513667 1507 0xab412f80 INFO imxvpudec decoder.c:388:gst_imx_vpu_dec_alloc_dec_mem_blocks:imxvpudec0 sub block 1 type: physical size: 5236744 0:00:00.293723000 1507 0xab412f80 INFO imxphysmemallocator phys_mem_allocator.c:62:gst_imx_phys_mem_allocator_init:GstImxPhysMemAllocator@0xab4034f8 initializing physical memory allocator 0:00:00.293841000 1507 0xab412f80 DEBUGimxphysmemallocator phys_mem_allocator.c:117:gst_imx_phys_mem_allocator_alloc_internal:imxvpudecallocator0 alloc_internal called: maxsize: 5236744, align: 0, offset: 0, size: 5236744 0:00:00.310837333 1507 0xab412f80 DEBUG imxvpudecallocator allocator.c:84:gst_imx_vpu_dec_alloc_phys_mem:imxvpudecallocator0 addresses: virt: 0xa985a000 phys: 0x3880 cpu: 0xe880 0:00:00.310908333 1507 0xab412f80 INFO imxphysmemallocator phys_mem_allocator.c:152:gst_imx_phys_mem_allocator_alloc:imxvpudecallocator0 allocated memory block 0xaaa04a98 at phys addr 0x3880 with 5236744 bytes 0:00:00.310954667 1507 0xab412f80 INFO imxvpudec decoder.c:693:gst_imx_vpu_dec_start:imxvpudec0 VPU decoder started 0:00:00.312911333 1507 0xab412f80 INFO imxvpudec decoder.c:760:gst_imx_vpu_dec_set_format:imxvpudec0 setting decoder format 0:00:00.312947000 1507 0xab412f80 INFO imxvpudec decoder.c:763:gst_imx_vpu_dec_set_format:imxvpudec0 draining remaining frames from decoder 0:00:00.312991000 1507 0xab412f80 INFO imxvpudec
Re: [meta-freescale] [meta-fsl-arm][PATCH] imx-base.inc: Advertize thumb2 and vfp capability
On Wed, May 27, 2015 at 12:33 PM, Khem Raj raj.k...@gmail.com wrote: These SoCs are capable of thmub2 ISA as well as VFP unit is available on them. This patch makes the default tunes aware of that. The final ISA still remains as it is currently but it offers a choice to distros to choose an alternative thumb2 or a mix if they want to. Signed-off-by: Khem Raj raj.k...@gmail.com Your patch seems nicer; it would be good though if you could add the discussion link included at: http://patchwork.openembedded.org/patch/94025/ -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-arm][PATCH] imx-base.inc: Advertize thumb2 and vfp capability
On Wed, May 27, 2015 at 3:17 PM, Otavio Salvador ota...@ossystems.com.br wrote: On Wed, May 27, 2015 at 12:33 PM, Khem Raj raj.k...@gmail.com wrote: These SoCs are capable of thmub2 ISA as well as VFP unit is available on them. This patch makes the default tunes aware of that. The final ISA still remains as it is currently but it offers a choice to distros to choose an alternative thumb2 or a mix if they want to. Signed-off-by: Khem Raj raj.k...@gmail.com Your patch seems nicer; it would be good though if you could add the discussion link included at: http://patchwork.openembedded.org/patch/94025/ And please, improve your commit log a little bit. I think it's confusing. These SoCs are capable of thmub2 ISA as well as VFP unit is available on them. This patch makes the default tunes aware of that. The final ISA still remains as it is currently but it offers a choice to distros to choose an alternative thumb2 or a mix if they want to. Instead of these socs please say The mx6 SoCs typo thmub2 - thumb2 soc are capable of thumb2 and VFP unit is available? The final ISA still remains as it is currently What does it means? The default for ISA is the same? And please, avoid choice and choose in the same sentence. And I'm not sure what you mean by thumb2 or a mix, if they want to (who is they? distros doesn't make choices ) Maybe something like: mx6 SoC can be used with both thumb2 ISA or VFP enabled. Change the default tunes in order to enable both always. In addition, it offers more options to external distros. At least it was what I understood from your commit log. This way you can double check if my understanding is what you meant. Daiane -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] iMX6 - CONFIG_SYS_GENERIC_BOARD macro defined in U-Boot
On Tue, May 26, 2015 at 11:00 AM, ansaris ansa...@iwavesystems.com wrote: Hi, We are using imx6Q SabreSD platform for our development with Linux3.14.28_1.0.0-GA BSP. But initially we used Linux 3.10.17_1.0.0-GA BSP. The Linux3.14.28_1.0.0-GA BSP uses U-Boot-2014.04 and the Linux 3.10.17_1.0.0-GA BSP uses U-Boot-2013.04 versions. Maybe it would be better if you send this question to u-boot mailing list. I don't know the answer, but if it was a quiz, I would guess it is because of SPL. Daiane We have gone through below file in U-Boot-2014.04 and found that the CONFIG_SYS_GENERIC_BOARD macro is defined. ~/u-boot-imx/include/configs/mx6sabre_common.h Because of the macro CONFIG_SYS_GENERIC_BOARD definition, the board_init_f and board_init_r functions are executed from the below files respectively. ~/u-boot-imx/common/board_f.c ~/u-boot-imx/common/board_r.c But we have gone through below file in U-Boot-2013.04 and found that the CONFIG_SYS_GENERIC_BOARD macro is not defined. ~/u-boot-imx/include/configs/mx6qsabre_common.h With U-Boot-2013.04, the board_init_f and board_init_r functions are executed from the below file ~/u-boot-imx/arch/arm/lib/board.c From U-Boot-2014.04, why the board_init_f and board_init_r functions are not executed from below file. ~/u-boot-imx/arch/arm/lib/board.c Please suggest us. Thanks and Regards, Ansari -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-arm][PATCH] imx-base.inc: Advertize thumb2 and vfp capability
On May 27, 2015, at 11:17 AM, Otavio Salvador ota...@ossystems.com.br wrote: On Wed, May 27, 2015 at 12:33 PM, Khem Raj raj.k...@gmail.com wrote: These SoCs are capable of thmub2 ISA as well as VFP unit is available on them. This patch makes the default tunes aware of that. The final ISA still remains as it is currently but it offers a choice to distros to choose an alternative thumb2 or a mix if they want to. Signed-off-by: Khem Raj raj.k...@gmail.com Your patch seems nicer; it would be good though if you could add the discussion link included at: http://patchwork.openembedded.org/patch/94025/ OK will send a v2 -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 signature.asc Description: Message signed with OpenPGP using GPGMail -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-arm][PATCH] imx-base.inc: Advertize thumb2 and vfp capability
On May 27, 2015, at 11:48 AM, Daiane Angolini daiane.l...@gmail.com wrote: On Wed, May 27, 2015 at 3:17 PM, Otavio Salvador ota...@ossystems.com.br wrote: On Wed, May 27, 2015 at 12:33 PM, Khem Raj raj.k...@gmail.com wrote: These SoCs are capable of thmub2 ISA as well as VFP unit is available on them. This patch makes the default tunes aware of that. The final ISA still remains as it is currently but it offers a choice to distros to choose an alternative thumb2 or a mix if they want to. Signed-off-by: Khem Raj raj.k...@gmail.com Your patch seems nicer; it would be good though if you could add the discussion link included at: http://patchwork.openembedded.org/patch/94025/ And please, improve your commit log a little bit. I think it's confusing. These SoCs are capable of thmub2 ISA as well as VFP unit is available on them. This patch makes the default tunes aware of that. The final ISA still remains as it is currently but it offers a choice to distros to choose an alternative thumb2 or a mix if they want to. Instead of these socs please say The mx6 SoCs” sure typo thmub2 - thumb2 yes soc are capable of thumb2 and VFP unit is available? The final ISA still remains as it is currently What does it means? The default for ISA is the same? It means that code generation still remains as it was before unless thumb2 is chosen explicitly. And please, avoid choice and choose in the same sentence. And I'm not sure what you mean by thumb2 or a mix, if they want to (who is they? distros doesn't make choices ) what ? Distro make choices about default ISA before the machines, they got to choose from the options that are offered by a machine. Maybe something like: mx6 SoC can be used with both thumb2 ISA or VFP enabled. Change the default tunes in order to enable both always. In addition, it offers more options to external distros. “ its a machine layer so all distros are external to it. At least it was what I understood from your commit log. This way you can double check if my understanding is what you meant. Thanks for your feedback, I will send a v2 shortly. Daiane -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale signature.asc Description: Message signed with OpenPGP using GPGMail -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [meta-fsl-arm][PATCH] imx-base.inc: Advertize thumb2 and vfp capability
On Wed, May 27, 2015 at 4:08 PM, Khem Raj raj.k...@gmail.com wrote: On May 27, 2015, at 11:48 AM, Daiane Angolini daiane.l...@gmail.com wrote: On Wed, May 27, 2015 at 3:17 PM, Otavio Salvador ota...@ossystems.com.br wrote: On Wed, May 27, 2015 at 12:33 PM, Khem Raj raj.k...@gmail.com wrote: These SoCs are capable of thmub2 ISA as well as VFP unit is available on them. This patch makes the default tunes aware of that. The final ISA still remains as it is currently but it offers a choice to distros to choose an alternative thumb2 or a mix if they want to. Signed-off-by: Khem Raj raj.k...@gmail.com Your patch seems nicer; it would be good though if you could add the discussion link included at: http://patchwork.openembedded.org/patch/94025/ And please, improve your commit log a little bit. I think it's confusing. These SoCs are capable of thmub2 ISA as well as VFP unit is available on them. This patch makes the default tunes aware of that. The final ISA still remains as it is currently but it offers a choice to distros to choose an alternative thumb2 or a mix if they want to. Instead of these socs please say The mx6 SoCs” sure typo thmub2 - thumb2 yes soc are capable of thumb2 and VFP unit is available? The final ISA still remains as it is currently What does it means? The default for ISA is the same? It means that code generation still remains as it was before unless thumb2 is chosen explicitly. You turn, and turn, and turn only to say nothing changed. I'm sorry, but it is confusing to me. And please, avoid choice and choose in the same sentence. And I'm not sure what you mean by thumb2 or a mix, if they want to (who is they? distros doesn't make choices ) what ? Distro make choices about default ISA before the machines, they got to choose from the options that are offered by a machine. People make choices. Distro can be configured, can override, can a lot of thing, not make a choice. Please, don't personify distro =P But it's not very important, try only to not say chose the choice. choice the option is nicer Maybe something like: mx6 SoC can be used with both thumb2 ISA or VFP enabled. Change the default tunes in order to enable both always. In addition, it offers more options to external distros. “ its a machine layer so all distros are external to it. Yes, you are right. Daiane At least it was what I understood from your commit log. This way you can double check if my understanding is what you meant. Thanks for your feedback, I will send a v2 shortly. Daiane -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [meta-fsl-arm][PATCH] imx-base.inc: Advertize thumb2 and vfp capability
These SoCs are capable of thmub2 ISA as well as VFP unit is available on them. This patch makes the default tunes aware of that. The final ISA still remains as it is currently but it offers a choice to distros to choose an alternative thumb2 or a mix if they want to. Signed-off-by: Khem Raj raj.k...@gmail.com --- conf/machine/include/imx-base.inc | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/conf/machine/include/imx-base.inc b/conf/machine/include/imx-base.inc index 5683041..d80ca46 100644 --- a/conf/machine/include/imx-base.inc +++ b/conf/machine/include/imx-base.inc @@ -30,11 +30,13 @@ PREFERRED_VERSION_directfb_mx6 = 1.7.4 # Ship kernel modules MACHINE_EXTRA_RRECOMMENDS = kernel-modules -# Float-Point setting +# Defaults is to show thumb2, VFP and Neon +# capabilities +# Float-Point ABI setting # handled by software -# DEFAULTTUNE_mx6 ?= cortexa9-neon +# DEFAULTTUNE_mx6 ?= cortexa9t2-vfp-neon # handled by hardware -DEFAULTTUNE_mx6 ?= cortexa9hf-neon +DEFAULTTUNE_mx6 ?= cortexa9t2hf-vfp-neon # Sub-architecture support MACHINE_SOCARCH_SUFFIX ?= -- 2.1.4 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
[meta-freescale] [PATCH V2] imx-base.inc: Enable thumb2 and vfp capability
MX6 SoCs have VFP unit and also support thumb2 ISA This patch makes the default machine tunes aware of thumb2 and VFP. The ISA for code generation still remains as it was before this patch, in addition it now offers different ISA options to OE distributions e.g thumb2, mixed (Thumb2/ARM) or ARM (default) Discussions which resulted in this patch are here [1] [1] https://lists.yoctoproject.org/pipermail/meta-freescale/2015-May/013904.html Signed-off-by: Khem Raj raj.k...@gmail.com --- conf/machine/include/imx-base.inc | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/conf/machine/include/imx-base.inc b/conf/machine/include/imx-base.inc index 5683041..d80ca46 100644 --- a/conf/machine/include/imx-base.inc +++ b/conf/machine/include/imx-base.inc @@ -30,11 +30,13 @@ PREFERRED_VERSION_directfb_mx6 = 1.7.4 # Ship kernel modules MACHINE_EXTRA_RRECOMMENDS = kernel-modules -# Float-Point setting +# Defaults is to show thumb2, VFP and Neon +# capabilities +# Float-Point ABI setting # handled by software -# DEFAULTTUNE_mx6 ?= cortexa9-neon +# DEFAULTTUNE_mx6 ?= cortexa9t2-vfp-neon # handled by hardware -DEFAULTTUNE_mx6 ?= cortexa9hf-neon +DEFAULTTUNE_mx6 ?= cortexa9t2hf-vfp-neon # Sub-architecture support MACHINE_SOCARCH_SUFFIX ?= -- 2.1.4 -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH V2] imx-base.inc: Enable thumb2 and vfp capability
On Wed, May 27, 2015 at 9:49 PM, Khem Raj raj.k...@gmail.com wrote:
MX6 SoCs have VFP unit and also support thumb2 ISA
This patch makes the default machine tunes aware of thumb2 and VFP.
The ISA for code generation still remains as it was before this patch,
in addition it now offers different ISA options to OE distributions e.g
thumb2, mixed (Thumb2/ARM) or ARM (default)
Discussions which resulted in this patch are here [1]
[1]
https://lists.yoctoproject.org/pipermail/meta-freescale/2015-May/013904.html
Signed-off-by: Khem Raj raj.k...@gmail.com
---
conf/machine/include/imx-base.inc | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/conf/machine/include/imx-base.inc
b/conf/machine/include/imx-base.inc
index 5683041..d80ca46 100644
--- a/conf/machine/include/imx-base.inc
+++ b/conf/machine/include/imx-base.inc
@@ -30,11 +30,13 @@ PREFERRED_VERSION_directfb_mx6 = 1.7.4
# Ship kernel modules
MACHINE_EXTRA_RRECOMMENDS = kernel-modules
-# Float-Point setting
+# Defaults is to show thumb2, VFP and Neon
+# capabilities
+# Float-Point ABI setting
# handled by software
-# DEFAULTTUNE_mx6 ?= cortexa9-neon
+# DEFAULTTUNE_mx6 ?= cortexa9t2-vfp-neon
# handled by hardware
-DEFAULTTUNE_mx6 ?= cortexa9hf-neon
+DEFAULTTUNE_mx6 ?= cortexa9t2hf-vfp-neon
# Sub-architecture support
MACHINE_SOCARCH_SUFFIX ?=
--
2.1.4
--
Instead discussing commit message: this patch breaks parsing with
ERROR: OE-core's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the
checker (see sanity.conf).
Following is the list of potential problems / advisories:
Error, the PACKAGE_ARCHS variable does not contain TUNE_PKGARCH
(${ARMPKGARCH_tune-cortexa9t2hf-vfp-neon}).Toolchain tunings invalid:
Tuning 'cortexa9t2hf-vfp-neon' has no defined features, and cannot be used.
A look into oe-core meta/conf/machine/include/tune-cortexa9.inc / line
PACKAGE_EXTRA_ARCHS_tune-cortexa9thf-neon =
${PACKAGE_EXTRA_ARCHS_tune-armv7athf-neon} cortexa9hf-vfp
cortexa9hf-vfp-neon cortexa9t2hf-vfp cortexa9t2hf-vfp-neon
makes me say my patch is nicer :)
Andreas
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] linux-congatec (fido) silent after Starting kernel ...
Hi, I am trying to understand why the higher FDT address would help. Where does the kernel extract to upon start? loadaddr=0x1200 Kind regards, alex.-- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH V2] imx-base.inc: Enable thumb2 and vfp capability
On Wed, May 27, 2015 at 3:28 PM, Andreas Müller schnitzelt...@googlemail.com wrote: On Wed, May 27, 2015 at 11:49 PM, Khem Raj raj.k...@gmail.com wrote: Yes just see if you can add vfp to it I think oe-core needs fixing probably for t2 case meanwhile we can live with it. ??? - sorry you lost me here. Just a note: Working with angstrom (enabling thumb(2))) leads to many packages with vfp/thumb2. What change do you have in mind? because in angstrom we change to use t2 when you have 't' in incoming tunes and the processor supports t2 thats why you see what you see. So when you just use 't' it all works out. However OE-Core should not freak out when we use 't2' since thats a valid combination. Hope that helps you Andreas -- ___ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale
Re: [meta-freescale] [PATCH V2] imx-base.inc: Enable thumb2 and vfp capability
On May 27, 2015 1:38 PM, Andreas Müller schnitzelt...@googlemail.com
wrote:
On Wed, May 27, 2015 at 9:49 PM, Khem Raj raj.k...@gmail.com wrote:
MX6 SoCs have VFP unit and also support thumb2 ISA
This patch makes the default machine tunes aware of thumb2 and VFP.
The ISA for code generation still remains as it was before this patch,
in addition it now offers different ISA options to OE distributions e.g
thumb2, mixed (Thumb2/ARM) or ARM (default)
Discussions which resulted in this patch are here [1]
[1]
https://lists.yoctoproject.org/pipermail/meta-freescale/2015-May/013904.html
Signed-off-by: Khem Raj raj.k...@gmail.com
---
conf/machine/include/imx-base.inc | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/conf/machine/include/imx-base.inc
b/conf/machine/include/imx-base.inc
index 5683041..d80ca46 100644
--- a/conf/machine/include/imx-base.inc
+++ b/conf/machine/include/imx-base.inc
@@ -30,11 +30,13 @@ PREFERRED_VERSION_directfb_mx6 = 1.7.4
# Ship kernel modules
MACHINE_EXTRA_RRECOMMENDS = kernel-modules
-# Float-Point setting
+# Defaults is to show thumb2, VFP and Neon
+# capabilities
+# Float-Point ABI setting
# handled by software
-# DEFAULTTUNE_mx6 ?= cortexa9-neon
+# DEFAULTTUNE_mx6 ?= cortexa9t2-vfp-neon
# handled by hardware
-DEFAULTTUNE_mx6 ?= cortexa9hf-neon
+DEFAULTTUNE_mx6 ?= cortexa9t2hf-vfp-neon
# Sub-architecture support
MACHINE_SOCARCH_SUFFIX ?=
--
2.1.4
--
Instead discussing commit message: this patch breaks parsing with
ERROR: OE-core's config sanity checker detected a potential
misconfiguration.
Either fix the cause of this error or at your own risk disable the
checker (see sanity.conf).
Following is the list of potential problems / advisories:
Error, the PACKAGE_ARCHS variable does not contain TUNE_PKGARCH
(${ARMPKGARCH_tune-cortexa9t2hf-vfp-neon}).Toolchain tunings invalid:
Tuning 'cortexa9t2hf-vfp-neon' has no defined features, and cannot be
used.
A look into oe-core meta/conf/machine/include/tune-cortexa9.inc / line
PACKAGE_EXTRA_ARCHS_tune-cortexa9thf-neon =
${PACKAGE_EXTRA_ARCHS_tune-armv7athf-neon} cortexa9hf-vfp
cortexa9hf-vfp-neon cortexa9t2hf-vfp cortexa9t2hf-vfp-neon
makes me say my patch is nicer :
Yes just see if you can add vfp to it
I think oe-core needs fixing probably for t2 case meanwhile we can live
with it.
Andreas
--
___
meta-freescale mailing list
meta-freescale@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-freescale
