Re: [meta-xilinx] [PATCH] xsctbase: do not delete CWD when do_configure starts
> On Jul 18, 2018, at 6:21 PM, Manjukumar Harthikote Matha
> wrote:
>
> I updated the master to track rel-v2018.2 branch.
> I don't think we had rm -rf ${XSCTH_WS} in xsctbase.bbclass, is this
> something in your tree?
Hmmm... indeed!
I added this a year ago or so because upon re-running the do_configure task on
xsctbase'd recipes, the xsct tools would react differently if it was a first
run (empty ${B} dir), or a re-run on the same "workspace". Adding the manual
cleaning of the directory fixed this and made the process solid and
reproducible.
I guess you can apply the change to your tree and see if it makes sense to you.
Or I can resend a clean patch if you prefer.
Cheers!--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx
[meta-xilinx] [meta-xilinx-bsp][PATCH] machine-xilinx-default.inc: set libgles1, libgles2 and egl to libmali-xlnx
From: Vineeth Chowdary Karumanchi
zynqmpeg and zynqmpev devices has Mali400, overrides extended with
mali400.This patch sets preferred providers to libmali-xlnx.
Signed-off-by: Vineeth Chowdary Karumanchi
Signed-off-by: Manjukumar Matha
---
meta-xilinx-bsp/conf/machine/include/machine-xilinx-default.inc | 6 ++
1 file changed, 6 insertions(+)
diff --git a/meta-xilinx-bsp/conf/machine/include/machine-xilinx-default.inc
b/meta-xilinx-bsp/conf/machine/include/machine-xilinx-default.inc
index 77fbec8..d37a43a 100644
--- a/meta-xilinx-bsp/conf/machine/include/machine-xilinx-default.inc
+++ b/meta-xilinx-bsp/conf/machine/include/machine-xilinx-default.inc
@@ -25,6 +25,12 @@ UBOOT_BINARY ?= "u-boot.${UBOOT_SUFFIX}"
UBOOT_ELF ?= "u-boot"
UBOOT_ELF_aarch64 ?= "u-boot.elf"
+#Hardware accelaration
+PREFERRED_PROVIDER_virtual/libgles1_mali400= "libmali-xlnx"
+PREFERRED_PROVIDER_virtual/libgles2_mali400= "libmali-xlnx"
+PREFERRED_PROVIDER_virtual/egl_mali400 = "libmali-xlnx"
+
+
XSERVER ?= " \
xserver-xorg \
xf86-input-evdev \
--
2.7.4
--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] Where are the TUNE_CCARGS when compiling for cortex-a53 with zynqmp
Hi Maxime, > -Original Message- > From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx- > boun...@yoctoproject.org] On Behalf Of Maxime Roussin-Belanger > Sent: Friday, July 13, 2018 10:05 AM > To: nat...@nathanrossi.com > Cc: meta-xil...@lists.yoctoproject.org > Subject: [meta-xilinx] Where are the TUNE_CCARGS when compiling for cortex- > a53 with zynqmp > > Hello! > > When are compiling our recipes with a cross aarch64-gcc compiler, we don't see > any "-march=armv8-a -mtune=cortex-a57.cortex-a53" flags in the Makefiles and > in > the log.do_compile or log.do_configure. > > We require tune-zynqmp.conf in our machine configuration and that means we do > see the aarch64 flags, but not the cortex tune. I didn't find any > tune-cortexa53, > does that mean there is nothing to do for that CPU and that we should just use > the default aarch64 tune? > The require file here https://github.com/Xilinx/meta-xilinx/blob/master/meta-xilinx-bsp/conf/machine/include/tune-zynqmp.inc#L11 includes all the required tune for aarch64 https://github.com/openembedded/openembedded-core/blob/master/meta/conf/machine/include/arm/arch-arm64.inc > Are they implicit(the compiler flags) when using an aarch64 cross compiler? > Yes > Do I have to create my own tune file for the cortex-a57.cortex-a53? > Don't think so you need one for aarch64 Thanks, Manju -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] [PATCH] xsctbase: do not delete CWD when do_configure starts
Hi Jean-Francois,
I updated the master to track rel-v2018.2 branch.
I don't think we had rm -rf ${XSCTH_WS} in xsctbase.bbclass, is this something
in your tree?
Thanks,
Manju
> -Original Message-
> From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx-
> boun...@yoctoproject.org] On Behalf Of Manjukumar Harthikote Matha
> Sent: Monday, July 16, 2018 1:21 AM
> To: Jean-Francois Dagenais ; meta-
> xil...@yoctoproject.org
> Subject: Re: [meta-xilinx] [PATCH] xsctbase: do not delete CWD when
> do_configure starts
>
> Hi Jean-Francois,
>
> I might have missed this patch, will look into it this week
>
> Thanks,
> Manju
>
> > -Original Message-
> > From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx-
> > boun...@yoctoproject.org] On Behalf Of Jean-Francois Dagenais
> > Sent: Friday, July 13, 2018 9:30 AM
> > To: meta-xilinx@yoctoproject.org
> > Subject: Re: [meta-xilinx] [PATCH] xsctbase: do not delete CWD when
> > do_configure starts
> >
> > anyone? Manju?
> >
> > > On Jun 7, 2018, at 10:19 AM, Jean-Francois Dagenais
> > wrote:
> > >
> > > This is to fix these errors in the configure.log:
> > >
> > > shell-init: error retrieving current directory: getcwd: cannot
> > > access parent directories: No such file or directory
> > > chdir: error retrieving current directory: getcwd: cannot access
> > > parent
> > > directories: No such file or directory
> > >
> > > Signed-off-by: Jean-Francois Dagenais
> > > ---
> > > classes/xsctbase.bbclass | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/classes/xsctbase.bbclass b/classes/xsctbase.bbclass
> > > index
> > > 74d8067..d764898 100644
> > > --- a/classes/xsctbase.bbclass
> > > +++ b/classes/xsctbase.bbclass
> > > @@ -27,7 +27,7 @@ do_configure() {
> > > export RDI_PLATFORM=lnx64
> > > export SWT_GTK3=0
> > >
> > > -rm -rf ${XSCTH_WS}
> > > +ls -A | xargs rm -rf
> > >
> > > if [ -d "${S}/patches" ]; then
> > >rm -rf ${S}/patches
> > > --
> > > 2.11.0
> > >
> >
> > --
> > ___
> > meta-xilinx mailing list
> > meta-xilinx@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-xilinx
> --
> ___
> meta-xilinx mailing list
> meta-xilinx@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx
--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] [[meta-xilinx-bsp][PATCH v2]] device-tree.bb: add missing include path
Applied
Thanks,
Manju
> -Original Message-
> From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx-
> boun...@yoctoproject.org] On Behalf Of Martin Siegumfeldt
> Sent: Tuesday, July 17, 2018 12:56 AM
> To: meta-xilinx@yoctoproject.org
> Subject: Re: [meta-xilinx] [[meta-xilinx-bsp][PATCH v2]] device-tree.bb: add
> missing include path
>
> Ping? Manju?
>
> From: Martin Siegumfeldt
> Sent: Thursday, June 21, 2018 2:36 PM
> To: meta-xilinx@yoctoproject.org
> Cc: Martin Siegumfeldt
> Subject: [[meta-xilinx][meta-xilinx-bsp][PATCH v2]] device-tree.bb: add
> missing
> include path
>
> This patch adds a missing include path for generic kernel DTC
> includes.
>
> Signed-off-by: Martin Siegumfeldt
> Reviewed-by: Nathan Rossi
> ---
> meta-xilinx-bsp/recipes-bsp/device-tree/device-tree.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta-xilinx-bsp/recipes-bsp/device-tree/device-tree.bb
> b/meta-xilinx-
> bsp/recipes-bsp/device-tree/device-tree.bb
> index dc49cbb..d1b6771 100644
> --- a/meta-xilinx-bsp/recipes-bsp/device-tree/device-tree.bb
> +++ b/meta-xilinx-bsp/recipes-bsp/device-tree/device-tree.bb
> @@ -30,6 +30,7 @@ SYSROOT_DIRS += "/boot/devicetree"
> KERNEL_DTS_INCLUDE ??= " \
> ${STAGING_KERNEL_DIR}/arch/${ARCH}/boot/dts \
> ${STAGING_KERNEL_DIR}/arch/${ARCH}/boot/dts/include \
> + ${STAGING_KERNEL_DIR}/scripts/dtc/include-prefixes \
> "
> # For arm64/zynqmp the xilinx specific includes are subdired under a vendor
> directory.
> KERNEL_DTS_INCLUDE_append_zynqmp = " \
> --
> 2.14.1
>
> --
> ___
> meta-xilinx mailing list
> meta-xilinx@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx
--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] [meta-xilinx-tools] error while building pmu-firmware
> -Original Message- > From: Ahsan, Noor [mailto:noor_ah...@mentor.com] > Sent: Wednesday, July 18, 2018 2:50 AM > To: Manjukumar Harthikote Matha ; meta- > xil...@lists.yoctoproject.org > Subject: RE: [meta-xilinx-tools] error while building pmu-firmware > > > > >-Original Message- > >From: Ahsan, Noor > >Sent: Monday, July 02, 2018 5:27 PM > >To: 'Manjukumar Harthikote Matha' ; meta- > xil...@lists.yoctoproject.org > >Subject: RE: [meta-xilinx-tools] error while building pmu-firmware > > > > > > > >>> but I think this is not correct as for 64bit architecture the > >>> PYTHON_SITEPACKAGES_DIR is set to /usr/lib64/python3.5/site-packages > >>> but python native will be location in /usr/lib/ not in /usr/lib64. > >>> This will cause the above error that I am getting. Have anybody seen this > issue? > >>> > >> > >>Can you try installing it on the host using > >>pip3 install pyyaml > > > >I think the meaning of this line https://github.com/Xilinx/meta-xilinx- > tools/blob/rel->v2018.2/classes/xsctyaml.bbclass#L3 was that that yaml will be > used which is building our build system. We >should not use host pyyaml. > > > Any update on this? I am not able to reproduce the error, were you able install in the host as well to see if it works? Thanks, Manju -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] [meta-xilinx-tools] error while building pmu-firmware
>-Original Message- >From: Ahsan, Noor >Sent: Monday, July 02, 2018 5:27 PM >To: 'Manjukumar Harthikote Matha' ; >meta-xil...@lists.yoctoproject.org >Subject: RE: [meta-xilinx-tools] error while building pmu-firmware > > > >>> but I think this is not correct as for 64bit architecture the >>> PYTHON_SITEPACKAGES_DIR is set to /usr/lib64/python3.5/site-packages >>> but python native will be location in /usr/lib/ not in /usr/lib64. >>> This will cause the above error that I am getting. Have anybody seen this >>> issue? >>> >> >>Can you try installing it on the host using >>pip3 install pyyaml > >I think the meaning of this line >https://github.com/Xilinx/meta-xilinx-tools/blob/rel->v2018.2/classes/xsctyaml.bbclass#L3 > was that that yaml will be used which is building our build system. We >>should not use host pyyaml. Any update on this? Noor -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
