date:20220919

[linux-yocto][linux-yocto v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc & v5.15/standard/nxp-sdk-5.15/nxp-soc][PATCH] usb: dwc3: fix a build error redefinition of 'dwc3_xhci_plat_priv'

2022-09-19 Thread Xiaolei Wang

Fix commit 3b6411d24f39 merge conflict, delete redundant
dwc3_xhci_plat_priv.

Signed-off-by: Xiaolei Wang 
---
 drivers/usb/dwc3/host.c | 4 
 1 file changed, 4 deletions(-)

diff --git a/drivers/usb/dwc3/host.c b/drivers/usb/dwc3/host.c
index a1f3f04e48aa..5cd2de3b1b8e 100644
--- a/drivers/usb/dwc3/host.c
+++ b/drivers/usb/dwc3/host.c
@@ -57,10 +57,6 @@ static void dwc3_power_off_all_roothub_ports(struct dwc3 
*dwc)
dev_err(dwc->dev, "xhci base reg invalid\n");
 }
 
-static const struct xhci_plat_priv dwc3_xhci_plat_priv = {
-   .quirks = XHCI_SKIP_PHY_INIT,
-};
-
 static int dwc3_host_get_irq(struct dwc3 *dwc)
 {
struct platform_device  *dwc3_pdev = to_platform_device(dwc->dev);
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11687): 
https://lists.yoctoproject.org/g/linux-yocto/message/11687
Mute This Topic: https://lists.yoctoproject.org/mt/93797761/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [PATCH] bsp/marvell-cn106xx: add initial support

2022-09-19 Thread Ruiqiang Hao

From: Ruiqiang Hao 

Add support for marvell-cn106xx bsp with standard and preempt-rt
kernel.

Signed-off-by: Ruiqiang Hao 
---
 .../marvell-cn106xx-preempt-rt.scc|   7 +
 .../marvell-cn106xx-standard.scc  |   8 +
 bsp/marvell-cn106xx/marvell-cn106xx.cfg   | 152 ++
 bsp/marvell-cn106xx/marvell-cn106xx.scc   |   9 ++
 4 files changed, 176 insertions(+)
 create mode 100644 bsp/marvell-cn106xx/marvell-cn106xx-preempt-rt.scc
 create mode 100644 bsp/marvell-cn106xx/marvell-cn106xx-standard.scc
 create mode 100644 bsp/marvell-cn106xx/marvell-cn106xx.cfg
 create mode 100644 bsp/marvell-cn106xx/marvell-cn106xx.scc

diff --git a/bsp/marvell-cn106xx/marvell-cn106xx-preempt-rt.scc 
b/bsp/marvell-cn106xx/marvell-cn106xx-preempt-rt.scc
new file mode 100644
index ..8733cbad
--- /dev/null
+++ b/bsp/marvell-cn106xx/marvell-cn106xx-preempt-rt.scc
@@ -0,0 +1,7 @@
+define KMACHINE marvell-cn106xx
+define KTYPE preempt-rt
+define KARCH arm64
+
+include ktypes/preempt-rt
+
+include marvell-cn106xx.scc
diff --git a/bsp/marvell-cn106xx/marvell-cn106xx-standard.scc 
b/bsp/marvell-cn106xx/marvell-cn106xx-standard.scc
new file mode 100644
index ..037540b1
--- /dev/null
+++ b/bsp/marvell-cn106xx/marvell-cn106xx-standard.scc
@@ -0,0 +1,8 @@
+# SPDX-License-Identifier: MIT
+define KMACHINE marvell-cn106xx
+define KTYPE standard
+define KARCH arm64
+
+include ktypes/standard
+
+include marvell-cn106xx.scc
diff --git a/bsp/marvell-cn106xx/marvell-cn106xx.cfg 
b/bsp/marvell-cn106xx/marvell-cn106xx.cfg
new file mode 100644
index ..87791f2c
--- /dev/null
+++ b/bsp/marvell-cn106xx/marvell-cn106xx.cfg
@@ -0,0 +1,152 @@
+# SPDX-License-Identifier: MIT
+..
+.WARNING
+.
+. This file is a kernel configuration fragment, and not a full kernel
+. configuration file.  The final kernel configuration is made up of
+. an assembly of processed fragments, each of which is designed to
+. capture a specific part of the final configuration (e.g. platform
+. configuration, feature configuration, and board specific hardware
+. configuration).  For more information on kernel configuration, please
+. consult the product documentation.
+.
+..
+
+CONFIG_ARM64=y
+CONFIG_ARM64_VA_BITS_48=y
+CONFIG_ARM64_64K_PAGES=y
+CONFIG_ARM_SMMU_V3=y
+CONFIG_NR_CPUS=24
+CONFIG_ARCH_THUNDER=y
+
+# Since we use the 64K pages, so we have to enable this for the multilib 
support
+CONFIG_EXPERT=y
+
+# PCIe
+CONFIG_PCI=y
+CONFIG_PCIEPORTBUS=y
+CONFIG_HOTPLUG_PCI=y
+CONFIG_HOTPLUG_PCI_PCIE=y
+CONFIG_PCI_IOV=y
+CONFIG_PCI_HOST_GENERIC=y
+
+# Ethernet
+CONFIG_OCTEONTX2_AF=y
+CONFIG_OCTEONTX2_PF=y
+CONFIG_OCTEONTX2_VF=y
+CONFIG_CAVIUM_PTP=y
+CONFIG_PTP_1588_CLOCK=y
+
+# DMA
+CONFIG_OCTEONTX2_DPI_PF=y
+
+# MTD
+CONFIG_MTD=y
+CONFIG_MTD_SPI_NOR=y
+CONFIG_MTD_BLOCK=y
+
+# USB
+CONFIG_USB=y
+CONFIG_USB_XHCI_HCD=y
+
+# SPI
+CONFIG_SPI=y
+CONFIG_SPI_CADENCE_XSPI=y
+
+# I2C
+CONFIG_I2C=y
+CONFIG_I2C_THUNDERX=y
+
+# Serial
+CONFIG_SERIAL_AMBA_PL011=y
+CONFIG_SERIAL_AMBA_PL011_CONSOLE=y
+
+# Watchdog
+CONFIG_ARM_SBSA_WATCHDOG=y
+
+# SD
+CONFIG_MMC=y
+CONFIG_MMC_CAVIUM_THUNDERX=y
+CONFIG_MMC_SDHCI=y
+CONFIG_MMC_SDHCI_PLTFM=y
+CONFIG_MMC_SDHCI_CADENCE=y
+
+# GPIO
+CONFIG_GPIOLIB=y
+CONFIG_GPIO_THUNDERX=y
+
+# HWMON
+CONFIG_SENSORS_MAX6697=y
+CONFIG_SENSORS_JC42=y
+CONFIG_SENSORS_ARM_SCMI=y
+
+# RTC
+CONFIG_RTC_CLASS=y
+
+# PM
+CONFIG_ARM_SCMI_POWER_DOMAIN=y
+CONFIG_RTC_DRV_DS1307=y
+
+# Regulator
+CONFIG_REGULATOR=y
+CONFIG_REGULATOR_FIXED_VOLTAGE=y
+CONFIG_REGULATOR_GPIO=y
+
+# VFIO
+CONFIG_VFIO=y
+CONFIG_VFIO_PCI=y
+CONFIG_VFIO_NOIOMMU=y
+
+# Misc
+CONFIG_EEPROM_AT24=y
+CONFIG_HW_RANDOM=y
+CONFIG_HW_RANDOM_CAVIUM=y
+CONFIG_HW_RANDOM_CN10K=y
+CONFIG_OCTEONTX_INFO=y
+CONFIG_OCTEONTX2_RM=y
+CONFIG_OCTEONTX2_RM_DOM_SYSFS=y
+
+# BPHY
+CONFIG_MARVELL_OTX_BPHY_CTR=y
+
+# Mailbox
+CONFIG_MAILBOX=y
+CONFIG_MVL_MHU=y
+
+# SCMI
+CONFIG_ARM_SCMI_PROTOCOL=y
+
+# CLK
+CONFIG_COMMON_CLK_SCMI=y
+
+# CPU freq
+CONFIG_CPU_FREQ=y
+CONFIG_ARM_SCMI_CPUFREQ=y
+
+# CRYPT
+CONFIG_CRYPTO_DEV_OCTEONTX2_CPT=y
+
+# NPA
+CONFIG_OCTEONTX2_NPA_PF=y
+
+# FWLOG
+CONFIG_MARVELL_CN10K_FWLOG=y
+
+# CORESIGHT
+CONFIG_CORESIGHT=y
+CONFIG_CORESIGHT_LINKS_AND_SINKS=y
+CONFIG_CORESIGHT_LINK_AND_SINK_TMC=y
+CONFIG_CORESIGHT_CATU=y
+CONFIG_CORESIGHT_SINK_TPIU=y
+CONFIG_CORESIGHT_SINK_ETBV10=y
+CONFIG_CORESIGHT_SOURCE_ETM4X=y
+CONFIG_CORESIGHT_CPU_DEBUG=y
+CONFIG_CORESIGHT_CTI=y
+CONFIG_CORESIGHT_CTI_INTEGRATION_REGS=y
+
+# MARVELL_UB
+CONFIG_MARVELL_UB=y
+CONFIG_MARVELL_UB_GEN_DRIVER=y
+
+# AVS_RESET
+CONFIG_MARVELL_AVS_RESET=y
diff --git a/bsp/marvell-cn106xx/marvell-cn106xx.scc 
b/bsp/marvell-cn106xx/marvell-cn106xx.scc
new file mode 100644
index ..a809af52
--- /dev/null
+++ b/bsp/marvell-cn106xx/marvell-cn106xx.scc
@@ -0,0 +1,9 @@
+# SPDX-License-Identifier: MIT
+kconf hardware

