date:20231009

Re: [yocto] [meta-rockchip] [PATCH v2] rock-3a add

2023-10-09 Thread Quentin Schulz via lists.yoctoproject.org


Hi Anthony,

On 10/7/23 01:26, Anthony Davies via lists.yoctoproject.org wrote:

From: Anthony Davies 

Add support for the Radxa Rock 3A
https://wiki.radxa.com/Rock3/3a

The TF-A project does not currently have support for
the rk3568. Therefore, for the time-being, the only way to supply a
TPL/DDR-init for the rk3568 is to use the closed-source rkbin binaries
from Rockchip. If/when TF-A adds support for the rk3588 we can investigate
switching.

recipes-bsp/rkbin/rockchip-rkbin_git.bb was modified to allow a machine
override to allow both rk3568 and rk3588s to use differnet binary blobs

Signed-off-by: Anthony Davies 
---
  README  |  1 +
  conf/machine/include/rk3568.inc | 17 +
  conf/machine/rock-3a.conf   | 12 
  recipes-bsp/rkbin/rockchip-rkbin_git.bb | 16 +++-
  recipes-bsp/u-boot/u-boot%.bbappend |  5 +
  5 files changed, 50 insertions(+), 1 deletion(-)
  create mode 100644 conf/machine/include/rk3568.inc
  create mode 100644 conf/machine/rock-3a.conf

diff --git a/README b/README
index 8104474..3357b47 100644
--- a/README
+++ b/README
@@ -32,6 +32,7 @@ Status of supported boards:
nanopi-r4s
rock-5b
nanopi-r2s
+rock-3a


Please use the same indentation here so it's aligned with the other boards.

It's 2 tabs for the indentation there it seems.


builds:
marsboard-rk3066
radxarock
diff --git a/conf/machine/include/rk3568.inc b/conf/machine/include/rk3568.inc
new file mode 100644
index 000..5382b58
--- /dev/null
+++ b/conf/machine/include/rk3568.inc
@@ -0,0 +1,17 @@
+MACHINEOVERRIDES =. "rk3568:"
+DEFAULTTUNE ?= "cortexa55"
+
+require conf/machine/include/arm/armv8-2a/tune-cortexa55.inc
+require conf/machine/include/rockchip-defaults.inc
+require conf/machine/include/rockchip-wic.inc
+
+KBUILD_DEFCONFIG ?= "defconfig"
+KERNEL_FEATURES:append:rk3568 = " 
bsp/rockchip/remove-non-rockchip-arch-arm64.scc"
+KERNEL_CLASSES ??= "kernel-fitimage"
+KERNEL_IMAGETYPE ??= "fitImage"
+
+PREFERRED_PROVIDER_trusted-firmware-a = "rockchip-rkbin"
+PREFERRED_PROVIDER_optee-os = "rockchip-rkbin"
+
+UBOOT_SUFFIX ?= "itb"
+UBOOT_ENTRYPOINT ?= "0x0600"
diff --git a/conf/machine/rock-3a.conf b/conf/machine/rock-3a.conf
new file mode 100644
index 000..2ed83a3
--- /dev/null
+++ b/conf/machine/rock-3a.conf
@@ -0,0 +1,12 @@
+#@TYPE: Machine
+#@NAME: Radxa Rock 3a
+#@DESCRIPTION: ROCK3 is a series of Rockchip RK3566/RK3568 based
+#SBC(Single Board Computer) and Compute Module by Radxa.
+#https://wiki.radxa.com/Rock3
+
+require conf/machine/include/rk3568.inc
+
+KERNEL_DEVICETREE = "rockchip/rk3568-rock-3a.dtb"
+MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
+
+UBOOT_MACHINE = "rock-3a-rk3568_defconfig"
diff --git a/recipes-bsp/rkbin/rockchip-rkbin_git.bb 
b/recipes-bsp/rkbin/rockchip-rkbin_git.bb
index 7fefb01..273f394 100644
--- a/recipes-bsp/rkbin/rockchip-rkbin_git.bb
+++ b/recipes-bsp/rkbin/rockchip-rkbin_git.bb
@@ -14,6 +14,7 @@ S = "${WORKDIR}/git"
  
  COMPATIBLE_MACHINE = ""

  COMPATIBLE_MACHINE:rk3588s = "rk3588s"
+COMPATIBLE_MACHINE:rk3568 = "rk3568"
  
  PACKAGE_ARCH = "${MACHINE_ARCH}"
  
