On Wed, Dec 8, 2021 at 7:03 PM Yu, Mingli wrote:
> From: Mingli Yu
>
> After the commit [1] introduced in openembedded-core layer,
> some configure options is't carried over include xshmfence
> option, so remove the xshmfence configure option to silence
> the below warning.
> WARNING:
From: Mingli Yu
After the commit [1] introduced in openembedded-core layer,
some configure options is't carried over include xshmfence
option, so remove the xshmfence configure option to silence
the below warning.
WARNING: xserver-xorg-2_21.1.1-r0 do_configure: QA Issue: xserver-xorg:
invalid
On Wed, Dec 8, 2021 at 6:03 PM Trevor Woerner wrote:
> On Wed 2021-12-08 @ 01:15:26 PM, Khem Raj wrote:
> > meta-arm has dropped exporting virtual/trusted-firmware-a and expects
> > direct use of trusted-firmware-a on depends sections
> >
> > Signed-off-by: Khem Raj
> > ---
> >
On Wed 2021-12-08 @ 03:29:14 PM, Trevor Woerner wrote:
> The latest trusted-firmware-a recipe in meta-arm no longer considers
> trusted-firmware-a to have potentially multiple providers.
>
> Signed-off-by: Trevor Woerner
> ---
> recipes-bsp/u-boot/u-boot%.bbappend | 4 ++--
> 1 file changed, 2
On Wed 2021-12-08 @ 01:15:26 PM, Khem Raj wrote:
> meta-arm has dropped exporting virtual/trusted-firmware-a and expects
> direct use of trusted-firmware-a on depends sections
>
> Signed-off-by: Khem Raj
> ---
> recipes-bsp/u-boot/u-boot%.bbappend | 4 ++--
> 1 file changed, 2 insertions(+), 2
On Wed 2021-12-08 @ 11:54:04 AM, Khem Raj wrote:
> This has been included upstream see [1]
>
> [1]
> https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/f943b7c8e292e3aad2fcbdd0a37505f62b3b4c87%5E%21/#F0
>
> Signed-off-by: Khem Raj
> ---
>
On Wed, Dec 8, 2021 at 2:08 PM Nicolas Dechesne
wrote:
>
>
> On Wed, Dec 8, 2021 at 10:57 PM Michael Opdenacker <
> michael.opdenac...@bootlin.com> wrote:
>
>> Quentin, Nico,
>>
>> On 12/3/21 11:51 AM, Quentin Schulz wrote:
>> >
>> > I think all our issues always come down to this weird and
On Wed, Dec 8, 2021 at 10:57 PM Michael Opdenacker <
michael.opdenac...@bootlin.com> wrote:
> Quentin, Nico,
>
> On 12/3/21 11:51 AM, Quentin Schulz wrote:
> >
> > I think all our issues always come down to this weird and inefficient
> > organization we have for docs and common files between doc
In message: [linux-yocto][PATCH 1/1] arm64: zynqmp: fix dtb compile warning
on 08/12/2021 quanyang.w...@windriver.com wrote:
> From: Quanyang Wang
>
> There should be one "@" between node-name and unit-address.
>
> Signed-off-by: Quanyang Wang
> ---
> Hi Bruce,
>
> Would you please help
Quentin, Nico,
On 12/3/21 11:51 AM, Quentin Schulz wrote:
>
> I think all our issues always come down to this weird and inefficient
> organization we have for docs and common files between doc releases.
> We'll need to settle on something one day because I don't think what
> we're doing today is
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] media: ov5640 mipi v2:
fix kernel warning when no camera is plugged in
on 08/12/2021 Xiaolei Wang wrote:
> the regulator need to be disabled before
In message: [linux-yocto][linux-yocto v5.10] fix patches for marvell octeon
on 07/12/2021 Ruiqiang Hao wrote:
> Hi Bruce,
>
> Please help to merge these two patches into our linux-yocto repo.
I'm glad you said "two" here, since the patch numbers were /3 :)
These are now merged.
Bruce
>
In message: [linux-yocto] [linux-yocto preempt-rt kernel]: nxp-s32g2xx: update
linux-yocto to NXP bsp31 release version
on 06/12/2021 Zhantao Tang wrote:
> Hi Bruce,
>
> There are 42 patches(including 25 patches from bsp31 rc5~rc8 and 17 patches
> for bug-fix) for rebase the following branch
>
In message: [linux-yocto] [linux-yocto std kernel]: nxp-s32g2xx: update
linux-yocto to NXP bsp31 release version
on 06/12/2021 Zhantao Tang wrote:
> Hi Bruce,
>
> There are 43 patches(including 25 patches from bsp31 rc5~rc8 and 18 patches
> for bug-fix) for rebase the following branch
>
meta-arm has dropped exporting virtual/trusted-firmware-a and expects
direct use of trusted-firmware-a on depends sections
Signed-off-by: Khem Raj
---
recipes-bsp/u-boot/u-boot%.bbappend | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-bsp/u-boot/u-boot%.bbappend
On Wed, Dec 08, 2021 at 12:06:49PM -0800, chiefsleepy...@gmail.com wrote:
> I'm on the "dunfell" branch and trying to build core-image-minimal-initramfs
> for a j7-evm target. When I do that I get the following error:
>
> >
> > * Solver encountered 1 problem(s):
> > * Problem 1/1:
> > * -
The latest trusted-firmware-a recipe in meta-arm no longer considers
trusted-firmware-a to have potentially multiple providers.
Signed-off-by: Trevor Woerner
---
recipes-bsp/u-boot/u-boot%.bbappend | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
I'm on the "dunfell" branch and trying to build core-image-minimal-initramfs
for a j7-evm target. When I do that I get the following error:
>
> * Solver encountered 1 problem(s):
> * Problem 1/1:
> * - nothing provides grub needed by
> initramfs-module-install-1.0-r1.aarch64
> *
> * Solution
This has been included upstream see [1]
[1]
https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/f943b7c8e292e3aad2fcbdd0a37505f62b3b4c87%5E%21/#F0
Signed-off-by: Khem Raj
---
.../files/0001-Fix-build-with-gcc-11.patch| 34 ---
Hi Quentin,
Thanks for the review and for your suggestions.
On 12/3/21 10:34 AM, Quentin Schulz wrote:
> Hi Michael,
>
> On Wed, Dec 01, 2021 at 02:49:31PM +0100, Michael Opdenacker wrote:
>> This allows all versions of Bitbake and Yocto Project manuals
>> to see the manuals for the latest
On Mon, 6 Dec 2021, Jon Mason wrote:
> This email is a follow-up from the session held on Friday at the
> OpenEmbedded Developer's Virtual Meeting (see
> https://www.openembedded.org/wiki/OEDVM_Nov_2021)
>
> The session was not recorded, but the slides can be found at
>
Dear all,
My goal is to have a squashfs rootfstype and ext4 data partition that get
combined in an overlayfs and switched to the root during boot.
I managed to get the overlayfs and switching of root working thanks to
meta-readonly-rootfs and some changes locally, but only with 2 ext4
Hi,
You could also consider using the `BBFILES_DYNAMIC`[1] variable, this way your
bbappend
would only apply when there is `meta-raspberrypi` in the build configuration.
Your bbappend
could be placed in custom layer under
`dynamic-layers/raspberrypi/recipes-bsp/bootfiles/ rpi-cmdline.bbappend `
You can either use BBMASK in your local.conf to remove the bbappend from
the parsing tree or set BB_DANGLINGAPPENDS_WARNONLY in your specific build.
both can be added to your specific kas yaml without any issues
[1]
Dear all,
My situation is as follows:
* Using Kas container to build and enable easy CI, I have 2 .yaml files
creating my 2 builds for 2 different machines: RaspberryPi and Qemu.
* Qemu yaml file does not contain meta-raspberrypi repo
* Custom distro that extends poky has a script
From: Quanyang Wang
There should be one "@" between node-name and unit-address.
Signed-off-by: Quanyang Wang
---
Hi Bruce,
Would you please help merge this patch to the following linux-yocto branches:
v5.10/standard/preempt-rt/sdkv5.10/xlnx-soc
v5.10/standard/sdkv5.10/xlnx-soc
Thanks,
26 matches
Mail list logo