[linux-yocto][yocto-kernel-cache v5.15] Add kernel-cache for marvell cn106xx

2022-09-19 Thread Ruiqiang Hao

Hi Bruce,

   Please help to merge this patch into our linux-yocto repo.

repo:
yocto-kernel-cache
branch:
yocto-5.15

Thanks,
Ruiqiang

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11685): 
https://lists.yoctoproject.org/g/linux-yocto/message/11685
Mute This Topic: https://lists.yoctoproject.org/mt/93796818/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [yocto-kernel-cache yocto-5.15]: nxp-s32g: add BRIDGE config as built-in

2022-09-19 Thread Zhantao Tang


Hi Bruce,

There is an patch of yocto-kernel-cache to update kernel configs for nxp-s32g 
bsp,
Would you please help to merge this patch into yocto-kernel-cache, branch 
yocto-5.15?


Thanks,
Zhantao

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11683): 
https://lists.yoctoproject.org/g/linux-yocto/message/11683
Mute This Topic: https://lists.yoctoproject.org/mt/93796435/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [PATCH] nxp-s32g: add BRIDGE config as built-in

2022-09-19 Thread Zhantao Tang

This patch is to fix the following build warning:

  WARNING: linux-yocto-rt-5.15.59+gitAUTOINC+358077fbd3_ee7baf33b6-r0
do_kernel_configcheck: [kernel config]: specified values did not
make it into the kernel's final configuration:

[NOTE]: 'CONFIG_NET_DSA' last val (y) and .config val (m) do not match

Because CONFIG_NET_DSA (S32G sja1105 switch driver needs this config)
depends on CONFIG_BRIDGE, which is a module by default in rt kernel.

Acctually, The CONFIG_BRIDGE has been set to 'y' in bridge.scc. But in
preempt-rt.scc, the bridge.scc is included before the preempt-rt.cfg.
There may be some side effects if we shuffle the include of the bridge.scc
and preempt-rt.cfg. So set CONFIG_BRIDGE to 'y' in nxp-s32g.cfg explicitly,
to fix the issue.

Signed-off-by: Zhantao Tang 
---
 bsp/nxp-s32g/nxp-s32g.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/nxp-s32g/nxp-s32g.cfg b/bsp/nxp-s32g/nxp-s32g.cfg
index f583d4d4..2c47ac49 100644
--- a/bsp/nxp-s32g/nxp-s32g.cfg
+++ b/bsp/nxp-s32g/nxp-s32g.cfg
@@ -41,6 +41,7 @@ CONFIG_STMMAC_ETH=y
 CONFIG_AT803X_PHY=y
 CONFIG_MICREL_PHY=y
 CONFIG_AQUANTIA_PHY=y
+CONFIG_BRIDGE=y
 CONFIG_NET_DSA=y
 CONFIG_NET_DSA_TAG_SJA1105=y
 CONFIG_NET_DSA_SJA1105=y
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11684): 
https://lists.yoctoproject.org/g/linux-yocto/message/11684
Mute This Topic: https://lists.yoctoproject.org/mt/93796436/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [PATCH] arm64: cpu_errata: fix unpaired brances

2022-09-19 Thread Ruiqiang Hao

From: Ruiqiang Hao 

commit 3f42e5879d35(Merge branch 'v5.15/standard/base' into 
v5.15/standard/cn-sdkv5.4/octeon)
introduces unpaired brances, will cause build issue below, complete brace to 
fix this.

arch/arm64/kernel/cpu_errata.c:766:17: error: field name not in record or union 
initializer
   766 | .desc = "ARM erratum 2457168",
   | ^
arch/arm64/kernel/cpu_errata.c:766:17: note: (near initialization for 
'arm64_errata[24].match_list')
arch/arm64/kernel/cpu_errata.c:766:25: error: initialization of 'const struct 
arm64_cpu_capabilities *' from incompatible pointer type 'char *' 
[-Werror=incompatible-pointer-types]
   766 | .desc = "ARM erratum 2457168",
   | ^
arch/arm64/kernel/cpu_errata.c:766:25: note: (near initialization for 
'arm64_errata[24].match_list')
arch/arm64/kernel/cpu_errata.c:767:17: error: field name not in record or union 
initializer
   767 | .capability = ARM64_WORKAROUND_2457168,
   | ^

Signed-off-by: Ruiqiang Hao 
---
 arch/arm64/kernel/cpu_errata.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm64/kernel/cpu_errata.c b/arch/arm64/kernel/cpu_errata.c
index c0807e3af045..2776b404c1a5 100644
--- a/arch/arm64/kernel/cpu_errata.c
+++ b/arch/arm64/kernel/cpu_errata.c
@@ -761,6 +761,8 @@ const struct arm64_cpu_capabilities arm64_errata[] = {
.desc = "MARVELL erratum 38627",
.capability = ARM64_WORKAROUND_MRVL_38627,
ERRATA_MIDR_RANGE_LIST(marvell_erratum_38627_cpus),
+   },
+#endif
 #ifdef CONFIG_ARM64_ERRATUM_2457168
{
.desc = "ARM erratum 2457168",
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11682): 
https://lists.yoctoproject.org/g/linux-yocto/message/11682
Mute This Topic: https://lists.yoctoproject.org/mt/93796261/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][linux-yocto v5.15] fix unpaired brances for marvell cn96xx

2022-09-19 Thread Ruiqiang Hao

Hi Bruce,

Please help to merge this patch into our linux-yocto repo.

repo:
linux-yocto
branch:
v5.15/standard/cn-sdkv5.4/octeon
v5.15/standard/preempt-rt/cn-sdkv5.4/octeon

Thanks,
Ruiqiang

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11681): 
https://lists.yoctoproject.org/g/linux-yocto/message/11681
Mute This Topic: https://lists.yoctoproject.org/mt/93796260/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] M+ & H bugs with Milestone Movements WW38

2022-09-19 Thread Stephen Jolley

All,

YP M+ or high bugs which moved to a new milestone in WW38 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  6428

Improve the ability to isolate changes that have caused a rebuild

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.2 M1


 

  10061

Ctrl+C during BB_HASHCHECK_FUNCTION execution does not interrupt processing 
nicely

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  12290

cross recipe kernel module dependency generation stopped working

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  12342

lib32-core-image-sato -ctestimage failed due to wrong package names

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  12760

CMake Toolchain File Has Wrong Module Path

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  13004

Automate yocto-check-layer -m option

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  13181

persist_data sqlite database mixed with forking is irreparably broken

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.2 M1


 

  13279

Make sure users/groups exist for package_write_* tasks

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  13285

YoctoProject Compatibility script improvements needed

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  13311

