|
On 3/30/21 12:42 AM, rohitbjadhav1@... wrote:
Hiit seems you are locking above said packages to revisions you want, but they also have additional dependencies, eg. the one which is causing issue here is poppler, since poppler version in zeus is 0.80.0 and krogoth has 0.41, however poppler switched to using standard types for bool starting 0.71, my suggestion is to use the versions that come with zeus release and forward port your app to consume them or second option is to fork versions then you must look at what would be the right set of packages you need to lock to older versions in-order for you to keep things going forward. Just Need some guideline to resolve this issue.
|
|
|
|
Re: eula-downloads.yoctoproject.org down???
Michael Halstead
After further discussion we've decided to take the site offline again as recommended. This check was removed on Jan 29 2016 and any systems still performing the check need to be updated.
On Tue, Mar 30, 2021 at 8:29 AM Michael Halstead via lists.yoctoproject.org <mhalstead=linuxfoundation.org@...> wrote:
--
Michael Halstead Linux Foundation / Yocto Project Systems Operations Engineer
|
|
|
|
Re: No significant diff b/w qemux86 and qemuarm poky build of core-image-minimal
On 3/30/21 1:48 PM, Ross Burton wrote:
On Tue, 30 Mar 2021 at 20:41, Khem Raj <raj.khem@...> wrote:yeah this is doing world build of not only core but several other layers included a usual build takes around 10 hrs for this machine config, I am planning toThanks for this infor Randy, really appreciated, I think I will alsoKhem: if you can reproduce this on demand with a clean build (ie 1. Collect build stats 2. buiid another qemu machine on this VM it could very well be rotting hardware underneath the VM. Ross
|
|
|
|
Re: No significant diff b/w qemux86 and qemuarm poky build of core-image-minimal
Ross Burton <ross@...>
On Tue, 30 Mar 2021 at 20:41, Khem Raj <raj.khem@...> wrote:
Thanks for this infor Randy, really appreciated, I think I will alsoKhem: if you can reproduce this on demand with a clean build (ie oe-init-build-env with a clean build directory, just set DL_DIR) then enabling buildstats would give some interesting metrics. buildstats-diff can compare two build runs and tell you what the differences are. Ross
|
|
|
|
Re: nativesdk-binutils sysroot bug?
Kenth Eriksson
No one having problems with sysroot for nativesdk-binutils / nativesdk-gcc?
|
|
|
|
Re: No significant diff b/w qemux86 and qemuarm poky build of core-image-minimal
On 3/30/21 10:45 AM, Randy MacLeod wrote:
Khem was asking if anyone had seen a >30% difference in build time forThanks for this infor Randy, really appreciated, I think I will also look at the h/w angle.
|
|
|
|
No significant diff b/w qemux86 and qemuarm poky build of core-image-minimal
Khem was asking if anyone had seen a >30% difference in build time for
qemuarm compared to other machines. I don't when building on my system: rmacleod@yow-rmacleod-lx3 b/c-i-m-x86 $ cat x86 real 43m29.142s user 0m19.887s sys 0m4.110s rmacleod@yow-rmacleod-lx3 b/c-i-m-x86 $ cat arm real 42m58.185s user 0m19.546s sys 0m3.867s This machine is relatively isolated in that there are no other users. The arm build was done second and I didn't pre-populate the downloads but so that may account for the 30 second difference. I wasn't using sstate for either build. -- # Randy MacLeod # Wind River Linux
|
|
|
|
[meta-rockchip][PATCH 3/3] WIP linux-yocto: add a NanoPi-M4 BSP
Yann Dirson
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 support the better it will get. It's sad that when a different kernel type is selected, and no BSP is available, this gets silently DWIM-handled - much time gets lost hunting for the reason. Tiny is not really testable by itself, I played with it using: PREFERRED_PROVIDER_virtual/kernel =3D "linux-yocto-tiny" KERNEL_FEATURES_append =3D "\ ktypes/base/base.scc \ features/debug/printk.scc \ cfg/fs/ext4.scc \ " Regardless from those additions, quite a number of useless hardware featu= res still manage to creep aboard. Despite this, the fitImage weight drops fr= om 11MB with "standard" to 5MB with "tiny" and boots to serial shell. --- recipes-kernel/linux/linux-yocto%.bbappend | 6 +++ .../linux-yocto/bsp/nanopi-m4-standard.scc | 7 +++ .../linux/linux-yocto/bsp/nanopi-m4-tiny.scc | 7 +++ .../linux/linux-yocto/bsp/nanopi-m4.cfg | 40 +++++++++++++++ .../linux/linux-yocto/bsp/nanopi-m4.scc | 5 ++ .../linux/linux-yocto/bsp/rk3399.cfg | 48 ++++++++++++++++++ .../linux/linux-yocto/bsp/rk3399.scc | 5 ++ .../linux/linux-yocto/bsp/rockchip.cfg | 50 +++++++++++++++++++ .../linux/linux-yocto/bsp/rockchip.scc | 6 +++ 9 files changed, 174 insertions(+) create mode 100644 recipes-kernel/linux/linux-yocto/bsp/nanopi-m4-standa= rd.scc create mode 100644 recipes-kernel/linux/linux-yocto/bsp/nanopi-m4-tiny.s= cc create mode 100644 recipes-kernel/linux/linux-yocto/bsp/nanopi-m4.cfg create mode 100644 recipes-kernel/linux/linux-yocto/bsp/nanopi-m4.scc create mode 100644 recipes-kernel/linux/linux-yocto/bsp/rk3399.cfg create mode 100644 recipes-kernel/linux/linux-yocto/bsp/rk3399.scc create mode 100644 recipes-kernel/linux/linux-yocto/bsp/rockchip.cfg create mode 100644 recipes-kernel/linux/linux-yocto/bsp/rockchip.scc diff --git a/recipes-kernel/linux/linux-yocto%.bbappend b/recipes-kernel/= linux/linux-yocto%.bbappend index 7702e3f..5193373 100644 --- a/recipes-kernel/linux/linux-yocto%.bbappend +++ b/recipes-kernel/linux/linux-yocto%.bbappend @@ -1,3 +1,9 @@ +FILESEXTRAPATHS_prepend :=3D "${THISDIR}/linux-yocto:" + +SRC_URI_append =3D "\ + file://bsp;type=3Dkmeta;subdir=3Dkernel-meta \ +" + COMPATIBLE_MACHINE_marsboard-rk3066 =3D "marsboard-rk3066" COMPATIBLE_MACHINE_rock2-square =3D "rock2-square" COMPATIBLE_MACHINE_radxarock =3D "radxarock" diff --git a/recipes-kernel/linux/linux-yocto/bsp/nanopi-m4-standard.scc = b/recipes-kernel/linux/linux-yocto/bsp/nanopi-m4-standard.scc new file mode 100644 index 0000000..5c74d6b --- /dev/null +++ b/recipes-kernel/linux/linux-yocto/bsp/nanopi-m4-standard.scc @@ -0,0 +1,7 @@ +# SPDX-License-Identifier: MIT +define KMACHINE nanopi-m4 +define KTYPE standard +define KARCH arm + +include ktypes/standard/standard.scc +include nanopi-m4.scc diff --git a/recipes-kernel/linux/linux-yocto/bsp/nanopi-m4-tiny.scc b/re= cipes-kernel/linux/linux-yocto/bsp/nanopi-m4-tiny.scc new file mode 100644 index 0000000..6e94d6a --- /dev/null +++ b/recipes-kernel/linux/linux-yocto/bsp/nanopi-m4-tiny.scc @@ -0,0 +1,7 @@ +# SPDX-License-Identifier: MIT +define KMACHINE nanopi-m4 +define KTYPE tiny +define KARCH arm + +include ktypes/tiny/tiny.scc +include nanopi-m4.scc diff --git a/recipes-kernel/linux/linux-yocto/bsp/nanopi-m4.cfg b/recipes= -kernel/linux/linux-yocto/bsp/nanopi-m4.cfg new file mode 100644 index 0000000..5864008 --- /dev/null +++ b/recipes-kernel/linux/linux-yocto/bsp/nanopi-m4.cfg @@ -0,0 +1,40 @@ +CONFIG_MFD_RK808=3Dy +CONFIG_COMMON_CLK_RK808=3Dy + +# regulators +CONFIG_REGULATOR_RK808=3Dy +CONFIG_REGULATOR_FAN53555=3Dy + +CONFIG_MMC_BLOCK=3Dy + +# audio jack +CONFIG_SND_SOC_ROCKCHIP_RT5651=3Dm + +# BT, maybe some - RFCOMM for headset voice, MSFTEXT ? +CONFIG_BT=3Dm +#CONFIG_BT_BCM=3Dm +#CONFIG_BT_HCIUART_BCM=3Dm +CONFIG_BT_RFCOMM=3Dm +CONFIG_BT_RFCOMM_TTY=3Dy +CONFIG_BT_BNEP=3Dm +CONFIG_BT_HS=3Dy +CONFIG_BT_LE=3Dy +CONFIG_BT_MSFTEXT=3Dy +CONFIG_BT_DEBUGFS=3Dy +CONFIG_WIRELESS=3Dy +CONFIG_RFKILL=3Dm + +CONFIG_PHY_ROCKCHIP_DP=3Dy + +CONFIG_VIDEO_DEV=3Dm +CONFIG_V4L_MEM2MEM_DRIVERS=3Dy +CONFIG_VIDEO_ROCKCHIP_RGA=3Dm + +CONFIG_DRM_DW_HDMI_AHB_AUDIO=3Dm +CONFIG_SND_SOC_RK3288_HDMI_ANALOG=3Dm + +CONFIG_V4L2_H264=3Dm +CONFIG_MEDIA_CONTROLLER_REQUEST_API=3Dy +CONFIG_VIDEO_HANTRO=3Dm +CONFIG_VIDEO_HANTRO_ROCKCHIP=3Dy +CONFIG_VIDEO_ROCKCHIP_VDEC=3Dm diff --git a/recipes-kernel/linux/linux-yocto/bsp/nanopi-m4.scc b/recipes= -kernel/linux/linux-yocto/bsp/nanopi-m4.scc new file mode 100644 index 0000000..f4267aa --- /dev/null +++ b/recipes-kernel/linux/linux-yocto/bsp/nanopi-m4.scc @@ -0,0 +1,5 @@ +# SPDX-License-Identifier: MIT + +kconf hardware nanopi-m4.cfg + +include rk3399.scc diff --git a/recipes-kernel/linux/linux-yocto/bsp/rk3399.cfg b/recipes-ke= rnel/linux/linux-yocto/bsp/rk3399.cfg new file mode 100644 index 0000000..232d2cf --- /dev/null +++ b/recipes-kernel/linux/linux-yocto/bsp/rk3399.cfg @@ -0,0 +1,48 @@ +# A72 errata, all past revisions +CONFIG_ARM64_ERRATUM_1319367=3Dy +# A53 errata, all patched on boot when needed +CONFIG_ARM64_ERRATUM_826319=3Dy +CONFIG_ARM64_ERRATUM_827319=3Dy +CONFIG_ARM64_ERRATUM_824069=3Dy +CONFIG_ARM64_ERRATUM_819472=3Dy + +# cru +CONFIG_CLK_RK3399=3Dy + +CONFIG_PL330_DMA=3Dy +CONFIG_I2C_RK3X=3Dy +CONFIG_SERIAL_8250_DW=3Dy + +# usb +CONFIG_PHY_ROCKCHIP_INNO_USB2=3Dy +CONFIG_PHY_ROCKCHIP_TYPEC=3Dy + +# ethernet +CONFIG_NET_VENDOR_STMICRO=3Dy +CONFIG_STMMAC_ETH=3Dm +CONFIG_STMMAC_PLATFORM=3Dm +CONFIG_DWMAC_ROCKCHIP=3Dm +CONFIG_ROCKCHIP_PHY=3Dm + +# display +CONFIG_ROCKCHIP_DW_HDMI=3Dy +CONFIG_ROCKCHIP_DW_MIPI_DSI=3Dy +CONFIG_ROCKCHIP_ANALOGIX_DP=3Dy +CONFIG_ROCKCHIP_CDN_DP=3Dy +CONFIG_DRM_DW_HDMI=3Dm +CONFIG_DRM_DW_HDMI_I2S_AUDIO=3Dm +CONFIG_DRM_DW_HDMI_CEC=3Dm +CONFIG_DRM_DW_MIPI_DSI=3Dm +CONFIG_DRM_PANFROST=3Dm + +# usb +CONFIG_USB_DWC2=3Dy +CONFIG_USB_DWC3=3Dy +CONFIG_USB_DWC3_DUAL_ROLE=3Dy + +# sd/mmc +CONFIG_MMC_SDHCI=3Dy +CONFIG_MMC_SDHCI_PLTFM=3Dy +CONFIG_MMC_DW=3Dy +CONFIG_MMC_DW_ROCKCHIP=3Dy +CONFIG_MMC_SDHCI_OF_ARASAN=3Dy diff --git a/recipes-kernel/linux/linux-yocto/bsp/rk3399.scc b/recipes-ke= rnel/linux/linux-yocto/bsp/rk3399.scc new file mode 100644 index 0000000..9b1a88e --- /dev/null +++ b/recipes-kernel/linux/linux-yocto/bsp/rk3399.scc @@ -0,0 +1,5 @@ +# SPDX-License-Identifier: MIT + +kconf hardware rk3399.cfg + +include rockchip.scc diff --git a/recipes-kernel/linux/linux-yocto/bsp/rockchip.cfg b/recipes-= kernel/linux/linux-yocto/bsp/rockchip.cfg new file mode 100644 index 0000000..eac2a31 --- /dev/null +++ b/recipes-kernel/linux/linux-yocto/bsp/rockchip.cfg @@ -0,0 +1,50 @@ +CONFIG_ARCH_ROCKCHIP=3Dy +CONFIG_COMMON_CLK_ROCKCHIP=3Dy +CONFIG_REGULATOR=3Dy +CONFIG_REGULATOR_FIXED_VOLTAGE=3Dy +CONFIG_REGULATOR_PWM=3Dy +CONFIG_I2C=3Dy +CONFIG_FW_LOADER=3Dy +CONFIG_PHY_ROCKCHIP_EMMC=3Dy +CONFIG_PINCTRL=3Dy +CONFIG_PINCTRL_ROCKCHIP=3Dy +CONFIG_ROCKCHIP_IODOMAIN=3Dy +CONFIG_ROCKCHIP_PM_DOMAINS=3Dy + +CONFIG_PWM=3Dy +CONFIG_PWM_ROCKCHIP=3Dy + +CONFIG_DRM_KMS_HELPER=3Dm +CONFIG_DRM_FBDEV_EMULATION=3Dy +CONFIG_ROCKCHIP_IOMMU=3Dy +CONFIG_DRM_ROCKCHIP=3Dm +CONFIG_DRM_BRIDGE=3Dy + +CONFIG_SND=3Dy +CONFIG_SND_SOC=3Dy +CONFIG_SND_HDA_CODEC_HDMI=3Dm +CONFIG_SND_SOC_ROCKCHIP=3Dm +CONFIG_SND_SOC_ROCKCHIP_I2S=3Dm +CONFIG_SND_SOC_ROCKCHIP_SPDIF=3Dm + +CONFIG_NVMEM=3Dy +CONFIG_ROCKCHIP_EFUSE=3Dm + +CONFIG_CPU_FREQ=3Dy + +# maybe? +CONFIG_MFD_SYSCON=3Dy +CONFIG_FB_MODE_HELPERS=3Dy + +# possibly for somewhere else +CONFIG_DRM=3Dm +CONFIG_DRM_MIPI_DSI=3Dy +CONFIG_SOUND=3Dy +CONFIG_USB=3Dy +CONFIG_SERIAL_8250=3Dy +CONFIG_SERIAL_8250_CONSOLE=3Dy + +# obviously for somewhere else +CONFIG_MULTIUSER=3Dy +CONFIG_TTY=3Dy +CONFIG_SERIAL_EARLYCON=3Dy diff --git a/recipes-kernel/linux/linux-yocto/bsp/rockchip.scc b/recipes-= kernel/linux/linux-yocto/bsp/rockchip.scc new file mode 100644 index 0000000..800f105 --- /dev/null +++ b/recipes-kernel/linux/linux-yocto/bsp/rockchip.scc @@ -0,0 +1,6 @@ +# SPDX-License-Identifier: MIT + +kconf hardware rockchip.cfg + +include cfg/dmaengine.scc +include features/mmc/mmc-block.cfg --=20 2.30.2
|
|
|
|
[meta-rockchip][PATCH 0/3] kmeta BSP for nanopi-m4
Yann Dirson
From: Yann Dirson <yann@...>
This is a first draft of a kmeta BSP for nanopi-m4, with rough granularity for now. For testing and comments. See patch 3 to play with "linux-yocto-tiny" config. Yann Dirson (3): linux-yocto: reduce bbappend duplication NanoPi-M4: let all variants use the same KMACHINE type WIP linux-yocto: add a NanoPi-M4 BSP conf/machine/include/nanopi-m4.inc | 1 + ...yocto_%.bbappend =3D> linux-yocto%.bbappend} | 6 +++ recipes-kernel/linux/linux-yocto-dev.bbappend | 10 ---- .../linux/linux-yocto-rt_%.bbappend | 10 ---- .../linux/linux-yocto-tiny_%.bbappend | 10 ---- .../linux-yocto/bsp/nanopi-m4-standard.scc | 7 +++ .../linux/linux-yocto/bsp/nanopi-m4-tiny.scc | 7 +++ .../linux/linux-yocto/bsp/nanopi-m4.cfg | 40 +++++++++++++++ .../linux/linux-yocto/bsp/nanopi-m4.scc | 5 ++ .../linux/linux-yocto/bsp/rk3399.cfg | 48 ++++++++++++++++++ .../linux/linux-yocto/bsp/rk3399.scc | 5 ++ .../linux/linux-yocto/bsp/rockchip.cfg | 50 +++++++++++++++++++ .../linux/linux-yocto/bsp/rockchip.scc | 6 +++ 13 files changed, 175 insertions(+), 30 deletions(-) rename recipes-kernel/linux/{linux-yocto_%.bbappend =3D> linux-yocto%.bb= append} (80%) delete mode 100644 recipes-kernel/linux/linux-yocto-dev.bbappend delete mode 100644 recipes-kernel/linux/linux-yocto-rt_%.bbappend delete mode 100644 recipes-kernel/linux/linux-yocto-tiny_%.bbappend create mode 100644 recipes-kernel/linux/linux-yocto/bsp/nanopi-m4-standa= rd.scc create mode 100644 recipes-kernel/linux/linux-yocto/bsp/nanopi-m4-tiny.s= cc create mode 100644 recipes-kernel/linux/linux-yocto/bsp/nanopi-m4.cfg create mode 100644 recipes-kernel/linux/linux-yocto/bsp/nanopi-m4.scc create mode 100644 recipes-kernel/linux/linux-yocto/bsp/rk3399.cfg create mode 100644 recipes-kernel/linux/linux-yocto/bsp/rk3399.scc create mode 100644 recipes-kernel/linux/linux-yocto/bsp/rockchip.cfg create mode 100644 recipes-kernel/linux/linux-yocto/bsp/rockchip.scc --=20 2.30.2
|
|
|
|
[meta-rockchip][PATCH 2/3] NanoPi-M4: let all variants use the same KMACHINE type
Yann Dirson
From: Yann Dirson <yann@...>
--- conf/machine/include/nanopi-m4.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/conf/machine/include/nanopi-m4.inc b/conf/machine/include/na= nopi-m4.inc index 74cdae8..603160f 100644 --- a/conf/machine/include/nanopi-m4.inc +++ b/conf/machine/include/nanopi-m4.inc @@ -3,6 +3,7 @@ =20 require rk3399.inc =20 +KMACHINE =3D "nanopi-m4" KERNEL_DEVICETREE =3D "rockchip/rk3399-nanopi-m4.dtb" =20 RK_BOOT_DEVICE =3D "mmcblk1" --=20 2.30.2
|
|
|
|
[meta-rockchip][PATCH 1/3] linux-yocto: reduce bbappend duplication
Yann Dirson
From: Yann Dirson <yann@...>
--- ...{linux-yocto-dev.bbappend =3D> linux-yocto%.bbappend} | 0 recipes-kernel/linux/linux-yocto-rt_%.bbappend | 10 ---------- recipes-kernel/linux/linux-yocto-tiny_%.bbappend | 10 ---------- recipes-kernel/linux/linux-yocto_%.bbappend | 10 ---------- 4 files changed, 30 deletions(-) rename recipes-kernel/linux/{linux-yocto-dev.bbappend =3D> linux-yocto%.= bbappend} (100%) delete mode 100644 recipes-kernel/linux/linux-yocto-rt_%.bbappend delete mode 100644 recipes-kernel/linux/linux-yocto-tiny_%.bbappend delete mode 100644 recipes-kernel/linux/linux-yocto_%.bbappend diff --git a/recipes-kernel/linux/linux-yocto-dev.bbappend b/recipes-kern= el/linux/linux-yocto%.bbappend similarity index 100% rename from recipes-kernel/linux/linux-yocto-dev.bbappend rename to recipes-kernel/linux/linux-yocto%.bbappend diff --git a/recipes-kernel/linux/linux-yocto-rt_%.bbappend b/recipes-ker= nel/linux/linux-yocto-rt_%.bbappend deleted file mode 100644 index 7702e3f..0000000 --- a/recipes-kernel/linux/linux-yocto-rt_%.bbappend +++ /dev/null @@ -1,10 +0,0 @@ -COMPATIBLE_MACHINE_marsboard-rk3066 =3D "marsboard-rk3066" -COMPATIBLE_MACHINE_rock2-square =3D "rock2-square" -COMPATIBLE_MACHINE_radxarock =3D "radxarock" -COMPATIBLE_MACHINE_firefly-rk3288 =3D "firefly-rk3288" -COMPATIBLE_MACHINE_vyasa-rk3288 =3D "vyasa-rk3288" -COMPATIBLE_MACHINE_tinker-board =3D "tinker-board" -COMPATIBLE_MACHINE_tinker-board-s =3D "tinker-board-s" -COMPATIBLE_MACHINE_rock-pi-4 =3D "rock-pi-4" -COMPATIBLE_MACHINE_nanopi-m4 =3D "nanopi-m4" -COMPATIBLE_MACHINE_nanopi-m4-2gb =3D "nanopi-m4-2gb" diff --git a/recipes-kernel/linux/linux-yocto-tiny_%.bbappend b/recipes-k= ernel/linux/linux-yocto-tiny_%.bbappend deleted file mode 100644 index 7702e3f..0000000 --- a/recipes-kernel/linux/linux-yocto-tiny_%.bbappend +++ /dev/null @@ -1,10 +0,0 @@ -COMPATIBLE_MACHINE_marsboard-rk3066 =3D "marsboard-rk3066" -COMPATIBLE_MACHINE_rock2-square =3D "rock2-square" -COMPATIBLE_MACHINE_radxarock =3D "radxarock" -COMPATIBLE_MACHINE_firefly-rk3288 =3D "firefly-rk3288" -COMPATIBLE_MACHINE_vyasa-rk3288 =3D "vyasa-rk3288" -COMPATIBLE_MACHINE_tinker-board =3D "tinker-board" -COMPATIBLE_MACHINE_tinker-board-s =3D "tinker-board-s" -COMPATIBLE_MACHINE_rock-pi-4 =3D "rock-pi-4" -COMPATIBLE_MACHINE_nanopi-m4 =3D "nanopi-m4" -COMPATIBLE_MACHINE_nanopi-m4-2gb =3D "nanopi-m4-2gb" diff --git a/recipes-kernel/linux/linux-yocto_%.bbappend b/recipes-kernel= /linux/linux-yocto_%.bbappend deleted file mode 100644 index 7702e3f..0000000 --- a/recipes-kernel/linux/linux-yocto_%.bbappend +++ /dev/null @@ -1,10 +0,0 @@ -COMPATIBLE_MACHINE_marsboard-rk3066 =3D "marsboard-rk3066" -COMPATIBLE_MACHINE_rock2-square =3D "rock2-square" -COMPATIBLE_MACHINE_radxarock =3D "radxarock" -COMPATIBLE_MACHINE_firefly-rk3288 =3D "firefly-rk3288" -COMPATIBLE_MACHINE_vyasa-rk3288 =3D "vyasa-rk3288" -COMPATIBLE_MACHINE_tinker-board =3D "tinker-board" -COMPATIBLE_MACHINE_tinker-board-s =3D "tinker-board-s" -COMPATIBLE_MACHINE_rock-pi-4 =3D "rock-pi-4" -COMPATIBLE_MACHINE_nanopi-m4 =3D "nanopi-m4" -COMPATIBLE_MACHINE_nanopi-m4-2gb =3D "nanopi-m4-2gb" --=20 2.30.2
|
|
|
|
Yocto Project Virtual Summit 2021
Trevor Woerner
The Yocto Project Summit Planning Committee is happy to announce the
upcoming 3rd Yocto Project Summit to take place Tuesday and Wednesday May 25-26 2021, virtually. The 2-day event will run in 2 tracks including a virtual developers meeting, beginner tutorial sessions, hands-on intermediate instruction, lightning talks, regular talks, and social events. The cost for all attendees will be $40USD. The event will run both days from noon until 8pm GMT. Registration is not yet open but will be shortly, please watch for further announcements. The call for papers is now open and will close at 11:59 PM PST on Sunday, April 25, 2021. To submit a proposal please visit: https://pretalx.com/yocto-project-summit-2021/cfp For more information please visit: https://www.yoctoproject.org/yocto-project-virtual-summit-2021/ We look forward to seeing you at the conference!
|
|
|
|
Re: eula-downloads.yoctoproject.org down???
Michael Halstead
I have restored https://eula-downloads.yoctoproject.org/index.php since these connectivity checks rely on it. The driver binaries are not available any longer so I will alter the site to indicate that.
On Tue, Mar 30, 2021 at 1:02 AM Josef Holzmayr <jester@...> wrote: Am Di., 30. März 2021 um 05:22 Uhr schrieb anthony.l via --
Michael Halstead Linux Foundation / Yocto Project Systems Operations Engineer
|
|
|
|
Yocto Project Status WW13`21
Stephen Jolley
Current Dev Position: YP 3.3 M4 (Feature Freeze) Next Deadline: 5th April 2021 YP 3.3 M4 build
Next Team Meetings:
Key Status/Updates:
We are working to identify the load pattern on the infrastructure that seems to trigger these.
Ways to contribute:
YP 3.3 Milestone Dates:
Planned upcoming dot releases:
Tracking Metrics:
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
|
|
|
SDK build artifacts describing software composition
keydi <krzysztof.dudziak@...>
I wonder if all the artifacts described in YP Development Manual, current release, ch. 3.32*
yet only those describing software composition (for purposes of compliance with copyleft software) will change if one builds SDK additionally to target system image. Is it recommended to start analysis of mentioned artifacts not until SDK is built if analysis results have to describe also software composition in SDK; rather doesn't matter? *) Chapter title "Working With Licenses"
|
|
|
|
Re: Get PR value of another recipe
Quentin Schulz
Hi Mauro,
On Tue, Mar 30, 2021 at 02:44:14PM +0200, Mauro Ziliani wrote: Hi all.No. Recipe data is local to the recipe. Cheers, Quentin
|
|
|
|
Get PR value of another recipe
Mauro Ziliani
Hi all. From an image recipe a-image_1.0.bb with IMAGE_INSTALL_append = " a " defined, can I get the PR value of recipe a? a_1.0.bb: PR="r5" a-image_1.0.bb: A_PR_VALUE := " <get PR of >" MZ Sent from Mailspring, the best free email app for work
|
|
|
|
Re: Naming images
Damien LEFEVRE
Thanks Quentin! That's just what I needed. Do you know if there's a variable to control the content of /etc/version? Cheers, -Damien
On Mon, Mar 29, 2021 at 4:14 PM Quentin Schulz <quentin.schulz@...> wrote: Hi Damien,
|
|
|
|
Re: eula-downloads.yoctoproject.org down???
Josef Holzmayr
Am Di., 30. März 2021 um 05:22 Uhr schrieb anthony.l via
lists.yoctoproject.org <anthony.l=axxin.com@...>: Please see https://www.yoctoproject.org/pipermail/poky/2016-January/010357.html If you are experiencing problems, you can override the connectivity check, and then please revisit your versions and/or third party layers. Greetz
|
|
|
|
rohit jadhav
Hi
I was using very old version of Yocto i.e. Krogoth. In that version I am able to use following packages with respective version: Package name Version Cups 2.2.4 Cups-filter 1.14.0 qpdf 6.0.0 Opencv 2.4 It was working fine. But When I switch to any other version of Yocto like Zeus [which I have tried on ]. Specifically for cups-filter pakage observed following errors while compilation and generation of rootfs ERROR: cups-filters-1.14.0-r0 do_compile: oe_runmake failed ERROR: cups-filters-1.14.0-r0 do_compile: Execution of '/home/tel/imx_yocto_bsp_Zeus/Yocto_setup/build_imx6ull/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/cups-filters/1.14.0-r0/temp/run.do_compile.17590' failed with exit code 1: It is observed due to wrong c standard while compilation as some log says as follow: warning: ISO C99 doesn't support unnamed structs/unions [-Wpedantic] warning: ' LPT #' directive output may be truncated writing 6 bytes into a region of size between 1 and 1024 [-Wformat-truncation=] warning: 'strncpy' specified bound 1024 equals destination size [-Wstringop-truncation] filter/pdftoopvp/oprs/OPVPSplash.h:53:3: error: 'GBool' does not name a type Just Need some guideline to resolve this issue. Please also suggest is there any way to use old pakage of Yocto version to latest Yocto version. Thanks and Regards Rohit
|
|
|