On 2022-01-20 07:05, mihirdav...@gmail.com wrote:
*recently tried to add ALSA support to core-image-minimal . by adding
following lines into local.conf: MACHINE_FEATURES+="alsa"
DISTRO_FEATURES+="alsa" CORE_IMAGE_EXTRA_INSTALL+="alsa-utils" but got
error of which I have attached image. *
*recently tried to add ALSA support to core-image-minimal . by adding following
lines into local.conf: MACHINE_FEATURES+="alsa" DISTRO_FEATURES+="alsa"
CORE_IMAGE_EXTRA_INSTALL+="alsa-utils" but got error of which I have attached
image.*
please guide me what should I do to solve it.
I’m testing migrating one of my dunfell builds to master in anticipation of the
upcoming LTS, and there is a difference in how packages are populated into
deploy that is causing me problems. My builds use a package feed, and the way
I’ve been generating my package feed is to create a
In message: [linux-yocto] [linux-yocto standard kernel]: nxp-s32g2xx: fix
build warnings of pcie
on 19/01/2022 Zhantao Tang wrote:
> Hi Bruce,
>
> There is a patch for fixing build warnings of pcie of the following branches
>
> v5.10/standard/nxp-sdk-5.10/nxp-s32g2xx
>
merged.
Bruce
In message: [linux-yocto][linux-yocto v5.10/standard/nxp-sdk-5.10/nxp-soc &
v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-soc][PATCH 1/1] dmaengine: imx-sdma:
Fix a build warning in sdma_runtime_resume function
on 19/01/2022 Xiaolei Wang wrote:
> Delete redundant variables 'i' and
In message: [linux-yocto][linux-yocto v5.10] kernel code for marvell octeon
on 19/01/2022 Ruiqiang Hao wrote:
> Hi Bruce,
>
> Please help to merge this patch into our linux-yocto repo.
>
> repo:
> linux-yocto
> branch:
> v5.10/standard/cn-sdkv5.4/octeon
>
Hi JH,
On 1/18/22 5:45 PM, Jupiter wrote:
Hi Rudolf,
Thanks for your response and comments.
If you run ifconfig -a does your WiFi interface show up? If not there is an
issue with the driver. Use dmesg and filter for the driver. Often a driver
cannot load the firmware. What is your WiFi
Hi,
I have tested the state mirror locally with my own http mirror and it works
perfectly.
There are no problems with the concurrent connections.
I'm more sure that the root cause is some bandwidth/connection limitation
on the http YP mirror.
Jose
Michael Opdenacker escreveu no dia sexta,
On Thu, Jan 6, 2022 at 10:22 AM Trevor Gamblin
wrote:
>
> Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage
>
> Attendees: Alexandre, Joshua, Michael, Randy, Richard, Saul, Stephen, Steve,
> Tim, Trevor
>
> ARs:
>
> - Joshua to send a patch limiting the size of diffoscope output for
>
On Wed, 2022-01-19 at 14:59 +0100, Michael Opdenacker wrote:
> Peter, Ross
>
> On 1/19/22 1:56 PM, Peter Bergin wrote:
> > Hi,
> >
> > On 2022-01-19 13:16, Michael Opdenacker wrote:
> > > Greetings,
> > >
> > > I reused a simple "hello" recipe and added a non-matching checksum to
> > > it:
> >
From: Eilís Ní Fhlannagáin
This commit just adds some documentation on how to use the machine
generation recipe.
Signed-off-by: Eilís Ní Fhlannagáin
---
README.txt | 16
1 file changed, 16 insertions(+)
diff --git a/README.txt b/README.txt
index f3dda51..ec860fd 100644
---
From: Eilís Ní Fhlannagáin
This commit removes the need for calling out ZEPHYR_MODULES via
MACHINEOVERRIDES. It uses west list to figure out what ZEPHYR_MODULES
are available and attaches them to -DZEPHYR_MODULES. Additional out of
tree modules may be added via ZEPHYR_EXTRA_MODULES.
From: Eilís Ní Fhlannagáin
Some of these recipes ended up overriding the ZEPHYR_MODULES we set
elsewhere. As well, zephyr-lvgl tries to apply a patch we already apply.
Signed-off-by: Eilís Ní Fhlannagáin
---
.../zephyr-kernel/zephyr-coap-client.bb | 2 --
From: Eilís Ní Fhlannagáin
This commit restructures meta-zephyr into meta-zephyr-core and
meta-zephyr-bsp. It moves machine definitions into meta-zephyr-bsp
in preparation for adding the autogenerated zephyr machines.
Signed-off-by: Eilís Ní Fhlannagáin
---
README.txt
From: Eilís Ní Fhlannagáin
Trying to handwrite all the machine defintions in zephyr would be an
enormous task. This commit creates a patch to zephy which abuses cmake
to output machine definitions for OE.
Not all machines can be generated this way and meta will need to be in
COREBASE/meta. It's
From: Eilís Ní Fhlannagáin
This set of patches relates to what I discussed at
https://lists.yoctoproject.org/g/yocto/message/55285.
Four major issues (and one minor issue)are dealt with in this series. The first
is a logical split of the
meta-zephyr layer into a machine BSP layer and a
From: Eilís Ní Fhlannagáin
We will need west for a few things.
First, west knows about all the boards supported, so for automatic
machine generation, we will need to be able to run west boards.
Secondly, I want to get rid of the dependance on MACHINEOVERRIDES in
machine definition files. One
From: Eilís Ní Fhlannagáin
Currently meta-zephyr only checks out a subset of the kernel source.
With the addition of being able to generate machine configs from
zephyr source, we need to be able to have the complete source if we
don't want things to break badly.
Signed-off-by: Eilís Ní
From: Eilís Ní Fhlannagáin
fd8bf397792d58280928d23686313a8da810485a should have also applied the
dtc.patch to the 2.6.1 kernel. This commits applies it, so both 2.7.1
and 2.6.1 work.
Signed-off-by: Eilís Ní Fhlannagáin
---
.../recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.1.inc | 1 +
Peter, Ross
On 1/19/22 1:56 PM, Peter Bergin wrote:
> Hi,
>
> On 2022-01-19 13:16, Michael Opdenacker wrote:
>> Greetings,
>>
>> I reused a simple "hello" recipe and added a non-matching checksum to
>> it:
>>
>> ...
>> SRC_URI = "file://helloworld.c"
>> SRC_URI[md5sum] =
This patch is to fix the following warnings:
1. warning: 's32gen1_pcie_config_irq' defined but not used
2. warning: 's32gen1_pcie_msi_handler' defined but not used
The functions are introduced in commit aefb6f1e55ad("s32gen1: Add
initial PCIe support (RC/EP)"), and the issues caused by commit
Hi Bruce,
There is a patch for fixing build warnings of pcie of the following branches
v5.10/standard/nxp-sdk-5.10/nxp-s32g2xx
v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-s32g2xx
Would you please help to merge the patch?
Thanks,
Zhantao
-=-=-=-=-=-=-=-=-=-=-=-
Links: You
Hi,
On 2022-01-19 13:16, Michael Opdenacker wrote:
Greetings,
I reused a simple "hello" recipe and added a non-matching checksum to it:
...
SRC_URI = "file://helloworld.c"
SRC_URI[md5sum] = "34f0efd76b4f188833cdd129"
...
The rest of the recipe comes from
On Wed, 19 Jan 2022 at 12:16, Michael Opdenacker
wrote:
>
> Greetings,
>
> I reused a simple "hello" recipe and added a non-matching checksum to it:
>
> ...
> SRC_URI = "file://helloworld.c"
> SRC_URI[md5sum] = "34f0efd76b4f188833cdd129"
> ...
>
> The rest of the recipe comes from
>
Greetings,
I reused a simple "hello" recipe and added a non-matching checksum to it:
...
SRC_URI = "file://helloworld.c"
SRC_URI[md5sum] = "34f0efd76b4f188833cdd129"
...
The rest of the recipe comes from
Hi Tomasz,
Thanks for your response.
> Are you using custom Linux kernel / custom device tree? Maybe there is
> some issue there?
Yes, but the Zeus build image uses the same device tree that could run
WiFi connection without any issues, I am comparing the same source and
configuration between
26 matches
Mail list logo