xargs: fdleak.c:396: complain_about_leaky_fds: Assertion `no_leaks' failed.

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  13338

SDK  build fails if image contains bash

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  13424

devupstream doesn't work with mutilib

richard.pur...@linuxfoundation.org

richard.pur...@linuxfoundation.org

4.1 M3

4.1 M4


 

  13599

Enhancement: Detect variables that shouldn't be defined in image scope, but in 
global (distro) scope

richard.pur...@linuxfoundation.org

richard.pur...@linuxfoundation.org

4.1 M3

4.1 M4


 

  13735

Performing Automated Runtime Testing with a custom hardware target / BeagleBone 
Hardware target

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.2 M1


 

  13868

Python cache files get lost in packages

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  13889

python3 Windows distutils stubs regressed in upgrade to 3.8.2

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  13897

POSTINST_INTERCEPTS_DIR broken by undocumented POSTINST_INTERCEPTS_PATHS since 
thud

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  13954

Invalid layerindex data causing backtrace in `bitbake-layers layerindex-fetch`

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  14066

bitbake core-image-base -c populate_sdk fails when image contains bash, 
core-utils and package_deb is used

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  14098

absolute path in TEMPLATECONF should be rejected or warned, makes ext-sdk 
uninstallable

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  14118

systemd services not enabled when using package feed

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.2 M1


 

  14127

cve-check falsely indicates a vulnerabily to be patched

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.1 M2

4.1 M4


 

  14136

If u-boot defconfig is incomplete, 'bitbake u-boot -c configure' hangs and eats 
all

[yocto] Enhancements/Bugs closed WW38!

2022-09-19 Thread Stephen Jolley

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


randy.macl...@windriver.com

1


sundeep.kokko...@gmail.com

1


jon.ma...@arm.com

1


Grand Total

3

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58084): https://lists.yoctoproject.org/g/yocto/message/58084
Mute This Topic: https://lists.yoctoproject.org/mt/93792062/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 4.1

2022-09-19 Thread Stephen Jolley

All,

Below is the list as of top 35 bug owners as of the end of WW38 of who have
open medium or higher bugs and enhancements against YP 4.1.   There are 28
possible work days left until the final release candidates for YP 4.1 needs
to be released.


Who

Count


michael.opdenac...@bootlin.com

37


david.re...@windriver.com

23


bruce.ashfi...@gmail.com

22


ross.bur...@arm.com

19


randy.macl...@windriver.com

16


richard.pur...@linuxfoundation.org

13


sakib.sa...@windriver.com

11


jpewhac...@gmail.com

9


saul.w...@windriver.com

8


aryaman.gu...@windriver.com

6


pa...@zhukoff.net

5


sundeep.kokko...@gmail.com

4


tim.orl...@konsulko.com

4


jon.ma...@arm.com

3


pgowda@gmail.com

3


akuster...@gmail.com

3


mhalst...@linuxfoundation.org

2


hongxu@windriver.com

2


raj.k...@gmail.com

2


qi.c...@windriver.com

2


s...@bigsur.com

2


tvgamb...@gmail.com

2


martin.ja...@gmail.com

1


aeh...@gmail.com

1


open.sou...@oleksandr-kravchuk.com

1


mostthings...@gmail.com

1


ptsne...@gmail.com

1


ola.x.nils...@axis.com

1


martin.bee...@online.de

1


nicolas.deche...@linaro.org

1


thomas.per...@bootlin.com

1


shac...@vdoo.com

1


beh...@converseincode.com

1


alexandre.bell...@bootlin.com

1


alejan...@enedino.org

1


Grand Total

211

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58083): https://lists.yoctoproject.org/g/yocto/message/58083
Mute This Topic: https://lists.yoctoproject.org/mt/93792022/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2022-09-19 Thread Stephen Jolley

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 410
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now,  "4.1", "4.2", "4.3", "4.99" and "Future", the more
pressing/urgent issues being in "4.1" and then "4.2".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58082): https://lists.yoctoproject.org/g/yocto/message/58082
Mute This Topic: https://lists.yoctoproject.org/mt/93792006/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] #yocto #dunfell

2022-09-19 Thread Monsees, Steven C (US) via lists.yoctoproject.org


I am seeing an error when I attempt to apply a patch, and could use some 
clarification or way to resolve...

Am doing something wrong in patch creation ?
What is meant by :  "Patch console.patch does not apply (enforce with -f)" ?
How can I best resolve this issue ?

I edited a file in the recipe's git repo in order to create the patch for the 
change:

git diff -u console.c

which I used as my patch:

diff --git a/lib/console.c b/lib/console.c
index 9c10560..b932a44 100644
--- a/lib/console.c
+++ b/lib/console.c
@@ -357,7 +357,7 @@ static struct {
{  EFI_SECURITY_VIOLATION, L"Security Violation"},
// warnings
-   {  EFI_WARN_UNKOWN_GLYPH,  L"Warning Unknown Glyph"},
+   {  EFI_WARN_UNKNOWN_GLYPH, L"Warning Unknown Glyph"},
{  EFI_WARN_DELETE_FAILURE,L"Warning Delete Failure"},
{  EFI_WARN_WRITE_FAILURE, L"Warning Write Failure"},
{  EFI_WARN_BUFFER_TOO_SMALL,  L"Warning Buffer Too Small"},

I am getting the following error when the patch is applied:

ERROR: efitools-native-1.7.0+gitAUTOINC+0649468475-r0 do_patch: Applying patch 
'console.patch' on target directory 
'/disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/builds/sbca-default/tmp/work/x86_64-linux/efitools-native/1.7.0+gitAUTOINC+0649468475-r0/git'
Command Error: 'quilt --quiltrc 
/disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/builds/sbca-default/tmp/work/x86_64-linux/efitools-native/1.7.0+gitAUTOINC+0649468475-r0/recipe-sysroot-native/etc/quiltrc
 push' exited with 0  Output:
Applying patch console.patch
patching file lib/console.c
Hunk #1 FAILED at 357.
1 out of 1 hunk FAILED -- rejects in file lib/console.c
Patch console.patch does not apply (enforce with -f)
ERROR: Logfile of failure stored in: 
/disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/builds/sbca-default/tmp/work/x86_64-linux/efitools-native/1.7.0+gitAUTOINC+0649468475-r0/temp/log.do_patch.7615
ERROR: Task 
(/disk0/scratch/yocto/workspace/poky-dunfell-23.0.19/meta-bae/meta-limws/meta-intel/meta-sbca/recipes-bsp/efitools/efitools-native_git.bb:do_patch)
 failed with exit code '1'

Thanks,
Steve

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58081): https://lists.yoctoproject.org/g/yocto/message/58081
Mute This Topic: https://lists.yoctoproject.org/mt/93787499/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Mute #dunfell:https://lists.yoctoproject.org/g/yocto/mutehashtag/dunfell
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Adding Vulkan to core-image-weston

2022-09-19 Thread Markus Volk

Am Mo, 19. Sep 2022 um 16:54:52 + schrieb Edgar Mobile 
:

This wasn't enough


i guess you would also need to add venus support to virglrenderer.bb 
for qemu:


DEPENDS:append = "vulkan-loader vulkan-headers"
EXTRA_OEMESON += "-Dvenus-experimental=true"

but i have never tested this


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58080): https://lists.yoctoproject.org/g/yocto/message/58080
Mute This Topic: https://lists.yoctoproject.org/mt/93720286/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Adding Vulkan to core-image-weston

2022-09-19 Thread Edgar Mobile

My current configuration is

DISTRO_FEATURES:append = "opengl x11 vulkan"

This wasn't enough for libvulkan.so.* to be installed or vulkaninfo to work. 
Only the simple weston egl examples work.

I also tried adding virtio-experimental to VULKAN_DRIVERS in mesa.inc, didn't 
help either.


From: Markus Volk 
Sent: Monday, September 19, 2022 4:37 PM
To: Alexander Kanavin 
Cc: Edgar Mobile ; yocto@lists.yoctoproject.org 

Subject: Re: [yocto] Adding Vulkan to core-image-weston

Am Mo, 19. Sep 2022 um 16:33:11 +0100 schrieb Alexander Kanavin 
:
You need to check the Mesa recipe to see how the build options are defined

mesa builds vulkan support, if you add 'vulkan' to DISTRO_FEATURES. If you need 
to, you can add additional drivers with a line like this to a mesa_%.bbappend:

VULKAN_DRIVERS:append = ",foo,bar"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58079): https://lists.yoctoproject.org/g/yocto/message/58079
Mute This Topic: https://lists.yoctoproject.org/mt/93720286/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Adding Vulkan to core-image-weston

2022-09-19 Thread Markus Volk

Am Mo, 19. Sep 2022 um 16:33:11 +0100 schrieb Alexander Kanavin 
:
You need to check the Mesa recipe to see how the build options are 
defined


mesa builds vulkan support, if you add 'vulkan' to DISTRO_FEATURES. If 
you need to, you can add additional drivers with a line like this to a 
mesa_%.bbappend:


VULKAN_DRIVERS:append = ",foo,bar"


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58078): https://lists.yoctoproject.org/g/yocto/message/58078
Mute This Topic: https://lists.yoctoproject.org/mt/93720286/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Adding Vulkan to core-image-weston

2022-09-19 Thread Alexander Kanavin

You need to check the Mesa recipe to see how the build options are defined,
and add swrast to the list of vulkan drivers if necessary. Meson_options
only defines available options in Mesa, not the actual set used in yocto.

Alex

On Mon 19. Sep 2022 at 15.40, Edgar Mobile  wrote:

> Is editing meson_options.txt the recommended way to customize Mesa in
> Yocto?
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Monday, September 19, 2022 2:36 PM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> You do, yes. It’s not qemu, it’s in Mesa. You can see the options here:
> https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/meson_options.txt
>
>
> Alex
>
> On Mon 19. Sep 2022 at 15.30, Edgar Mobile  wrote:
>
> What are the qemu params to activate swrast vulkan driver? And do I still
> need mesa vulkan package? meson logs show it wasnt't compiled with
> vulkan-drivers.
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Monday, September 19, 2022 2:20 PM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> I think swrast Vulkan driver may be a better option to start with. At
> least that is contained entirely in qemu guest so you won’t have to wrestle
> with pass through code paths to the host which are all experimental. It’s
> entirely uncharted waters for me as well.
>
> Alex
>
> On Mon 19. Sep 2022 at 14.52, Edgar Mobile  wrote:
>
> For the time being I use vulkan-tools so I get vulkaninfo. It fails
> apparently due to no appropriate driver available.
> I think adding virtio-experimental to mesa may be necessary, right? Or is
> there another core recipse that will add mesa vulkan drivers?
>
> Regards
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Monday, September 19, 2022 1:31 PM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> As I said you need to inspect the working directory of the recipe to find
> out what goes where.
>
>
> Alex
>
> On Mon 19. Sep 2022 at 13.28, Edgar Mobile  wrote:
>
> I have the impression that the only binary vulkan-samples installs is
> /usr/bin/spirv-cross . Are there other packages that install more samples?
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Monday, September 19, 2022 8:25 AM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> I suppose you need to look at compile and install logs for vulkan-samples.
> And how the installed items get split into packages. I’m short, inspect
> ${WORKDIR} for it.
>
> Alex
>
> On Mon 19. Sep 2022 at 9.36, Edgar Mobile  wrote:
>
> Greetings,
>
> I see the libvulkan.so.* libs now, but I don't see any sample binaries
> that look like Vulkan. Is there a list somewhere for all the files in
> vulkan-samples?
> Regards
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Saturday, September 17, 2022 8:28 AM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> If the samples don't link with libvulkan directly, it won't get pulled
> into the images. How are they loading that library, is it via dlopen()
> somewhere? Invisible dlopen() dependencies typically need to be listed
> explicitly in RDEPENDS.
>
> As a quick fix, you can add vulkan-loader to the same
> CORE_IMAGE_EXTRA_INSTALL list.
>
> Alex
>
> On Fri, 16 Sept 2022 at 19:17, Edgar Mobile  wrote:
> >
> > Ok, so I switched to Kirkstone and added vulkan-samples to
> CORE_IMAGE_EXTRA_INSTALL.
> > But no libvulkan.so in /usr/lib.
> >
> > Am I missing something?
> >
> > 
> > From: Alexander Kanavin 
> > Sent: Friday, September 16, 2022 12:14 PM
> > To: Edgar Mobile 
> > Cc: yocto@lists.yoctoproject.org 
> > Subject: Re: [yocto] Adding Vulkan to core-image-weston
> >
> > You can start by adding vulkan-samples to the image - the recipe is in
> > core. We do not test vulkan in qemu, because the software vulkan
> > rendering is still under active development, and marked as
> > experimental in virglrenderer.
> >
> > It may help if you use qemux86_64 and kvm for it, because software
> > graphical paths are too slow without it generally.
> >
> > Alex
> >
> > On Fri, 16 Sept 2022 at 13:43, Edgar Mobile 
> wrote:
> > >
> > > Greetings,
> > >
> > > I'd like to test graphics rendering with Vulkan on an Aarch64 Yocto
> honister (qemu, host is x64). Can you tell me which parameters I need to
> add to local.conf to get all libs and headers installed (plus maybe some
> useful tools and demo if present)?
> > >
> > > Regards
> > >
> > > 
> > >
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58077):

Re: [yocto] Adding Vulkan to core-image-weston

2022-09-19 Thread Edgar Mobile

Is editing meson_options.txt the recommended way to customize Mesa in Yocto?

From: Alexander Kanavin 
Sent: Monday, September 19, 2022 2:36 PM
To: Edgar Mobile 
Cc: yocto@lists.yoctoproject.org 
Subject: Re: [yocto] Adding Vulkan to core-image-weston

You do, yes. It’s not qemu, it’s in Mesa. You can see the options here:
https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/meson_options.txt

Alex

On Mon 19. Sep 2022 at 15.30, Edgar Mobile 
mailto:heide...@hotmail.com>> wrote:
What are the qemu params to activate swrast vulkan driver? And do I still need 
mesa vulkan package? meson logs show it wasnt't compiled with vulkan-drivers.

From: Alexander Kanavin mailto:alex.kana...@gmail.com>>
Sent: Monday, September 19, 2022 2:20 PM

To: Edgar Mobile mailto:heide...@hotmail.com>>
Cc: yocto@lists.yoctoproject.org 
mailto:yocto@lists.yoctoproject.org>>
Subject: Re: [yocto] Adding Vulkan to core-image-weston

I think swrast Vulkan driver may be a better option to start with. At least 
that is contained entirely in qemu guest so you won’t have to wrestle with pass 
through code paths to the host which are all experimental. It’s entirely 
uncharted waters for me as well.

Alex

On Mon 19. Sep 2022 at 14.52, Edgar Mobile 
mailto:heide...@hotmail.com>> wrote:
For the time being I use vulkan-tools so I get vulkaninfo. It fails apparently 
due to no appropriate driver available.
I think adding virtio-experimental to mesa may be necessary, right? Or is there 
another core recipse that will add mesa vulkan drivers?

Regards

From: Alexander Kanavin mailto:alex.kana...@gmail.com>>
Sent: Monday, September 19, 2022 1:31 PM

To: Edgar Mobile mailto:heide...@hotmail.com>>
Cc: yocto@lists.yoctoproject.org 
mailto:yocto@lists.yoctoproject.org>>
Subject: Re: [yocto] Adding Vulkan to core-image-weston

As I said you need to inspect the working directory of the recipe to find out 
what goes where.

Alex

On Mon 19. Sep 2022 at 13.28, Edgar Mobile 
mailto:heide...@hotmail.com>> wrote:
I have the impression that the only binary vulkan-samples installs is 
/usr/bin/spirv-cross . Are there other packages that install more samples?

From: Alexander Kanavin mailto:alex.kana...@gmail.com>>
Sent: Monday, September 19, 2022 8:25 AM

To: Edgar Mobile mailto:heide...@hotmail.com>>
Cc: yocto@lists.yoctoproject.org 
mailto:yocto@lists.yoctoproject.org>>
Subject: Re: [yocto] Adding Vulkan to core-image-weston

I suppose you need to look at compile and install logs for vulkan-samples. And 
how the installed items get split into packages. I’m short, inspect ${WORKDIR} 
for it.

Alex

On Mon 19. Sep 2022 at 9.36, Edgar Mobile 
mailto:heide...@hotmail.com>> wrote:
Greetings,

I see the libvulkan.so.* libs now, but I don't see any sample binaries that 
look like Vulkan. Is there a list somewhere for all the files in vulkan-samples?
Regards

From: Alexander Kanavin mailto:alex.kana...@gmail.com>>
Sent: Saturday, September 17, 2022 8:28 AM

To: Edgar Mobile mailto:heide...@hotmail.com>>
Cc: yocto@lists.yoctoproject.org 
mailto:yocto@lists.yoctoproject.org>>
Subject: Re: [yocto] Adding Vulkan to core-image-weston

If the samples don't link with libvulkan directly, it won't get pulled
into the images. How are they loading that library, is it via dlopen()
somewhere? Invisible dlopen() dependencies typically need to be listed
explicitly in RDEPENDS.

As a quick fix, you can add vulkan-loader to the same
CORE_IMAGE_EXTRA_INSTALL list.

Alex

On Fri, 16 Sept 2022 at 19:17, Edgar Mobile 
mailto:heide...@hotmail.com>> wrote:
>
> Ok, so I switched to Kirkstone and added vulkan-samples to 
> CORE_IMAGE_EXTRA_INSTALL.
> But no libvulkan.so in /usr/lib.
>
> Am I missing something?
>
> 
> From: Alexander Kanavin 
> mailto:alex.kana...@gmail.com>>
> Sent: Friday, September 16, 2022 12:14 PM
> To: Edgar Mobile mailto:heide...@hotmail.com>>
> Cc: yocto@lists.yoctoproject.org 
> mailto:yocto@lists.yoctoproject.org>>
> Subject: Re: [yocto] Adding Vulkan to core-image-weston
>
> You can start by adding vulkan-samples to the image - the recipe is in
> core. We do not test vulkan in qemu, because the software vulkan
> rendering is still under active development, and marked as
> experimental in virglrenderer.
>
> It may help if you use qemux86_64 and kvm for it, because software
> graphical paths are too slow without it generally.
>
> Alex
>
> On Fri, 16 Sept 2022 at 13:43, Edgar Mobile 
> mailto:heide...@hotmail.com>> wrote:
> >
> > Greetings,
> >
> > I'd like to test graphics rendering with Vulkan on an Aarch64 Yocto 
> > honister (qemu, host is x64). Can you tell me which parameters I need

Re: [yocto] Adding Vulkan to core-image-weston

2022-09-19 Thread Alexander Kanavin

You do, yes. It’s not qemu, it’s in Mesa. You can see the options here:
https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/meson_options.txt


Alex

On Mon 19. Sep 2022 at 15.30, Edgar Mobile  wrote:

> What are the qemu params to activate swrast vulkan driver? And do I still
> need mesa vulkan package? meson logs show it wasnt't compiled with
> vulkan-drivers.
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Monday, September 19, 2022 2:20 PM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> I think swrast Vulkan driver may be a better option to start with. At
> least that is contained entirely in qemu guest so you won’t have to wrestle
> with pass through code paths to the host which are all experimental. It’s
> entirely uncharted waters for me as well.
>
> Alex
>
> On Mon 19. Sep 2022 at 14.52, Edgar Mobile  wrote:
>
> For the time being I use vulkan-tools so I get vulkaninfo. It fails
> apparently due to no appropriate driver available.
> I think adding virtio-experimental to mesa may be necessary, right? Or is
> there another core recipse that will add mesa vulkan drivers?
>
> Regards
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Monday, September 19, 2022 1:31 PM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> As I said you need to inspect the working directory of the recipe to find
> out what goes where.
>
>
> Alex
>
> On Mon 19. Sep 2022 at 13.28, Edgar Mobile  wrote:
>
> I have the impression that the only binary vulkan-samples installs is
> /usr/bin/spirv-cross . Are there other packages that install more samples?
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Monday, September 19, 2022 8:25 AM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> I suppose you need to look at compile and install logs for vulkan-samples.
> And how the installed items get split into packages. I’m short, inspect
> ${WORKDIR} for it.
>
> Alex
>
> On Mon 19. Sep 2022 at 9.36, Edgar Mobile  wrote:
>
> Greetings,
>
> I see the libvulkan.so.* libs now, but I don't see any sample binaries
> that look like Vulkan. Is there a list somewhere for all the files in
> vulkan-samples?
> Regards
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Saturday, September 17, 2022 8:28 AM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> If the samples don't link with libvulkan directly, it won't get pulled
> into the images. How are they loading that library, is it via dlopen()
> somewhere? Invisible dlopen() dependencies typically need to be listed
> explicitly in RDEPENDS.
>
> As a quick fix, you can add vulkan-loader to the same
> CORE_IMAGE_EXTRA_INSTALL list.
>
> Alex
>
> On Fri, 16 Sept 2022 at 19:17, Edgar Mobile  wrote:
> >
> > Ok, so I switched to Kirkstone and added vulkan-samples to
> CORE_IMAGE_EXTRA_INSTALL.
> > But no libvulkan.so in /usr/lib.
> >
> > Am I missing something?
> >
> > 
> > From: Alexander Kanavin 
> > Sent: Friday, September 16, 2022 12:14 PM
> > To: Edgar Mobile 
> > Cc: yocto@lists.yoctoproject.org 
> > Subject: Re: [yocto] Adding Vulkan to core-image-weston
> >
> > You can start by adding vulkan-samples to the image - the recipe is in
> > core. We do not test vulkan in qemu, because the software vulkan
> > rendering is still under active development, and marked as
> > experimental in virglrenderer.
> >
> > It may help if you use qemux86_64 and kvm for it, because software
> > graphical paths are too slow without it generally.
> >
> > Alex
> >
> > On Fri, 16 Sept 2022 at 13:43, Edgar Mobile 
> wrote:
> > >
> > > Greetings,
> > >
> > > I'd like to test graphics rendering with Vulkan on an Aarch64 Yocto
> honister (qemu, host is x64). Can you tell me which parameters I need to
> add to local.conf to get all libs and headers installed (plus maybe some
> useful tools and demo if present)?
> > >
> > > Regards
> > >
> > > 
> > >
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58075): https://lists.yoctoproject.org/g/yocto/message/58075
Mute This Topic: https://lists.yoctoproject.org/mt/93720286/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Adding Vulkan to core-image-weston

2022-09-19 Thread Edgar Mobile

What are the qemu params to activate swrast vulkan driver? And do I still need 
mesa vulkan package? meson logs show it wasnt't compiled with vulkan-drivers.

From: Alexander Kanavin 
Sent: Monday, September 19, 2022 2:20 PM
To: Edgar Mobile 
Cc: yocto@lists.yoctoproject.org 
Subject: Re: [yocto] Adding Vulkan to core-image-weston

I think swrast Vulkan driver may be a better option to start with. At least 
that is contained entirely in qemu guest so you won’t have to wrestle with pass 
through code paths to the host which are all experimental. It’s entirely 
uncharted waters for me as well.

Alex

On Mon 19. Sep 2022 at 14.52, Edgar Mobile 
mailto:heide...@hotmail.com>> wrote:
For the time being I use vulkan-tools so I get vulkaninfo. It fails apparently 
due to no appropriate driver available.
I think adding virtio-experimental to mesa may be necessary, right? Or is there 
another core recipse that will add mesa vulkan drivers?

Regards

From: Alexander Kanavin mailto:alex.kana...@gmail.com>>
Sent: Monday, September 19, 2022 1:31 PM

To: Edgar Mobile mailto:heide...@hotmail.com>>
Cc: yocto@lists.yoctoproject.org 
mailto:yocto@lists.yoctoproject.org>>
Subject: Re: [yocto] Adding Vulkan to core-image-weston

As I said you need to inspect the working directory of the recipe to find out 
what goes where.

Alex

On Mon 19. Sep 2022 at 13.28, Edgar Mobile 
mailto:heide...@hotmail.com>> wrote:
I have the impression that the only binary vulkan-samples installs is 
/usr/bin/spirv-cross . Are there other packages that install more samples?

From: Alexander Kanavin mailto:alex.kana...@gmail.com>>
Sent: Monday, September 19, 2022 8:25 AM

To: Edgar Mobile mailto:heide...@hotmail.com>>
Cc: yocto@lists.yoctoproject.org 
mailto:yocto@lists.yoctoproject.org>>
Subject: Re: [yocto] Adding Vulkan to core-image-weston

I suppose you need to look at compile and install logs for vulkan-samples. And 
how the installed items get split into packages. I’m short, inspect ${WORKDIR} 
for it.

Alex

On Mon 19. Sep 2022 at 9.36, Edgar Mobile 
mailto:heide...@hotmail.com>> wrote:
Greetings,

I see the libvulkan.so.* libs now, but I don't see any sample binaries that 
look like Vulkan. Is there a list somewhere for all the files in vulkan-samples?
Regards

From: Alexander Kanavin mailto:alex.kana...@gmail.com>>
Sent: Saturday, September 17, 2022 8:28 AM

To: Edgar Mobile mailto:heide...@hotmail.com>>
Cc: yocto@lists.yoctoproject.org 
mailto:yocto@lists.yoctoproject.org>>
Subject: Re: [yocto] Adding Vulkan to core-image-weston

If the samples don't link with libvulkan directly, it won't get pulled
into the images. How are they loading that library, is it via dlopen()
somewhere? Invisible dlopen() dependencies typically need to be listed
explicitly in RDEPENDS.

As a quick fix, you can add vulkan-loader to the same
CORE_IMAGE_EXTRA_INSTALL list.

Alex

On Fri, 16 Sept 2022 at 19:17, Edgar Mobile 
mailto:heide...@hotmail.com>> wrote:
>
> Ok, so I switched to Kirkstone and added vulkan-samples to 
> CORE_IMAGE_EXTRA_INSTALL.
> But no libvulkan.so in /usr/lib.
>
> Am I missing something?
>
> 
> From: Alexander Kanavin 
> mailto:alex.kana...@gmail.com>>
> Sent: Friday, September 16, 2022 12:14 PM
> To: Edgar Mobile mailto:heide...@hotmail.com>>
> Cc: yocto@lists.yoctoproject.org 
> mailto:yocto@lists.yoctoproject.org>>
> Subject: Re: [yocto] Adding Vulkan to core-image-weston
>
> You can start by adding vulkan-samples to the image - the recipe is in
> core. We do not test vulkan in qemu, because the software vulkan
> rendering is still under active development, and marked as
> experimental in virglrenderer.
>
> It may help if you use qemux86_64 and kvm for it, because software
> graphical paths are too slow without it generally.
>
> Alex
>
> On Fri, 16 Sept 2022 at 13:43, Edgar Mobile 
> mailto:heide...@hotmail.com>> wrote:
> >
> > Greetings,
> >
> > I'd like to test graphics rendering with Vulkan on an Aarch64 Yocto 
> > honister (qemu, host is x64). Can you tell me which parameters I need to 
> > add to local.conf to get all libs and headers installed (plus maybe some 
> > useful tools and demo if present)?
> >
> > Regards
> >
> > 
> >

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58074): https://lists.yoctoproject.org/g/yocto/message/58074
Mute This Topic: https://lists.yoctoproject.org/mt/93720286/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Adding Vulkan to core-image-weston

2022-09-19 Thread Alexander Kanavin

I think swrast Vulkan driver may be a better option to start with. At least
that is contained entirely in qemu guest so you won’t have to wrestle with
pass through code paths to the host which are all experimental. It’s
entirely uncharted waters for me as well.

Alex

On Mon 19. Sep 2022 at 14.52, Edgar Mobile  wrote:

> For the time being I use vulkan-tools so I get vulkaninfo. It fails
> apparently due to no appropriate driver available.
> I think adding virtio-experimental to mesa may be necessary, right? Or is
> there another core recipse that will add mesa vulkan drivers?
>
> Regards
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Monday, September 19, 2022 1:31 PM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> As I said you need to inspect the working directory of the recipe to find
> out what goes where.
>
>
> Alex
>
> On Mon 19. Sep 2022 at 13.28, Edgar Mobile  wrote:
>
> I have the impression that the only binary vulkan-samples installs is
> /usr/bin/spirv-cross . Are there other packages that install more samples?
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Monday, September 19, 2022 8:25 AM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> I suppose you need to look at compile and install logs for vulkan-samples.
> And how the installed items get split into packages. I’m short, inspect
> ${WORKDIR} for it.
>
> Alex
>
> On Mon 19. Sep 2022 at 9.36, Edgar Mobile  wrote:
>
> Greetings,
>
> I see the libvulkan.so.* libs now, but I don't see any sample binaries
> that look like Vulkan. Is there a list somewhere for all the files in
> vulkan-samples?
> Regards
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Saturday, September 17, 2022 8:28 AM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> If the samples don't link with libvulkan directly, it won't get pulled
> into the images. How are they loading that library, is it via dlopen()
> somewhere? Invisible dlopen() dependencies typically need to be listed
> explicitly in RDEPENDS.
>
> As a quick fix, you can add vulkan-loader to the same
> CORE_IMAGE_EXTRA_INSTALL list.
>
> Alex
>
> On Fri, 16 Sept 2022 at 19:17, Edgar Mobile  wrote:
> >
> > Ok, so I switched to Kirkstone and added vulkan-samples to
> CORE_IMAGE_EXTRA_INSTALL.
> > But no libvulkan.so in /usr/lib.
> >
> > Am I missing something?
> >
> > 
> > From: Alexander Kanavin 
> > Sent: Friday, September 16, 2022 12:14 PM
> > To: Edgar Mobile 
> > Cc: yocto@lists.yoctoproject.org 
> > Subject: Re: [yocto] Adding Vulkan to core-image-weston
> >
> > You can start by adding vulkan-samples to the image - the recipe is in
> > core. We do not test vulkan in qemu, because the software vulkan
> > rendering is still under active development, and marked as
> > experimental in virglrenderer.
> >
> > It may help if you use qemux86_64 and kvm for it, because software
> > graphical paths are too slow without it generally.
> >
> > Alex
> >
> > On Fri, 16 Sept 2022 at 13:43, Edgar Mobile 
> wrote:
> > >
> > > Greetings,
> > >
> > > I'd like to test graphics rendering with Vulkan on an Aarch64 Yocto
> honister (qemu, host is x64). Can you tell me which parameters I need to
> add to local.conf to get all libs and headers installed (plus maybe some
> useful tools and demo if present)?
> > >
> > > Regards
> > >
> > > 
> > >
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58073): https://lists.yoctoproject.org/g/yocto/message/58073
Mute This Topic: https://lists.yoctoproject.org/mt/93720286/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Adding Vulkan to core-image-weston

2022-09-19 Thread Edgar Mobile

For the time being I use vulkan-tools so I get vulkaninfo. It fails apparently 
due to no appropriate driver available.
I think adding virtio-experimental to mesa may be necessary, right? Or is there 
another core recipse that will add mesa vulkan drivers?

Regards

From: Alexander Kanavin 
Sent: Monday, September 19, 2022 1:31 PM
To: Edgar Mobile 
Cc: yocto@lists.yoctoproject.org 
Subject: Re: [yocto] Adding Vulkan to core-image-weston

As I said you need to inspect the working directory of the recipe to find out 
what goes where.

Alex

On Mon 19. Sep 2022 at 13.28, Edgar Mobile 
mailto:heide...@hotmail.com>> wrote:
I have the impression that the only binary vulkan-samples installs is 
/usr/bin/spirv-cross . Are there other packages that install more samples?

From: Alexander Kanavin mailto:alex.kana...@gmail.com>>
Sent: Monday, September 19, 2022 8:25 AM

To: Edgar Mobile mailto:heide...@hotmail.com>>
Cc: yocto@lists.yoctoproject.org 
mailto:yocto@lists.yoctoproject.org>>
Subject: Re: [yocto] Adding Vulkan to core-image-weston

I suppose you need to look at compile and install logs for vulkan-samples. And 
how the installed items get split into packages. I’m short, inspect ${WORKDIR} 
for it.

Alex

On Mon 19. Sep 2022 at 9.36, Edgar Mobile 
mailto:heide...@hotmail.com>> wrote:
Greetings,

I see the libvulkan.so.* libs now, but I don't see any sample binaries that 
look like Vulkan. Is there a list somewhere for all the files in vulkan-samples?
Regards

From: Alexander Kanavin mailto:alex.kana...@gmail.com>>
Sent: Saturday, September 17, 2022 8:28 AM

To: Edgar Mobile mailto:heide...@hotmail.com>>
Cc: yocto@lists.yoctoproject.org 
mailto:yocto@lists.yoctoproject.org>>
Subject: Re: [yocto] Adding Vulkan to core-image-weston

If the samples don't link with libvulkan directly, it won't get pulled
into the images. How are they loading that library, is it via dlopen()
somewhere? Invisible dlopen() dependencies typically need to be listed
explicitly in RDEPENDS.

As a quick fix, you can add vulkan-loader to the same
CORE_IMAGE_EXTRA_INSTALL list.

Alex

On Fri, 16 Sept 2022 at 19:17, Edgar Mobile 
mailto:heide...@hotmail.com>> wrote:
>
> Ok, so I switched to Kirkstone and added vulkan-samples to 
> CORE_IMAGE_EXTRA_INSTALL.
> But no libvulkan.so in /usr/lib.
>
> Am I missing something?
>
> 
> From: Alexander Kanavin 
> mailto:alex.kana...@gmail.com>>
> Sent: Friday, September 16, 2022 12:14 PM
> To: Edgar Mobile mailto:heide...@hotmail.com>>
> Cc: yocto@lists.yoctoproject.org 
> mailto:yocto@lists.yoctoproject.org>>
> Subject: Re: [yocto] Adding Vulkan to core-image-weston
>
> You can start by adding vulkan-samples to the image - the recipe is in
> core. We do not test vulkan in qemu, because the software vulkan
> rendering is still under active development, and marked as
> experimental in virglrenderer.
>
> It may help if you use qemux86_64 and kvm for it, because software
> graphical paths are too slow without it generally.
>
> Alex
>
> On Fri, 16 Sept 2022 at 13:43, Edgar Mobile 
> mailto:heide...@hotmail.com>> wrote:
> >
> > Greetings,
> >
> > I'd like to test graphics rendering with Vulkan on an Aarch64 Yocto 
> > honister (qemu, host is x64). Can you tell me which parameters I need to 
> > add to local.conf to get all libs and headers installed (plus maybe some 
> > useful tools and demo if present)?
> >
> > Regards
> >
> > 
> >

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58072): https://lists.yoctoproject.org/g/yocto/message/58072
Mute This Topic: https://lists.yoctoproject.org/mt/93720286/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Adding Vulkan to core-image-weston

2022-09-19 Thread Alexander Kanavin

As I said you need to inspect the working directory of the recipe to find
out what goes where.


Alex

On Mon 19. Sep 2022 at 13.28, Edgar Mobile  wrote:

> I have the impression that the only binary vulkan-samples installs is
> /usr/bin/spirv-cross . Are there other packages that install more samples?
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Monday, September 19, 2022 8:25 AM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> I suppose you need to look at compile and install logs for vulkan-samples.
> And how the installed items get split into packages. I’m short, inspect
> ${WORKDIR} for it.
>
> Alex
>
> On Mon 19. Sep 2022 at 9.36, Edgar Mobile  wrote:
>
> Greetings,
>
> I see the libvulkan.so.* libs now, but I don't see any sample binaries
> that look like Vulkan. Is there a list somewhere for all the files in
> vulkan-samples?
> Regards
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Saturday, September 17, 2022 8:28 AM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> If the samples don't link with libvulkan directly, it won't get pulled
> into the images. How are they loading that library, is it via dlopen()
> somewhere? Invisible dlopen() dependencies typically need to be listed
> explicitly in RDEPENDS.
>
> As a quick fix, you can add vulkan-loader to the same
> CORE_IMAGE_EXTRA_INSTALL list.
>
> Alex
>
> On Fri, 16 Sept 2022 at 19:17, Edgar Mobile  wrote:
> >
> > Ok, so I switched to Kirkstone and added vulkan-samples to
> CORE_IMAGE_EXTRA_INSTALL.
> > But no libvulkan.so in /usr/lib.
> >
> > Am I missing something?
> >
> > 
> > From: Alexander Kanavin 
> > Sent: Friday, September 16, 2022 12:14 PM
> > To: Edgar Mobile 
> > Cc: yocto@lists.yoctoproject.org 
> > Subject: Re: [yocto] Adding Vulkan to core-image-weston
> >
> > You can start by adding vulkan-samples to the image - the recipe is in
> > core. We do not test vulkan in qemu, because the software vulkan
> > rendering is still under active development, and marked as
> > experimental in virglrenderer.
> >
> > It may help if you use qemux86_64 and kvm for it, because software
> > graphical paths are too slow without it generally.
> >
> > Alex
> >
> > On Fri, 16 Sept 2022 at 13:43, Edgar Mobile 
> wrote:
> > >
> > > Greetings,
> > >
> > > I'd like to test graphics rendering with Vulkan on an Aarch64 Yocto
> honister (qemu, host is x64). Can you tell me which parameters I need to
> add to local.conf to get all libs and headers installed (plus maybe some
> useful tools and demo if present)?
> > >
> > > Regards
> > >
> > > 
> > >
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58071): https://lists.yoctoproject.org/g/yocto/message/58071
Mute This Topic: https://lists.yoctoproject.org/mt/93720286/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Adding Vulkan to core-image-weston

2022-09-19 Thread Edgar Mobile

I have the impression that the only binary vulkan-samples installs is 
/usr/bin/spirv-cross . Are there other packages that install more samples?


From: Alexander Kanavin 
Sent: Monday, September 19, 2022 8:25 AM
To: Edgar Mobile 
Cc: yocto@lists.yoctoproject.org 
Subject: Re: [yocto] Adding Vulkan to core-image-weston

I suppose you need to look at compile and install logs for vulkan-samples. And 
how the installed items get split into packages. I’m short, inspect ${WORKDIR} 
for it.

Alex

On Mon 19. Sep 2022 at 9.36, Edgar Mobile 
mailto:heide...@hotmail.com>> wrote:
Greetings,

I see the libvulkan.so.* libs now, but I don't see any sample binaries that 
look like Vulkan. Is there a list somewhere for all the files in vulkan-samples?
Regards


From: Alexander Kanavin mailto:alex.kana...@gmail.com>>
Sent: Saturday, September 17, 2022 8:28 AM

To: Edgar Mobile mailto:heide...@hotmail.com>>
Cc: yocto@lists.yoctoproject.org 
mailto:yocto@lists.yoctoproject.org>>
Subject: Re: [yocto] Adding Vulkan to core-image-weston

If the samples don't link with libvulkan directly, it won't get pulled
into the images. How are they loading that library, is it via dlopen()
somewhere? Invisible dlopen() dependencies typically need to be listed
explicitly in RDEPENDS.

As a quick fix, you can add vulkan-loader to the same
CORE_IMAGE_EXTRA_INSTALL list.

Alex

On Fri, 16 Sept 2022 at 19:17, Edgar Mobile 
mailto:heide...@hotmail.com>> wrote:
>
> Ok, so I switched to Kirkstone and added vulkan-samples to 
> CORE_IMAGE_EXTRA_INSTALL.
> But no libvulkan.so in /usr/lib.
>
> Am I missing something?
>
> 
> From: Alexander Kanavin 
> mailto:alex.kana...@gmail.com>>
> Sent: Friday, September 16, 2022 12:14 PM
> To: Edgar Mobile mailto:heide...@hotmail.com>>
> Cc: yocto@lists.yoctoproject.org 
> mailto:yocto@lists.yoctoproject.org>>
> Subject: Re: [yocto] Adding Vulkan to core-image-weston
>
> You can start by adding vulkan-samples to the image - the recipe is in
> core. We do not test vulkan in qemu, because the software vulkan
> rendering is still under active development, and marked as
> experimental in virglrenderer.
>
> It may help if you use qemux86_64 and kvm for it, because software
> graphical paths are too slow without it generally.
>
> Alex
>
> On Fri, 16 Sept 2022 at 13:43, Edgar Mobile 
> mailto:heide...@hotmail.com>> wrote:
> >
> > Greetings,
> >
> > I'd like to test graphics rendering with Vulkan on an Aarch64 Yocto 
> > honister (qemu, host is x64). Can you tell me which parameters I need to 
> > add to local.conf to get all libs and headers installed (plus maybe some 
> > useful tools and demo if present)?
> >
> > Regards
> >
> > 
> >

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58070): https://lists.yoctoproject.org/g/yocto/message/58070
Mute This Topic: https://lists.yoctoproject.org/mt/93720286/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Adding Vulkan to core-image-weston

2022-09-19 Thread Alexander Kanavin

I suppose you need to look at compile and install logs for vulkan-samples.
And how the installed items get split into packages. I’m short, inspect
${WORKDIR} for it.

Alex

On Mon 19. Sep 2022 at 9.36, Edgar Mobile  wrote:

> Greetings,
>
> I see the libvulkan.so.* libs now, but I don't see any sample binaries
> that look like Vulkan. Is there a list somewhere for all the files in
> vulkan-samples?
> Regards
>
> --
> *From:* Alexander Kanavin 
> *Sent:* Saturday, September 17, 2022 8:28 AM
>
> *To:* Edgar Mobile 
> *Cc:* yocto@lists.yoctoproject.org 
> *Subject:* Re: [yocto] Adding Vulkan to core-image-weston
>
> If the samples don't link with libvulkan directly, it won't get pulled
> into the images. How are they loading that library, is it via dlopen()
> somewhere? Invisible dlopen() dependencies typically need to be listed
> explicitly in RDEPENDS.
>
> As a quick fix, you can add vulkan-loader to the same
> CORE_IMAGE_EXTRA_INSTALL list.
>
> Alex
>
> On Fri, 16 Sept 2022 at 19:17, Edgar Mobile  wrote:
> >
> > Ok, so I switched to Kirkstone and added vulkan-samples to
> CORE_IMAGE_EXTRA_INSTALL.
> > But no libvulkan.so in /usr/lib.
> >
> > Am I missing something?
> >
> > 
> > From: Alexander Kanavin 
> > Sent: Friday, September 16, 2022 12:14 PM
> > To: Edgar Mobile 
> > Cc: yocto@lists.yoctoproject.org 
> > Subject: Re: [yocto] Adding Vulkan to core-image-weston
> >
> > You can start by adding vulkan-samples to the image - the recipe is in
> > core. We do not test vulkan in qemu, because the software vulkan
> > rendering is still under active development, and marked as
> > experimental in virglrenderer.
> >
> > It may help if you use qemux86_64 and kvm for it, because software
> > graphical paths are too slow without it generally.
> >
> > Alex
> >
> > On Fri, 16 Sept 2022 at 13:43, Edgar Mobile 
> wrote:
> > >
> > > Greetings,
> > >
> > > I'd like to test graphics rendering with Vulkan on an Aarch64 Yocto
> honister (qemu, host is x64). Can you tell me which parameters I need to
> add to local.conf to get all libs and headers installed (plus maybe some
> useful tools and demo if present)?
> > >
> > > Regards
> > >
> > > 
> > >
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58069): https://lists.yoctoproject.org/g/yocto/message/58069
Mute This Topic: https://lists.yoctoproject.org/mt/93720286/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Problem with make: *** No targets specified and no makefile found.

2022-09-19 Thread Quentin Schulz via lists.yoctoproject.org


Hi Kuzemko Aleksandr,

On 9/17/22 19:19, Kuzemko Aleksandr wrote:

I am trying adapt fbi recipe. 
(https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Kuzma30_meta-2Dmyconf_blob_main_recipes-2Dcore_fbi_fbi-5F1.31.bb=DwIFaQ=_sEr5x9kUWhuk4_nFwjJtA=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t=gnSpmPTreYq9mxX4ptMTWTg0gTJw7RWcUWX8gKmcw8S8xDyWysHjWlYvrelWOfuf=js1u3ARo14dxKOe3T2TO2ZX6O_y6RGMtZ8eDqYtxUm4=
 )
When I run bitbake fbi I get

NOTE: Executing Tasks
ERROR: fbi-1.31-r0 do_compile: oe_runmake failed
ERROR: fbi-1.31-r0 do_compile: 
ExecutionError('/home/qtembed/b2qt/build-raspberrypi4-64/tmp/work/cortexa72-poky-linux/fbi/1.31-r0/temp/run.do_compile.4355',
 1, None, None)
ERROR: Logfile of failure stored in: 
/home/qtembed/b2qt/build-raspberrypi4-64/tmp/work/cortexa72-poky-linux/fbi/1.31-r0/temp/log.do_compile.4355
Log data follows:
| DEBUG: Executing python function autotools_aclocals
| DEBUG: SITE files ['endian-little', 'bit-64', 'arm-common', 'arm-64', 
'common-linux', 'common-glibc', 'aarch64-linux', 'common']
| DEBUG: Python function autotools_aclocals finished
| DEBUG: Executing shell function do_compile
| NOTE: make
| make: *** No targets specified and no makefile found.  Stop.
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
ERROR: Task 
(/home/qtembed/b2qt/sources/meta-myconfig/recipes-core/fbi/fbi_1.31.bb:do_compile)
 failed with exit code '1'
NOTE: Tasks Summary: Attempted 769 tasks of which 768 didn't need to be rerun 
and 1 failed.

I see empty 
home/qtembed/b2qt/build-raspberrypi4-64/tmp/work/cortexa72-poky-linux/fbi/1.31-r0/build
 directory. In 
home/qtembed/b2qt/build-raspberrypi4-64/tmp/work/cortexa72-poky-linux/fbi/1.31-r0/fbi-1.31
 I see extracted source code.
As I understand this error make is running in empty build dir, not in source.
How to fix this?



Maybe this has a broken autotools script, can you try to inherit 
autotools-brokensep instead of autotools?


c.f. https://docs.yoctoproject.org/ref-manual/classes.html#autotools-bbclass

Cheers,
Quentin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58068): https://lists.yoctoproject.org/g/yocto/message/58068
Mute This Topic: https://lists.yoctoproject.org/mt/93747035/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Adding Vulkan to core-image-weston

2022-09-19 Thread Edgar Mobile

Greetings,

I see the libvulkan.so.* libs now, but I don't see any sample binaries that 
look like Vulkan. Is there a list somewhere for all the files in vulkan-samples?
Regards


From: Alexander Kanavin 
Sent: Saturday, September 17, 2022 8:28 AM
To: Edgar Mobile 
Cc: yocto@lists.yoctoproject.org 
Subject: Re: [yocto] Adding Vulkan to core-image-weston

If the samples don't link with libvulkan directly, it won't get pulled
into the images. How are they loading that library, is it via dlopen()
somewhere? Invisible dlopen() dependencies typically need to be listed
explicitly in RDEPENDS.

As a quick fix, you can add vulkan-loader to the same
CORE_IMAGE_EXTRA_INSTALL list.

Alex

On Fri, 16 Sept 2022 at 19:17, Edgar Mobile  wrote:
>
> Ok, so I switched to Kirkstone and added vulkan-samples to 
> CORE_IMAGE_EXTRA_INSTALL.
> But no libvulkan.so in /usr/lib.
>
> Am I missing something?
>
> 
> From: Alexander Kanavin 
> Sent: Friday, September 16, 2022 12:14 PM
> To: Edgar Mobile 
> Cc: yocto@lists.yoctoproject.org 
> Subject: Re: [yocto] Adding Vulkan to core-image-weston
>
> You can start by adding vulkan-samples to the image - the recipe is in
> core. We do not test vulkan in qemu, because the software vulkan
> rendering is still under active development, and marked as
> experimental in virglrenderer.
>
> It may help if you use qemux86_64 and kvm for it, because software
> graphical paths are too slow without it generally.
>
> Alex
>
> On Fri, 16 Sept 2022 at 13:43, Edgar Mobile  wrote:
> >
> > Greetings,
> >
> > I'd like to test graphics rendering with Vulkan on an Aarch64 Yocto 
> > honister (qemu, host is x64). Can you tell me which parameters I need to 
> > add to local.conf to get all libs and headers installed (plus maybe some 
> > useful tools and demo if present)?
> >
> > Regards
> >
> > 
> >

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58067): https://lists.yoctoproject.org/g/yocto/message/58067
Mute This Topic: https://lists.yoctoproject.org/mt/93720286/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][linux-yocto v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc & v5.15/standard/nxp-sdk-5.15/nxp-soc][PATCH] usb: dwc3: fix a build error redefinition of 'dwc3_xhci_plat_priv'

[linux-yocto] [PATCH] bsp/marvell-cn106xx: add initial support

[linux-yocto][yocto-kernel-cache v5.15] Add kernel-cache for marvell cn106xx

[linux-yocto] [yocto-kernel-cache yocto-5.15]: nxp-s32g: add BRIDGE config as built-in

[linux-yocto] [PATCH] nxp-s32g: add BRIDGE config as built-in

[linux-yocto] [PATCH] arm64: cpu_errata: fix unpaired brances

[linux-yocto][linux-yocto v5.15] fix unpaired brances for marvell cn96xx

[yocto] M+ & H bugs with Milestone Movements WW38

[yocto] Enhancements/Bugs closed WW38!

[yocto] Current high bug count owners for Yocto Project 4.1

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[yocto] #yocto #dunfell

Re: [yocto] Adding Vulkan to core-image-weston

Re: [yocto] Adding Vulkan to core-image-weston

Re: [yocto] Adding Vulkan to core-image-weston

Re: [yocto] Adding Vulkan to core-image-weston

Re: [yocto] Adding Vulkan to core-image-weston

Re: [yocto] Adding Vulkan to core-image-weston

Re: [yocto] Adding Vulkan to core-image-weston

Re: [yocto] Adding Vulkan to core-image-weston

Re: [yocto] Adding Vulkan to core-image-weston

Re: [yocto] Adding Vulkan to core-image-weston

Re: [yocto] Adding Vulkan to core-image-weston

Re: [yocto] Adding Vulkan to core-image-weston

Re: [yocto] Problem with make: *** No targets specified and no makefile found.

Re: [yocto] Adding Vulkan to core-image-weston

26 matches

Site Navigation

Mail list logo

Footer information