|
Issue generating working sdk containing Clang (meta-clang) and package_deb for compiling eBPF
#sdk
#dunfell
#yocto
#kernel
#linux
Hello,
I need Clang compiler apart from currently available default gcc compiler as I am trying to compile eBPF which will run on my custom yocto which is based on core-image-minimal. Therefore I
Hello,
I need Clang compiler apart from currently available default gcc compiler as I am trying to compile eBPF which will run on my custom yocto which is based on core-image-minimal. Therefore I
|
By
msg board
·
#53009
·
|
|
does meta-virtualization layer have superfluous dynamic layers stuff?
just noticed this is meta-virt layer, file layer.conf:
# The dynamic-layers directory hosts extensions and layer-specific
# modifications.
#
# The .bbappend and .bb files are included if the
just noticed this is meta-virt layer, file layer.conf:
# The dynamic-layers directory hosts extensions and layer-specific
# modifications.
#
# The .bbappend and .bb files are included if the
|
By
Robert P. J. Day
·
#53008
·
|
|
[ANNOUNCEMENT] Yocto Project 3.2.3 (gatesgarth-24.0.3) is Released
Hello,
We are pleased to announce the Yocto Project 3.2.3 (gatesgarth-24.0.3) Release is now available for
Hello,
We are pleased to announce the Yocto Project 3.2.3 (gatesgarth-24.0.3) Release is now available for
|
By
Vineela
·
#53007
·
|
|
where is the definitive/canonical layer for TPM stuff?
i just noticed that both of the layers meta-secure-core and
meta-security:
https://github.com/jiazhang0/meta-secure-core
https://git.yoctoproject.org/cgit/cgit.cgi/meta-security
seem to include a
i just noticed that both of the layers meta-secure-core and
meta-security:
https://github.com/jiazhang0/meta-secure-core
https://git.yoctoproject.org/cgit/cgit.cgi/meta-security
seem to include a
|
By
Robert P. J. Day
·
#53006
·
|
|
Re: OPencv 3.1 with Rocko
#rocko
Observed same error.
By
rohit jadhav
·
#53005
·
|
|
Re: OPencv 3.1 with Rocko
#rocko
Thank you Chuck Wolber for valuable response.
Yeah I have tried it with cleanstate on opencv and build it again but still did not worked.
Thank you Chuck Wolber for valuable response.
Yeah I have tried it with cleanstate on opencv and build it again but still did not worked.
|
By
rohit jadhav
·
#53004
·
|
|
Re: OPencv 3.1 with Rocko
#rocko
Did you try doing a cleansstate on opencv and attempting the build again?
..Ch:W..
--
"Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire
Did you try doing a cleansstate on opencv and attempting the build again?
..Ch:W..
--
"Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire
|
By
Chuck Wolber
·
#53003
·
|
|
Re: #yocto #sdk
#yocto
#sdk
For Arm EXT SDK support:
Can I modify the EXT SDK build env paths from “sdk-extra.conf” so as to reference the “vivado” env?
Is there a way to build in support so the “module load”
For Arm EXT SDK support:
Can I modify the EXT SDK build env paths from “sdk-extra.conf” so as to reference the “vivado” env?
Is there a way to build in support so the “module load”
|
By
Monsees, Steven C (US)
·
#53002
·
|
|
OPencv 3.1 with Rocko
#rocko
Observing following error
while generationg rootfs with Packages of opencv 2.4 and 3.1
RROR: opencv-3.1+gitAUTOINC+92387b1ef8-r0 do_package: Error executing a python function in exec_python_func()
Observing following error
while generationg rootfs with Packages of opencv 2.4 and 3.1
RROR: opencv-3.1+gitAUTOINC+92387b1ef8-r0 do_package: Error executing a python function in exec_python_func()
|
By
rohit jadhav
·
#53001
·
|
|
Re: #yocto #sdk
#yocto
#sdk
Thanks for your patience…
I was able to followed your advice and I am now able to build and install the Extended SDK for our Intel platform…
Can you tell me when building for Arm/Xilinx
Thanks for your patience…
I was able to followed your advice and I am now able to build and install the Extended SDK for our Intel platform…
Can you tell me when building for Arm/Xilinx
|
By
Monsees, Steven C (US)
·
#53000
·
|
|
Re: [meta-rockchip] defconfig alternatives
My thoughts on this after working on this for the nanopi-m4 have
changed a bit: it looks
like the existing kmeta system already provides us with everything we need:
- the kmeta BSP mechanism already
My thoughts on this after working on this for the nanopi-m4 have
changed a bit: it looks
like the existing kmeta system already provides us with everything we need:
- the kmeta BSP mechanism already
|
By
Yann Dirson
·
#52999
·
|
|
[meta-rockchip][PATCH v2 0/4] kmeta BSP for nanopi-m4
From: Yann Dirson <yann@...>
This second iteration adds support for KBUILD_DEFCONFIG=3D"", as well as
a loosely-related patch to avoid touching KCONFIG_MODE.
Kernel weight:
- standard
From: Yann Dirson <yann@...>
This second iteration adds support for KBUILD_DEFCONFIG=3D"", as well as
a loosely-related patch to avoid touching KCONFIG_MODE.
Kernel weight:
- standard
|
By
Yann Dirson
·
#52998
·
|
|
[meta-rockchip][PATCH v2 4/4] WIP linux-yocto: add a NanoPi-M4 BSP
From: Yann Dirson <yann@...>
This patch provides "standard" and "tiny" BSP.
There is still much work to be done in dispatching feature to individual
scc files - the more boards we can
From: Yann Dirson <yann@...>
This patch provides "standard" and "tiny" BSP.
There is still much work to be done in dispatching feature to individual
scc files - the more boards we can
|
By
Yann Dirson
·
#52997
·
|
|
[meta-rockchip][PATCH v2 3/4] NanoPi-M4: let all variants use the same KMACHINE type
From: Yann Dirson <yann@...>
Signed-off-by: Yann Dirson <yann@...>
---
conf/machine/include/nanopi-m4.inc | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Yann Dirson <yann@...>
Signed-off-by: Yann Dirson <yann@...>
---
conf/machine/include/nanopi-m4.inc | 1 +
1 file changed, 1 insertion(+)
diff --git
|
By
Yann Dirson
·
#52996
·
|
|
[meta-rockchip][PATCH v2 1/4] linux-yocto: reduce bbappend duplication
From: Yann Dirson <yann@...>
Signed-off-by: Yann Dirson <yann@...>
---
...{linux-yocto-dev.bbappend =3D> linux-yocto%.bbappend} | 0
From: Yann Dirson <yann@...>
Signed-off-by: Yann Dirson <yann@...>
---
...{linux-yocto-dev.bbappend =3D> linux-yocto%.bbappend} | 0
|
By
Yann Dirson
·
#52995
·
|
|
[meta-rockchip][PATCH v2 2/4] rockchip-defaults: don't force KCONFIG_MODE to alldefconfig
From: Yann Dirson <yann@...>
When using in-kernel defconfig this is already the default, but
linux-yocto defaults to "allnoconfig" mode when a defconfig is
specified in SRC_URI, and there
From: Yann Dirson <yann@...>
When using in-kernel defconfig this is already the default, but
linux-yocto defaults to "allnoconfig" mode when a defconfig is
specified in SRC_URI, and there
|
By
Yann Dirson
·
#52994
·
|
|
BeagleBone Black wig image does not boot
Hi all,
I successfully compile/create a target image and binaries for a BeagleBone Black:
MACHINE ?= "beaglebone-yocto"
The resulting wic image does not boot, when I write it to a sdcard nor when I
Hi all,
I successfully compile/create a target image and binaries for a BeagleBone Black:
MACHINE ?= "beaglebone-yocto"
The resulting wic image does not boot, when I write it to a sdcard nor when I
|
By
Konstantin Kletschke
·
#52993
·
|
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.2.3.rc1)
Hello All,
This is the full report for yocto-3.2.3.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
======= Summary ========
No high
Hello All,
This is the full report for yocto-3.2.3.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
======= Summary ========
No high
|
By
Sangeeta Jain
·
#52992
·
|
|
SYSVINIT_ENABLED_GETTYS dynamic setup
Hi all.
I make two images image1 image1-installer
In image1 I don't need any getty so i'd like to put SYSVINIT_ENALED_GETTYS := ""
image1.bb give the output image1.sdcard
SYSVINIT_ENABLED_GETTYS :=
Hi all.
I make two images image1 image1-installer
In image1 I don't need any getty so i'd like to put SYSVINIT_ENALED_GETTYS := ""
image1.bb give the output image1.sdcard
SYSVINIT_ENABLED_GETTYS :=
|
By
Mauro Ziliani
·
#52991
·
|
|
what is the state of upcoming(?) NXP S32G2xx support; layer, BSP?
i note that the linux-yocto repo has a nxp-s32g2xx branch:
https://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit/?h=v5.10/standard/nxp-sdk-5.4/nxp-s32g2xx
so wondering about the subsequent
i note that the linux-yocto repo has a nxp-s32g2xx branch:
https://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit/?h=v5.10/standard/nxp-sdk-5.4/nxp-s32g2xx
so wondering about the subsequent
|
By
Robert P. J. Day
·
#52990
·
|