@@ -25,7 +26,16 @@ do_install() {

  PACKAGES = "${PN}"
  ALLOW_EMPTY:${PN} = "1"
  
-do_deploy() {

+do_deploy:rk3568() {
+   # Prebuilt TF-A
+   install -m 644 ${S}/bin/rk35/rk3568_bl31_v*.elf 
${DEPLOYDIR}/bl31-rk3568.elf
+   # Prebuilt OPTEE-OS
+   install -m 644 ${S}/bin/rk35/rk3568_bl32_v*.bin 
${DEPLOYDIR}/tee-rk3568.bin
+   # Prebuilt U-Boot TPL (DDR init)
+   install -m 644 ${S}/bin/rk35/rk3568_ddr_1560MHz_v1.18.bin 
${DEPLOYDIR}/ddr-rk3568.bin
+}
+
+do_deploy:rk3588s() {
# Prebuilt TF-A
install -m 644 ${S}/bin/rk35/rk3588_bl31_v*.elf 
${DEPLOYDIR}/bl31-rk3588.elf
# Prebuilt OPTEE-OS
@@ -34,4 +44,8 @@ do_deploy() {
install -m 644 ${S}/bin/rk35/rk3588_ddr_lp4_2112MHz_lp5_2736MHz_v*.bin 
${DEPLOYDIR}/ddr-rk3588.bin
  }
  
+do_deploy() {

+# Needed as a default perhaps a bb.fatal with a message saying an override 
needs to be set
+}
+


Well, we could, but also... the recipe won't be used until you add to 
COMPATIBLE_MACHINE, which means the recipe should have been working by 
the time you add it. Not entirely sure how much we want to prevent users 
to shoot their own foot honestly. But I guess it's such a small change 
that adding it is probably better than just arguing whether we need it 
or not, so maybe send another patch to add the bb.fatal :) ?


Cheers,
Quentin

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

Re: [yocto] [meta-rockchip] [PATCH v2] rock-3a add

2023-10-09 Thread Anthony Davies

Hi Quentin,

On Mon, 9 Oct 2023 at 19:25, Quentin Schulz
 wrote:
>
> Hi Anthony,
>
> On 10/7/23 01:26, Anthony Davies via lists.yoctoproject.org wrote:
> > From: Anthony Davies 
> >
> > Add support for the Radxa Rock 3A
> > https://wiki.radxa.com/Rock3/3a
> >
> > The TF-A project does not currently have support for
> > the rk3568. Therefore, for the time-being, the only way to supply a
> > TPL/DDR-init for the rk3568 is to use the closed-source rkbin binaries
> > from Rockchip. If/when TF-A adds support for the rk3588 we can investigate
> > switching.
> >
> > recipes-bsp/rkbin/rockchip-rkbin_git.bb was modified to allow a machine
> > override to allow both rk3568 and rk3588s to use differnet binary blobs
> >
> > Signed-off-by: Anthony Davies 
> > ---
> >   README  |  1 +
> >   conf/machine/include/rk3568.inc | 17 +
> >   conf/machine/rock-3a.conf   | 12 
> >   recipes-bsp/rkbin/rockchip-rkbin_git.bb | 16 +++-
> >   recipes-bsp/u-boot/u-boot%.bbappend |  5 +
> >   5 files changed, 50 insertions(+), 1 deletion(-)
> >   create mode 100644 conf/machine/include/rk3568.inc
> >   create mode 100644 conf/machine/rock-3a.conf
> >
> > diff --git a/README b/README
> > index 8104474..3357b47 100644
> > --- a/README
> > +++ b/README
> > @@ -32,6 +32,7 @@ Status of supported boards:
> >   nanopi-r4s
> >   rock-5b
> >   nanopi-r2s
> > +rock-3a
>
> Please use the same indentation here so it's aligned with the other boards.
>
> It's 2 tabs for the indentation there it seems.

This would be my vim converting my \t to spaces. I will update and resend.

>
> >   builds:
> >   marsboard-rk3066
> >   radxarock
> > diff --git a/conf/machine/include/rk3568.inc 
> > b/conf/machine/include/rk3568.inc
> > new file mode 100644
> > index 000..5382b58
> > --- /dev/null
> > +++ b/conf/machine/include/rk3568.inc
> > @@ -0,0 +1,17 @@
> > +MACHINEOVERRIDES =. "rk3568:"
> > +DEFAULTTUNE ?= "cortexa55"
> > +
> > +require conf/machine/include/arm/armv8-2a/tune-cortexa55.inc
> > +require conf/machine/include/rockchip-defaults.inc
> > +require conf/machine/include/rockchip-wic.inc
> > +
> > +KBUILD_DEFCONFIG ?= "defconfig"
> > +KERNEL_FEATURES:append:rk3568 = " 
> > bsp/rockchip/remove-non-rockchip-arch-arm64.scc"
> > +KERNEL_CLASSES ??= "kernel-fitimage"
> > +KERNEL_IMAGETYPE ??= "fitImage"
> > +
> > +PREFERRED_PROVIDER_trusted-firmware-a = "rockchip-rkbin"
> > +PREFERRED_PROVIDER_optee-os = "rockchip-rkbin"
> > +
> > +UBOOT_SUFFIX ?= "itb"
> > +UBOOT_ENTRYPOINT ?= "0x0600"
> > diff --git a/conf/machine/rock-3a.conf b/conf/machine/rock-3a.conf
> > new file mode 100644
> > index 000..2ed83a3
> > --- /dev/null
> > +++ b/conf/machine/rock-3a.conf
> > @@ -0,0 +1,12 @@
> > +#@TYPE: Machine
> > +#@NAME: Radxa Rock 3a
> > +#@DESCRIPTION: ROCK3 is a series of Rockchip RK3566/RK3568 based
> > +#SBC(Single Board Computer) and Compute Module by Radxa.
> > +#https://wiki.radxa.com/Rock3
> > +
> > +require conf/machine/include/rk3568.inc
> > +
> > +KERNEL_DEVICETREE = "rockchip/rk3568-rock-3a.dtb"
> > +MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
> > +
> > +UBOOT_MACHINE = "rock-3a-rk3568_defconfig"
> > diff --git a/recipes-bsp/rkbin/rockchip-rkbin_git.bb 
> > b/recipes-bsp/rkbin/rockchip-rkbin_git.bb
> > index 7fefb01..273f394 100644
> > --- a/recipes-bsp/rkbin/rockchip-rkbin_git.bb
> > +++ b/recipes-bsp/rkbin/rockchip-rkbin_git.bb
> > @@ -14,6 +14,7 @@ S = "${WORKDIR}/git"
> >
> >   COMPATIBLE_MACHINE = ""
> >   COMPATIBLE_MACHINE:rk3588s = "rk3588s"
> > +COMPATIBLE_MACHINE:rk3568 = "rk3568"
> >
> >   PACKAGE_ARCH = "${MACHINE_ARCH}"
> >
> > @@ -25,7 +26,16 @@ do_install() {
> >   PACKAGES = "${PN}"
> >   ALLOW_EMPTY:${PN} = "1"
> >
> > -do_deploy() {
> > +do_deploy:rk3568() {
> > + # Prebuilt TF-A
> > + install -m 644 ${S}/bin/rk35/rk3568_bl31_v*.elf 
> > ${DEPLOYDIR}/bl31-rk3568.elf
> > + # Prebuilt OPTEE-OS
> > + install -m 644 ${S}/bin/rk35/rk3568_bl32_v*.bin 
> > ${DEPLOYDIR}/tee-rk3568.bin
> > + # Prebuilt U-Boot TPL (DDR init)
> > + install -m 644 ${S}/bin/rk35/rk3568_ddr_1560MHz_v1.18.bin 
> > ${DEPLOYDIR}/ddr-rk3568.bin
> > +}
> > +
> > +do_deploy:rk3588s() {
> >   # Prebuilt TF-A
> >   install -m 644 ${S}/bin/rk35/rk3588_bl31_v*.elf 
> > ${DEPLOYDIR}/bl31-rk3588.elf
> >   # Prebuilt OPTEE-OS
> > @@ -34,4 +44,8 @@ do_deploy() {
> >   install -m 644 
> > ${S}/bin/rk35/rk3588_ddr_lp4_2112MHz_lp5_2736MHz_v*.bin 
> > ${DEPLOYDIR}/ddr-rk3588.bin
> >   }
> >
> > +do_deploy() {
> > +# Needed as a default perhaps a bb.fatal with a message saying an override 
> > needs to be set
> > +}
> > +
>
> Well, we could, but also... the recipe won't be used until you add to
> COMPATIBLE_MACHINE, which means the recipe should have been working by
> the time you add it. Not entirely sure how much we want to prevent users
> to shoot their own foot hon

[yocto] Password added succesfully but defaults to autologin

2023-10-09 Thread MOHAMMED HASSAN

Hi guys,
I am trying to set up a login password for my hardware but the problem is
that my device uses automatic login. I checked online to comment out
automatic login but it seems like
my /lib/systemd/system/serial-getty\@.service contains the line
"ExecStart=-/sbin/agetty -8 -L %I 921600 $TERM --autologin root" but before
building the image i checked my service file and "ExecStart=-/sbin/agetty
-8 -L %I @BAUDRATE@ $TERM". There is no mention of autologin and in my
image recipe file I have not enabled it.
After removing the line manually and reloading the service I can use the
login creds to login but ssh login returns the message "permission denied".

I have attached the relevant files for your reference. Let me know if you
need more information.

Regards,
Hassan


amlogic-yocto.bb
Description: Binary data
#  SPDX-License-Identifier: LGPL-2.1+
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Serial Getty on %I
Documentation=man:agetty(8) man:systemd-getty-generator(8)
Documentation=http://0pointer.de/blog/projects/serial-console.html
PartOf=dev-%i.device
ConditionPathExists=/dev/%i
After=dev-%i.device systemd-user-sessions.service plymouth-quit-wait.service getty-pre.target
After=rc-local.service

# If additional gettys are spawned during boot then we should make
# sure that this is synchronized before getty.target, even though
# getty.target didn't actually pull it in.
Before=getty.target
IgnoreOnIsolate=yes

# IgnoreOnIsolate causes issues with sulogin, if someone isolates
# rescue.target or starts rescue.service from multi-user.target or
# graphical.target.
Conflicts=rescue.service
Before=rescue.service

[Service]
Environment="TERM=xterm"
ExecStart=-/sbin/agetty -8 -L %I @BAUDRATE@ $TERM
Type=idle
Restart=always
UtmpIdentifier=%I
TTYPath=/dev/%I
TTYReset=yes
TTYVHangup=yes
KillMode=process
IgnoreSIGPIPE=no
SendSIGHUP=yes

[Install]
WantedBy=getty.target


systemd-serialgetty.bb
Description: Binary data

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

[yocto] continuous security updates for the Linux system

2023-10-09 Thread MOHAMMED HASSAN

Hi guys,
I want to know more about security updates in yocto.
So generally we update our distros when we get pop-ups about security
updates and it's done. But what if my device is installed at a
remote location? How does security update take place in the case of yocto?
How can we do it?
Any other relevant information is graciously welcomed.


Thanks and Regards,
Hassan

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

Re: [yocto] continuous security updates for the Linux system

2023-10-09 Thread Josef Holzmayr

Please see https://wiki.yoctoproject.org/wiki/System_Update

Full disclosure: I work for Mender, which is one of the mentioned OTA
solutions - mender.io

Greetz,
Josef

On Mon, Oct 9, 2023 at 2:56 PM MOHAMMED HASSAN 
wrote:

> Hi guys,
> I want to know more about security updates in yocto.
> So generally we update our distros when we get pop-ups about security
> updates and it's done. But what if my device is installed at a
> remote location? How does security update take place in the case of yocto?
> How can we do it?
> Any other relevant information is graciously welcomed.
>
>
> Thanks and Regards,
> Hassan
>
> 
>
>

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

Re: [yocto] continuous security updates for the Linux system

2023-10-09 Thread MOHAMMED HASSAN

On Mon, Oct 9, 2023 at 06:12 AM, Josef Holzmayr wrote:

> 
> Please see https://wiki.yoctoproject.org/wiki/System_Update
> 
> 

Thanks for your reply. I am aware of the system_updates feature though still 
yet to implement. Is it possible to update the yocto version (i use dunfell) to 
the latest one, to update the linux version(mine is 5.4.180) to the latest and 
to update the tools to the latest using these features. Actually i have no 
clarity with this so I am asking.

Thanks and regards,
Hassan

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

Re: [yocto] continuous security updates for the Linux system

2023-10-09 Thread Adrian Freihofer

Hi

Would it be possible to extend the
https://wiki.yoctoproject.org/wiki/System_Update table with compatible
backends? Ideally the license of the backends should also be
transparent. OE/Yocto should not end up with a vendor lock in when it
comes to a standard update mechanism. In the end it's about a solution
with client and server, where a client alone is usually pretty
worthless.

Regards,
Adrian

On Mon, 2023-10-09 at 06:22 -0700, MOHAMMED HASSAN wrote:
> On Mon, Oct 9, 2023 at 06:12 AM, Josef Holzmayr wrote:
> > Please see https://wiki.yoctoproject.org/wiki/System_Update
> >  
> Thanks for your reply. I am aware of the system_updates feature
> though still yet to implement. Is it possible to update the yocto
> version (i use dunfell) to the latest one, to update the linux
> version(mine is 5.4.180) to the latest and to update the tools to the
> latest using these features. Actually i have no clarity with this so
> I am asking.
> 
> Thanks and regards,
> Hassan
> 
> 
> 


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

Re: [yocto] continuous security updates for the Linux system

2023-10-09 Thread Michael Opdenacker via lists.yoctoproject.org


Hi Hassan

On 09.10.23 at 15:22, MOHAMMED HASSAN wrote:

On Mon, Oct 9, 2023 at 06:12 AM, Josef Holzmayr wrote:

Please see https://wiki.yoctoproject.org/wiki/System_Update

Thanks for your reply. I am aware of the system_updates feature though 
still yet to implement. Is it possible to update the yocto version (i 
use dunfell) to the latest one, to update the linux version(mine is 
5.4.180) to the latest and to update the tools to the latest using 
these features. Actually i have no clarity with this so I am asking.



Which version of Yocto are you using? If you have one that is still 
supported (like Kirkstone or Dunfell), I'd recommend to stick to these 
and just rebuild with the latest release update. This way you have the 
latest vulnerability fixes supported by the Yocto Project. Once a new 
image is generated, you can deploy it using one of the tools Josef 
mentioned.


Moving to the latest version of Yocto will represent more work, all the 
more as the latest one should be replaced this month.


As far as the Linux kernel is concerned, I'd rather work with a stable 
LTS kernel (https://kernel.org/category/releases.html), as I guess the 
Yocto Project releases can't match the stable kernels in terms of 
vulnerability fixes and how quickly they are deployed. That's my own 
opinion though.


I hope this helps
Cheers
Michael.

--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


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

Re: [yocto] continuous security updates for the Linux system

2023-10-09 Thread MOHAMMED HASSAN

On Mon, Oct 9, 2023 at 07:11 AM, Michael Opdenacker wrote:

> 
> Hi Hassan
> 
> On 09.10.23 at 15:22, MOHAMMED HASSAN wrote:
> 
>> On Mon, Oct 9, 2023 at 06:12 AM, Josef Holzmayr wrote:
>> 
>> Please see https://wiki.yoctoproject.org/wiki/System_Update
>> 
>> Thanks for your reply. I am aware of the system_updates feature though
>> still yet to implement. Is it possible to update the yocto version (i
>> use dunfell) to the latest one, to update the linux version(mine is
>> 5.4.180) to the latest and to update the tools to the latest using
>> these features. Actually i have no clarity with this so I am asking.
> 
> 
> Which version of Yocto are you using? If you have one that is still
> supported (like Kirkstone or Dunfell), I'd recommend to stick to these
> and just rebuild with the latest release update. This way you have the
> latest vulnerability fixes supported by the Yocto Project. Once a new
> image is generated, you can deploy it using one of the tools Josef
> mentioned.
> 
> Moving to the latest version of Yocto will represent more work, all the
> more as the latest one should be replaced this month.
> 
> As far as the Linux kernel is concerned, I'd rather work with a stable
> LTS kernel ( https://kernel.org/category/releases.html ), as I guess the
> Yocto Project releases can't match the stable kernels in terms of
> vulnerability fixes and how quickly they are deployed. That's my own
> opinion though.
> 
> 

Hi Michael,
Thanks for your reply.
I am currently using dunfell 3.1.11 and my kernel release is Linux 
5.4.180-amlogic. Going by your suggestion i should rebuild to the latest 
dunfell update i.e 3.1.28. Moving to kirkstone would take more work.
I will search on how to update my yocto release version and get into it.

Thanks
Hassan

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

Re: [yocto] Password added succesfully but defaults to autologin

2023-10-09 Thread MOHAMMED HASSAN

Let me know if I am making any mistakes here. Also let me know if you need any 
other piece of information to help me on this issue.

Thanks,
Hassan

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

[yocto] Auto-mount causing "transport endpoint is not connected error"

2023-10-09 Thread Logan Grosz via lists.yoctoproject.org

Hi, all

I am attempting to set up removable drive auto-mounting. I am doing so with a 
tweaked version of meta/recipes-core/udev/udev-extraconf/mount.sh.

My version is as follows

```
#!/bin/sh
#
# Called from udev
#
# Attempt to mount any added block devices and umount any removed devices
#
# This way ripped from mickledore poky with some modifications

MOUNT_BASE="/run/media/"
MOUNT="/bin/mount"
UMOUNT="/bin/umount"

for line in `grep -h -v ^# /etc/udev/mount.ignorelist 
/etc/udev/mount.ignorelist.d/*`
do
if [ ` expr match "$DEVNAME" "$line" ` -gt 0 ];
then
logger "udev/mount.sh" "[$DEVNAME] is marked to ignore"
exit 0
fi
done

automount() {
name="`basename "$DEVNAME"`"

$MOUNT $DEVNAME 2> /dev/null

# If the device isn't mounted at this point, it isn't
# configured in fstab
grep -q "^$DEVNAME " /proc/mounts && return

# Get the unique name for mount point
get_label_name "${DEVNAME}"

# Only go for auto-mounting when the device has been cleaned up in 
remove
# or has not been identified yet
if [ -e "/tmp/.automount-$basename" ]; then
logger "mount.sh/automount" "[$MOUNT_BASE/name$] is already 
cached"
return
fi

! test -d "$MOUNT_BASE/$name" && mkdir -p "$MOUNT_BASE/$name"
# Silent util-linux's version of mounting auto
if [ "x`readlink $MOUNT`" = "x/bin/mount.util-linux" ] ;
then
MOUNT="$MOUNT -o silent"
fi

# If filesystem type is vfat, change the ownership group to 'disk', and
# grant it with  w/r/x permissions.
case $ID_FS_TYPE in
vfat|fat)
MOUNT="$MOUNT -o umask=007,gid=`awk -F':' 
'/^disk/{print $3}' /etc/group`"
;;
swap)
return ;;
lvm*|LVM*)
return ;;
# TODO
*)
;;
esac

if ! $MOUNT -t auto $DEVNAME "$MOUNT_BASE/$name"
then
logger "mount.sh/automount" "$MOUNT -t auto $DEVNAME 
\"$MOUNT_BASE/$name\" failed!"
rm_dir "$MOUNT_BASE/$name"
else
logger "mount.sh/automount" "Auto-mount of [$MOUNT_BASE/$name] 
successful"
# The actual device might not be present in the remove event so 
blkid cannot
# be used to calculate what name was generated here. Simply 
save the mount
# name in our tmp file.
echo "$MOUNT_BASE/$name" > "/tmp/.automount-$basename"
fi
}

rm_dir() {
# We do not want to rm -r populated directories
if test "`find "$1" | wc -l | tr -d " "`" -lt 2 -a -d "$1"
then
! test -z "$1" && rm -r "$1"
else
logger "mount.sh/automount" "Not removing non-empty directory 
[$1]"
fi
}

get_label_name() {
# Get the LABEL or PARTLABEL
LABEL=`/sbin/blkid | grep "$1:" | grep -o 'LABEL=".*"' | cut -d '"' -f2`
# If the $DEVNAME has a LABEL or a PARTLABEL
if [ -n "$LABEL" ]; then
name="${LABEL}"
else
name="USB Drive"
fi

n=1;
prefix=$name
while [ -d $MOUNT_BASE/$name ]
do
name=$prefix-$n
((n++))
done
}

# No ID_FS_TYPE for cdrom device, yet it should be mounted
basename="`basename "$DEVNAME"`"
name=$basename
[ -e /sys/block/$basename/device/media ] && media_type=`cat 
/sys/block/$basename/device/media`

if [ "$ACTION" = "add" ] && [ -n "$DEVNAME" ] && [ -n "$ID_FS_TYPE" -o 
"$media_type" = "cdrom" ]; then
# Note the root filesystem can show up as /dev/root in /proc/mounts,
# so check the device number too
if expr $MAJOR "*" 256 + $MINOR != `stat -c %d /`; then
automount
fi
fi

if [ "$ACTION" = "remove" ] || [ "$ACTION" = "change" ] && [ -x "$UMOUNT" ] && 
[ -n "$DEVNAME" ]; then
tmpfile=`find /tmp | grep "\.automount-${basename}$"`
if [ ! -e "/sys/$DEVPATH" -a -e "$tmpfile" ]; then
logger "mount.sh/remove" "cleaning up $DEVNAME, was mounted by 
the auto-mounter"
for mnt in `cat /proc/mounts | grep "$DEVNAME" | cut -f 2 -d " 
" `
do
$UMOUNT $mnt
done

# Remove mount directory created by the auto-mounter
# and clean up our tmp cache file
rm_dir `cat $tmpfile`
rm "$tmpfile"
fi
fi
```

The udev rules are identical to that from poky. Unfortunately, every time I 
insert my USB drive I get a file created /run/media/LABEL, upon when I run ls 
-la /run/media/LABEL, I receive an error, ls: cannot access 
'/run/media/LABEL': Transport endpoint is not connected.

I am on

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

2023-10-09 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 411
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.3”, “4.4”, "4.99" and "Future", the more
pressing/urgent issues being in "4.3" and then “4.4”.

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*: *s
jolley.yp...@gmail.com *

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61292): https://lists.yoctoproject.org/g/yocto/message/61292
Mute This Topic: https://lists.yoctoproject.org/mt/101864968/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.3

2023-10-09 Thread Stephen Jolley

All,

Below is the list of top 25 bug owners as of the end of WW40 who have open
medium or higher bugs and enhancements against YP 4.3. There are 1 possible
workday left until the final release candidates for YP 4.3 needs to be
released.
Who Count
michael.opdenac...@bootlin.com 34
ross.bur...@arm.com 30
richard.pur...@linuxfoundation.org 24
david.re...@windriver.com 23
randy.macl...@windriver.com 16
bruce.ashfi...@gmail.com 13
jpewhac...@gmail.com 10
pi...@pidge.org 7
yash.shi...@windriver.com 5
alexandre.bell...@bootlin.com 3
tim.orl...@konsulko.com 2
sundeep.kokko...@windriver.com 2
pa...@zhukoff.net 2
jon.ma...@arm.com 2
alexis.loth...@bootlin.com 2
yoann.con...@smile.fr 1
tvgamb...@gmail.com 1
thr...@amazon.de 1
thomas.per...@bootlin.com 1
sakib.sa...@windriver.com 1
p.lob...@welotec.com 1
mark.asselst...@windriver.com 1
louis.ran...@syslinbit.com 1
jens.ge...@desy.de 1
fathi.bou...@linaro.org 1
Grand Total 185

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *

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

[yocto] Enhancements/Bugs closed WW40!

2023-10-09 Thread Stephen Jolley

All,

The below were the owners of enhancements or bugs closed during the last
week!
Who Count
tim.orl...@konsulko.com 2
randy.macl...@windriver.com 2
ross.bur...@arm.com 1
Grand Total 5

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *

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

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

2023-10-09 Thread Stephen Jolley

All,

YP M+ or high bugs which moved to a new milestone in WW40 are listed below:
Priority Bug ID Short Description Changer Owner Was Became
Medium+ 3362  Improve
dependency analysis tools randy.macl...@windriver.com
richard.pur...@linuxfoundation.org 0.0.0 5.99
4530  gconv data
needs virtual providers randy.macl...@windriver.com
bernhard.guil...@begu.org 0.0.0 5.0 M1
10820  devtool:
-d/--debug doesn't show bitbake debug output randy.macl...@windriver.com
pi...@pidge.org 4.3 M3 4.3 M4
11704  Add other
resource monitoring options to conf/local.conf STOPTASKS/ABORT
randy.macl...@windriver.com randy.macl...@windriver.com 4.3 M3 5.0 M2
13919  Multi
License GPLv3 -lic cannot be installed into the image because it has
incompatible license randy.macl...@windriver.com anilrat...@gmail.com 4.3 M3
5.99
14007  When qemu
hangs, try to create a snapshot or core file. randy.macl...@windriver.com
randy.macl...@windriver.com 4.3 M3 5.0 M1
14157  git
fetcher: consider using different git commands for repo packing,
eliminating "git pack-redundant" randy.macl...@windriver.com
newco...@yoctoproject.org 4.3 M3 5.99
14385  mode of
sstate files created under pseudo randy.macl...@windriver.com
pi...@pidge.org 4.3 M3 4.3 M4
14443  valgrind
none/tests/amd64/fb_test_amd64 ptest intermittent failure
randy.macl...@windriver.com randy.macl...@windriver.com 4.3 M3 5.0 M1
14693  cmake-native
do_configure fails when rebuilding without sstate on NIS hosts
randy.macl...@windriver.com randy.macl...@windriver.com 4.3 M3 5.0 M1
14710  Improve
cargo fetcher test cases randy.macl...@windriver.com
randy.macl...@windriver.com 4.3 M3 5.0 M2
14723  patches not
applied by devtool when using overrides in SRC_URI
randy.macl...@windriver.com pi...@pidge.org 4.3 M3 4.3 M4
14837  devtool
modify doesnt fetch all the crates on rust based recipes
randy.macl...@windriver.com pi...@pidge.org 4.3 M3 4.3 M4
15023  Cannot
build SDK with api-documentation enabled randy.macl...@windriver.com
pi...@pidge.org 4.3 M3 4.3 M4
15061  Rust
multilib sdks broken randy.macl...@windriver.com
deepthi.hem...@windriver.com 4.3 M3 4.3 M4
15071  AB-INT
PTEST: strace ptest intermittent failure in syscall-times-ms.gen
randy.macl...@windriver.com randy.macl...@windriver.com 4.3 M3 4.3 M4
15074  syncfs
probe fails with newer compilers randy.macl...@windriver.com
pi...@pidge.org 4.3
M3 4.3 M4
15145  module conf
files missing when KERNEL_SPLIT_MODULES=0 randy.macl...@windriver.com
george.tho...@gmail.com 4.3 M3 5.0 M1
15172  tzdata
recipe: build tzdata.zi zoneinfo file randy.macl...@windriver.com
randy.macl...@windriver.com 4.3 M3 5.0 M1

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *

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

[yocto] inode mismatch

2023-10-09 Thread MOHAMMED HASSAN

Hi guys,
I did bitbake image clean && bitbake image but it continuously due to inode
mismatch
The error i see
Initialising tasks: 100%
|##|
Time: 0:00:19
Sstate summary: Wanted 236 Found 217 Missed 19 Current 2867 (91% match, 99%
complete)
NOTE: Executing Tasks
ERROR: lib32-libdrm-meson-git-r0 do_prepare_recipe_sysroot: Error executing
a python function in exec_func_python() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_func_python() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:extend_recipe_sysroot(d)
 0003:
File: '/Yocto/yocto_sdk/poky/meta/classes/staging.bbclass', lineno: 595,
function: extend_recipe_sysroot
 0591:for f in fixme:
 0592:staging_processfixme(fixme[f], f, recipesysroot,
recipesysrootnative, d)
 0593:
 0594:for p in postinsts:
 *** 0595:subprocess.check_output(p, shell=True,
stderr=subprocess.STDOUT)
 0596:
 0597:for dep in manifests:
 0598:c = setscenedeps[dep][0]
 0599:os.symlink(manifests[dep], depdir + "/" + c + ".complete")
File: '/usr/lib/python3.8/subprocess.py', lineno: 415, function:
check_output
 0411:else:
 0412:empty = b''
 0413:kwargs['input'] = empty
 0414:
 *** 0415:return run(*popenargs, stdout=PIPE, timeout=timeout,
check=True,
 0416:   **kwargs).stdout
 0417:
 0418:
 0419:class CompletedProcess(object):
File: '/usr/lib/python3.8/subprocess.py', lineno: 516, function: run
 0512:# We don't call process.wait() as .__exit__ does that
for us.
 0513:raise
 0514:retcode = process.poll()
 0515:if check and retcode:
 *** 0516:raise CalledProcessError(retcode, process.args,
 0517: output=stdout, stderr=stderr)
 0518:return CompletedProcess(process.args, retcode, stdout, stderr)
 0519:
 0520:
Exception: subprocess.CalledProcessError: Command
'/Yocto/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-libdrm-meson/git-r0/lib32-recipe-sysroot/usr/bin/postinst-useradd-lib32-systemd'
returned non-zero exit status 1.

Subprocess output:
/Yocto/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-libdrm-meson/git-r0/recipe-sysroot-native/usr/sbin/useradd
Running groupadd commands...
NOTE: lib32-systemd: Performing groupadd with [--root
/Yocto/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-libdrm-meson/git-r0/lib32-recipe-sysroot
-r systemd-journal]
abort()ing pseudo client by server request. See
https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this.
Check logfile:
/Yocto/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-libdrm-meson/git-r0/pseudo//pseudo.log
Aborted (core dumped)
ERROR: lib32-systemd: groupadd command did not succeed.

ERROR: Logfile of failure stored in:
/Yocto/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-libdrm-meson/git-r0/temp/log.do_prepare_recipe_sysroot.870561
ERROR: Task
(virtual:multilib:lib32:/Yocto/yocto_sdk/meta-meson/recipes-graphics/wayland/libdrm-meson_git.bb:do_prepare_recipe_sysroot)
failed with exit code '1'



*Here is the data of the entire log file.
/Yocto/yocto_sdk/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-libdrm-meson/git-r0/pseudo//pseudo.log*

debug_logfile: fd 2
pid 163883 [parent 163882], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 163882.
db cleanup for server shutdown, 09:44:43.924
memory-to-file backup complete, 09:44:43.924.
db cleanup finished, 09:44:43.924
debug_logfile: fd 2
pid 384934 [parent 384929], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 384929.
db cleanup for server shutdown, 09:54:34.912
memory-to-file backup complete, 09:54:34.912.
db cleanup finished, 09:54:34.912
debug_logfile: fd 2
pid 1804511 [parent 1804508], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 1804508.
creat for '/tmp/sh-thd.X4MAa7' replaces existing 9438805
['/tmp/sh-thd.qyh9bp'].
creat for '/tmp/sh-thd.XAqy56' replaces existing 9438805
['/tmp/sh-thd.X4MAa7'].
creat for '/tmp/sh-thd.OU5Xfn' replaces existing 9438805
['/tmp/sh-thd.XAqy56'].
creat for '/tmp/sh-thd.EXpf9x' replaces existing 9438805
['/tmp/sh-thd.OU5Xfn'].
creat for '/tmp/sh-thd.XJ9pbB' replaces existing 9438805
['/tmp/sh-thd.EXpf9x'].
db cleanup for server shutdown, 10:47:41.903
memory-to-file backup complete, 10:47:41.903.
db cleanup finished, 10:47:41.903
debug_logfile: fd 2
pid 1960923 [parent 1960922], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 1960922.
db cleanup for server shutdown, 10:52:14.678
memory-to-fil

[yocto] are there any plans for a RISC-V reference board?

2023-10-09 Thread Robert P. J. Day


  at some point, will there be a poky (meta-yocto-bsp) RISC-V
reference board? i'm thinking the Nezha Allwinner D1 (which is
already supported in meta-riscv) would be a safe choice. or maybe the
more powerful VisionFive 2?

  thoughts?

rday

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

Re: [yocto] are there any plans for a RISC-V reference board?

2023-10-09 Thread Josef Holzmayr

Hi Robert,

It has been discussed at numerous occasions. The main blocker is: we need a
commitment for the maintenance. So if a high-ranking member decides to push
forwards with this and allocate resources, or a new member from the RISC-V
ecosystem steps up to make it happen, then the project is all ears.

Greetz,
Josef

On Tue, Oct 10, 2023 at 8:32 AM Robert P. J. Day 
wrote:

>
>   at some point, will there be a poky (meta-yocto-bsp) RISC-V
> reference board? i'm thinking the Nezha Allwinner D1 (which is
> already supported in meta-riscv) would be a safe choice. or maybe the
> more powerful VisionFive 2?
>
>   thoughts?
>
> rday
>
> 
>
>

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

Re: [yocto] [meta-rockchip] [PATCH v2] rock-3a add

Re: [yocto] [meta-rockchip] [PATCH v2] rock-3a add

[yocto] Password added succesfully but defaults to autologin

[yocto] continuous security updates for the Linux system

Re: [yocto] continuous security updates for the Linux system

Re: [yocto] continuous security updates for the Linux system

Re: [yocto] continuous security updates for the Linux system

Re: [yocto] continuous security updates for the Linux system

Re: [yocto] continuous security updates for the Linux system

Re: [yocto] Password added succesfully but defaults to autologin

[yocto] Auto-mount causing "transport endpoint is not connected error"

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

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

[yocto] Enhancements/Bugs closed WW40!

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

[yocto] inode mismatch

[yocto] are there any plans for a RISC-V reference board?

Re: [yocto] are there any plans for a RISC-V reference board?

18 matches

Site Navigation

Mail list logo

Footer information