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

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

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

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

[yocto] continuous security updates for the Linux system

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

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

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

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

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

[yocto] Password added succesfully but defaults to autologin

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

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

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):

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

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

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

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 # #

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

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

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

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

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

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:

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

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

[yocto] Enhancements/Bugs closed WW40!

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 *

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

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

Re: [linux-yocto] [PATCH] nxp-imx7: enable CONFIG_I2C kernel config explicitly

merged. Bruce In message: [PATCH] nxp-imx7: enable CONFIG_I2C kernel config explicitly on 09/10/2023 Meng Li wrote: > The CONFIG_I2C kernel config is not enabled if setup WRLinux project > with nodistro parameter, so add it into BSP cfg file. > > Signed-off-by: Meng Li > --- >

Re: [linux-yocto][linux-yocto v6.1] fix patch for marvell cn96xx

In message: [linux-yocto][linux-yocto v6.1] fix patch for marvell cn96xx on 09/10/2023 Ruiqiang Hao wrote: > Hi Bruce, > > Please help to merge this patch into our linux-yocto repo. > > repo: > linux-yocto > branch: > v6.1/standard/cn-sdkv5.15/octeon >

Re: [linux-yocto][linux-yocto v6.1] fix patch for marvell cn96xx

The condition being removed wasn't in exactly the same place on the -rt brances, so I fixedup the patch when applying it. Both branches should be fixed. I just realized that RT branch and Standard branch are different when processing merges, this patch is not applicable on the RT branch. I

[linux-yocto][v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc & v6.1/standard/nxp-sdk-6.1/nxp-soc][PATCH 1/1] ARM: imx: use raw_spin_lock instead of spin_lock

Use raw_spin_lock instead of spin_lock, this patch fixes the following warning: Hardware name: Freescale i.MX7 Dual (Device Tree) unwind_backtrace from show_stack+0x18/0x1c show_stack from dump_stack_lvl+0x40/0x4c dump_stack_lvl from __might_resched+0x140/0x1b4 __might_resched from