Re: [yocto] Opkg cannot find anything to satisfy 'kernel-module-iwlmvm'
If anybody else has the problem of their kernel config being rewritten by the yocto build process when configuring a iwlwifi chip I have the answer. Not the reason, just the answer. On Tue, 14 May 2024 at 14:51, Worik Stanton via lists.yoctoproject.org wrote: > > > On Mon, 13 May 2024 at 19:14, Alexander Kanavin > wrote: > >> You need to look into build logs and build directory for the kernel >> recipe to see what modules are being built and packaged. >> > > Rightio. (I found that the failure is logged in the "do_rootfs" recipe, > but concentrating on the kernel recipe): > > I found a problem, straight away: The kernel recipe includes in its > SRC_URI a file that (looks like) it sets kernel configuration to load the > iwlwifi modules. > However when I build it and boot it and examine /proc/config.gz none of > the configuration from the kernel recipe are there > If anybody cares, the problem with the kernel configuration being rewritten was solved by adding "CONFIG_WLAN_VENDOR_INTEL=y" to the config. On the face of it this makes no sense because this is the documentation from https://www.kernelconfig.io/config_wlan_vendor_intel --- If you have a wireless card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about these cards. If you say Y, you will be asked for your specific card in the following questions. --- Now I am moving on to getting the firmware installed by Yocto. I find if I add the firmware by hand the wireless chip is working well, which ATM it looks as if the opkg error I started with was a red herring. I still have no explanation for it. I am disturbed that the kernel config is getting rewritten, and the answer is a "magic incantation". I am sure there are sensible reasons, and it is not magic. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63104): https://lists.yoctoproject.org/g/yocto/message/63104 Mute This Topic: https://lists.yoctoproject.org/mt/106063799/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Python3 pyee recipe for Kirkstone
That’s normally because there’s a dependency on something like setuptools-scm. Check the pyproject.toml and see what it says it depends on. (Post kirkstone this would error out earlier) Ross From: Gary Huband via Lists.Yoctoproject.Org Sent: Wednesday, May 15, 2024 8:05:46 PM To: Ross Burton ; yocto@lists.yoctoproject.org Subject: Re: [yocto] Python3 pyee recipe for Kirkstone Still no pyee under site-packages and the dist-info dir is UNKNOWN $ tree ./tmp/work/corei7-64-poky-linux/python3-pyee/11.1.0-r0/image/ ./tmp/work/corei7-64-poky-linux/python3-pyee/11.1.0-r0/image/ └── usr └── lib └── python3.10 └── site-packages └── UNKNOWN-0.0.0.dist-info ├── LICENSE ├── METADATA ├── RECORD ├── top_level.txt └── WHEEL -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63103): https://lists.yoctoproject.org/g/yocto/message/63103 Mute This Topic: https://lists.yoctoproject.org/mt/106120050/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Python3 pyee recipe for Kirkstone
Still no pyee under site-packages and the dist-info dir is UNKNOWN > > $ tree ./tmp/work/corei7-64-poky-linux/python3-pyee/11.1.0-r0/image/ > ./tmp/work/corei7-64-poky-linux/python3-pyee/11.1.0-r0/image/ > └── usr > └── lib > └── python3.10 > └── site-packages > └── UNKNOWN-0.0.0.dist-info > ├── LICENSE > ├── METADATA > ├── RECORD > ├── top_level.txt > └── WHEEL -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63102): https://lists.yoctoproject.org/g/yocto/message/63102 Mute This Topic: https://lists.yoctoproject.org/mt/106120050/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Python3 pyee recipe for Kirkstone
On 15 May 2024, at 19:33, Gary Huband via lists.yoctoproject.org
wrote:
>
> I'm trying to create a Python3 recipe for pyee
> https://pypi.org/project/pyee/
> The package has a pyproject.toml but no setup.py.
> The build system section:
> [build-system]
> requires = ["setuptools", "setuptools-scm", "wheel"]
> build-backend = "setuptools.build_meta"
>
> Here's my recipe python3-pyee_11.1.0.bb:
> inherit pypi python_setuptools_build_meta
>
> LICENSE = "MIT"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=b2b1cc8797dff32cec5d783148fceab5"
>
> SRC_URI[md5sum] = "b12a1105a13a218ef0d6b1fa6cb6425a"
> SRC_URI[sha1sum] = "50661cf14bb6e8093ff623856bcdb10400d2ff0b"
> SRC_URI[sha256sum] =
> "b53af98f6990c810edd9b56b87791021a8f54fd13db4edd1142438d44ba2263f"
> SRC_URI[sha384sum] =
> "ff6c091d3a824b164a175fd9996c7e4e859c2a59441df6ea140eafab525656669ee51412508b0f5398027a9404c8e785"
> SRC_URI[sha512sum] =
> "86dd34b6d353be9c01a84cbe7cfbdc70eb8ad75626bfde48d0c7d9b027650df3c51edc8c002b6d011a51868b0ad92b6b44e34618f20861313899221730130f16"
>
> RDEPENDS:${PN} += "python3-typing-extensions"
>
> # pyee uses pyproject.toml instead of setup.py, so need below
You don’t need the below, as kirkstone has python_setuptools_build_meta. Just
delete that and it should work.
Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63101): https://lists.yoctoproject.org/g/yocto/message/63101
Mute This Topic: https://lists.yoctoproject.org/mt/106120050/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] Python3 pyee recipe for Kirkstone
I'm trying to create a Python3 recipe for pyee
https://pypi.org/project/pyee/
The package has a pyproject.toml but no setup.py.
The build system section:
[build-system]
requires = ["setuptools", "setuptools-scm", "wheel"]
build-backend = "setuptools.build_meta"
Here's my recipe python3-pyee_11.1.0.bb:
>
>
>
> inherit pypi python_setuptools_build_meta
>
> LICENSE = "MIT"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=b2b1cc8797dff32cec5d783148fceab5"
>
> SRC_URI[md5sum] = "b12a1105a13a218ef0d6b1fa6cb6425a"
> SRC_URI[sha1sum] = "50661cf14bb6e8093ff623856bcdb10400d2ff0b"
> SRC_URI[sha256sum] =
> "b53af98f6990c810edd9b56b87791021a8f54fd13db4edd1142438d44ba2263f"
> SRC_URI[sha384sum] =
> "ff6c091d3a824b164a175fd9996c7e4e859c2a59441df6ea140eafab525656669ee51412508b0f5398027a9404c8e785"
>
> SRC_URI[sha512sum] =
> "86dd34b6d353be9c01a84cbe7cfbdc70eb8ad75626bfde48d0c7d9b027650df3c51edc8c002b6d011a51868b0ad92b6b44e34618f20861313899221730130f16"
>
>
> RDEPENDS:${PN} += "python3-typing-extensions"
>
> # pyee uses pyproject.toml instead of setup.py, so need below
> do_configure:prepend() {
> cat > ${S}/setup.py <<-EOF
> from setuptools import setup
> from setuptools import find_packages
> setup(
> name="${PYPI_PACKAGE}",
> version="${PV}",
> license="${LICENSE}",
> package_dir={'': 'pyee'},
> packages=find_packages(''),
> python_requires=">=3.8",
> zip_safe=True,
> )
> EOF
> }
>
>
>
> This does not put the package code into site-packages/pyee
> $ tree ./tmp/work/corei7-64-poky-linux/python3-pyee/11.1.0-r0/image/
> ./tmp/work/corei7-64-poky-linux/python3-pyee/11.1.0-r0/image/
> └── usr
> └── lib
> └── python3.10
> └── site-packages
> └── pyee-11.1.0.dist-info
> ├── LICENSE
> ├── METADATA
> ├── RECORD
> ├── top_level.txt
> ├── WHEEL
> └── zip-safe
>
>
Any help is appreciated.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#63100): https://lists.yoctoproject.org/g/yocto/message/63100
Mute This Topic: https://lists.yoctoproject.org/mt/106120050/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] [yocto-autobuilder2] schedulers: update branchdefaults for scarthgap
Signed-off-by: Steve Sakoman -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63097): https://lists.yoctoproject.org/g/yocto/message/63097 Mute This Topic: https://lists.yoctoproject.org/mt/106117557/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] devtool update-recipe/finish fix in scarthgap
On 15 May 2024, at 16:41, Jeff Harris via lists.yoctoproject.org wrote: > > Is the new devtool fix for update-recipe/finish in the master branch slated > for merge into scarthgap as well? Commit > 28516320d81f1767be24fb3226021f16b425d355 fixes a problem that occurs > frequently for our projects which append onto the linux and busybox recipes > and have customized menuconfig fragments. It would be nice to have that fix > to prevent having to fork poky ourselves as it doesn't seem to be fixable in > our own layers. The quickest way for this to happen would be for you to create a series of backports of devtool fixes that you know fix your issue and pass the selftests (oe-selftest -r devtool). Post the patches to the oe-core list with the [scarthgap] tag in the subject and the maintainer can review them. Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63096): https://lists.yoctoproject.org/g/yocto/message/63096 Mute This Topic: https://lists.yoctoproject.org/mt/106116458/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] devtool update-recipe/finish fix in scarthgap
Is the new devtool fix for update-recipe/finish in the master branch slated for merge into scarthgap as well? Commit 28516320d81f1767be24fb3226021f16b425d355 fixes a problem that occurs frequently for our projects which append onto the linux and busybox recipes and have customized menuconfig fragments. It would be nice to have that fix to prevent having to fork poky ourselves as it doesn't seem to be fixable in our own layers. Thanks, Jeff -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63095): https://lists.yoctoproject.org/g/yocto/message/63095 Mute This Topic: https://lists.yoctoproject.org/mt/106116458/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto][linux-yocto v6.1/standard/nxp-sdk-6.1/nxp-soc & v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH] ethosu: Use GFP_ATOMIC instead of GFP_KERNEL
Atomic operations should be employed within rwlock, hence GFP_ATOMIC
is utilized instead of GFP_KERNEL. This ensures the avoidance of the
subsequent call trace and prevents potential misinterpretation of NPU
performance degradation during testing.
BUG: sleeping function called from invalid context at
include/linux/sched/mm.h:274
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 529, name: python3
preempt_count: 1, expected: 0
RCU nest depth: 0, expected: 0
Preemption disabled at:
[] ethosu_rpmsg_register+0x24/0x64
CPU: 1 PID: 529 Comm: python3 Tainted: G C
6.1.90-yocto-standard #1
Hardware name: NXP i.MX93 11X11 EVK board (DT)
Call trace:
dump_backtrace.part.0+0xc8/0xd4
show_stack+0x20/0x30
dump_stack_lvl+0x6c/0x88
dump_stack+0x18/0x34
__might_resched+0x154/0x1c0
__might_sleep+0x54/0xa4
kmem_cache_alloc+0x458/0x630
radix_tree_node_alloc.constprop.0+0x54/0x110
idr_get_free+0x22c/0x2b0
idr_alloc_u32+0x70/0x100
idr_alloc_cyclic+0x6c/0xf0
ethosu_rpmsg_register+0x3c/0x64
ethosu_inference_create+0xc0/0x2a4
ethosu_network_ioctl+0xd4/0x2a0
__arm64_sys_ioctl+0xb4/0x100
Signed-off-by: Xiaolei Wang
---
drivers/staging/ethosu/ethosu_rpmsg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/ethosu/ethosu_rpmsg.c
b/drivers/staging/ethosu/ethosu_rpmsg.c
index d3e597e82762..f2ab3b366de7 100644
--- a/drivers/staging/ethosu/ethosu_rpmsg.c
+++ b/drivers/staging/ethosu/ethosu_rpmsg.c
@@ -36,7 +36,7 @@ int ethosu_rpmsg_register(struct ethosu_rpmsg *erp,
struct ethosu_rpmsg_msg *msg)
{
write_lock(>lock);
- msg->id = idr_alloc_cyclic(>msg_idr, msg, 0, INT_MAX, GFP_KERNEL);
+ msg->id = idr_alloc_cyclic(>msg_idr, msg, 0, INT_MAX, GFP_ATOMIC);
write_unlock(>lock);
if (msg->id < 0)
return msg->id;
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13938):
https://lists.yoctoproject.org/g/linux-yocto/message/13938
Mute This Topic: https://lists.yoctoproject.org/mt/106112654/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[linux-yocto] [kernel-cache][PATCH] features/intel-npu: introduce Intel NPU fragment
Add config fragment for the system with an 14th generation Intel CPU (Meteor Lake) or newer. It will allow users to enable Intel NPU (formerly called Intel VPU) which is a CPU-integrated inference accelerator for Computer Vision and Deep Learning applications. Signed-off-by: Naveen Saini --- features/intel-npu/intel-npu.cfg | 3 +++ features/intel-npu/intel-npu.scc | 4 kern-features.rc | 1 + 3 files changed, 8 insertions(+) create mode 100644 features/intel-npu/intel-npu.cfg create mode 100644 features/intel-npu/intel-npu.scc diff --git a/features/intel-npu/intel-npu.cfg b/features/intel-npu/intel-npu.cfg new file mode 100644 index ..6b7ced30 --- /dev/null +++ b/features/intel-npu/intel-npu.cfg @@ -0,0 +1,3 @@ +# SPDX-License-Identifier: MIT +CONFIG_DRM_ACCEL=y +CONFIG_DRM_ACCEL_IVPU=m diff --git a/features/intel-npu/intel-npu.scc b/features/intel-npu/intel-npu.scc new file mode 100644 index ..782c8499 --- /dev/null +++ b/features/intel-npu/intel-npu.scc @@ -0,0 +1,4 @@ +# SPDX-License-Identifier: MIT +define KFEATURE_DESCRIPTION "Enable Intel NPU for Computer Vision and Deep Learning applications" + +kconf hardware intel-npu.cfg diff --git a/kern-features.rc b/kern-features.rc index 0e83053c..14381cc8 100644 --- a/kern-features.rc +++ b/kern-features.rc @@ -72,6 +72,7 @@ config = features/lxc/lxc-enable.scc config = features/inline/inline.scc config = features/intel-tco/intel-tco.scc + config = features/intel-npu/intel-npu.scc config = features/ftrace/ftrace-function-tracer-disable.scc config = features/ftrace/ftrace.scc config = features/vxlan/vxlan-enable.scc -- 2.37.3 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13937): https://lists.yoctoproject.org/g/linux-yocto/message/13937 Mute This Topic: https://lists.yoctoproject.org/mt/106109710/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
