linux/poky.git/meta-yocto-bsp, branch walnascar

genericarm64.conf: increase INITRAMFS_MAXSIZE

2025-06-05T16:18:43+00:00

Since pmem kernel drivers were enabled as modules, the initrd size limit is hit. On genericarm64 all kernel modules and some firmware files get installed to initrd by default which make the thing large. I'm working on patches to reduce the kernel drivers installed to initrd and to make the kernel in general more modular (btrfs 5 Mb etc built into kernel by default). For now just increase the size limit to unblock genericarm64 builds and testing. Fixes: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15833 (From meta-yocto rev: c8b151d2d7879c2b1276824444a963a59dfcf240) Signed-off-by: Mikko Rapeli Signed-off-by: Richard Purdie (cherry picked from commit 09bef6a491c087f0f0371874e759aae08a720c4e) Signed-off-by: Steve Sakoman

genericarm64: add ttyPS1 for KV260

2025-04-23T18:49:06+00:00

The AMD KV260 has a serial console on ttyPS1, so until we can dynamically detect the console under sysvinit we can add it to SERIAL_CONSOLES so this platform has a working console when not running systemd. (From meta-yocto rev: 467b6d77e50f92bee3c8f7ca928bd70758bab457) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

linux-yocto: revert omap8250 power management changes on genericarm64

2025-02-18T11:08:36+00:00

The genericarm64 machine sets SERIAL_CONSOLES to a number of potential devices: SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0 115200;ttyS0 115200;ttyS1 115200;ttyS2" With sysvinit this turns into getty lines in inittab, and with systemd the systemd-serialgetty recipe creates explicit units to spawn gettys. This worked fine with 6.6, but since "serial: 8250_omap: Drop pm_runtime_irq_safe()"[1] in 6.7 onwards we see kernel hangs: BUG: scheduling while atomic: getty/957/0x00000002 Call trace: dump_stack+0x1c/0x30 __schedule_bug+0x60/0x90 __schedule+0x83c/0xcf8 schedule+0x40/0x158 schedule_timeout+0xb0/0x1b0 wait_for_completion_timeout+0x84/0x188 ti_sci_set_device_state+0x134/0x220 ti_sci_cmd_get_device_exclusive+0x24/0x40 ti_sci_pd_power_on+0x34/0x68 [ti_sci_pm_domains] _genpd_power_on+0xa4/0x178 genpd_power_on+0xb4/0x190 genpd_runtime_resume+0xc8/0x260 __rpm_callback+0x54/0x200 rpm_callback+0x78/0x90 rpm_resume+0x420/0x690 __pm_runtime_resume+0x5c/0xb0 omap8250_set_mctrl+0x38/0xe0 [8250_omap] serial8250_set_mctrl+0x2c/0x60 uart_update_mctrl+0x98/0x120 uart_shutdown+0x124/0x180 uart_hangup+0x7c/0x180 __tty_hangup.part.0+0x408/0x440 tty_vhangup_session+0x24/0x40 disassociate_ctty.part.0+0x48/0x1b0 disassociate_ctty+0x30/0x48 (full backtrace elided) With many thanks to TI, my understanding is that it was determined that the problem here is that we have a getty connected to ttyS1 which is actually the expansion port uart and on the BeaglePlay wired up to the wifi controller's debug port. The getty receives noise it doesn't know what to do with, and at some point the power management code does a suspend/result cycle of the device. The serial drivers assume that child nodes use the serdev driver and they manage runtime_pm, but the getty opening the tty breaks a series of bad assumptions in the drivers. So, there are two bugs: 1) The kernel shouldn't crash if this tty is opened 2) The only serial port for a console on the BeaglePlay is ttyS2, despite others existing. TI are looking at (1) and other patches to follow will deal with (2). Until one of these is resolved entirely, reverting this change to power management stops the crashes. [ YOCTO #15704 ] [1] linux 8700a7ea5519fb0b3bad2362adfeac358c2119ce (From meta-yocto rev: 49519579f8b6bacf181d2f00bdd256e71d0880c4) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

yocto-bsp: drop linux-yocto 6.6 bbappend

2025-02-11T11:44:20+00:00

6.6 has been dropped from OE core master in preparation for the LTS release, so we drop our reference BSP bbappend as well. (From meta-yocto rev: e40fb898889254c461b4049d5e457b2270c659c9) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

genericarm64.conf: allow overriding u-boot and qemuboot variables

2025-02-11T11:44:19+00:00

Assignment in machine config can not be overwritten in local.conf because former is evaluated later than latter. Use ?= conditional assignment for u-boot and qemuboot variables so that they can be overwritten in local.conf if a different test setup is wanted for kernel, initrd and rootfs built for genericarm64 machine config. (From meta-yocto rev: fbb2b2a2dcfd4dd990071d4d73b149d4099a36ab) Signed-off-by: Mikko Rapeli Signed-off-by: Richard Purdie

yocto-bsp: drop genericarm64 SRCREV

2025-01-11T18:34:30+00:00

The OEcore SRCREVs now contain the fixes this machine specific SRCREV was added to incorporate. Dropping it to ensure that all reference boards are at the same source and configuration level. (From meta-yocto rev: 11d690061d67ab0f84265d609e129d8717e88bcb) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

yocto-bsp: Bump the default kernel to v6.12 for x86 machines

2024-12-15T11:09:42+00:00

(From meta-yocto rev: 7a65cd769151a817a771cce6ee70b5437fca60e5) Signed-off-by: Kevin Hao Signed-off-by: Richard Purdie

yocto-bsp: Bump the default kernel to v6.12 for beaglebone

2024-12-15T11:09:42+00:00

There have been no specific patches on beaglebone branche for many years, so I have decided to switch to using the base branch for this machine. This approach eliminates the need to adjust the corresponding SRCREV_machine and LINUX_VERSION with each stable kernel version bump. (From meta-yocto rev: 1570badbf93511f370614c21ccd967af28549b2c) Signed-off-by: Kevin Hao Signed-off-by: Richard Purdie

linux-yocto: enable linux 6.12 for genericarm64

2024-12-13T15:20:23+00:00

Add a bbappend so that genericarm64 can use 6.12.x. We explicitly set the SRCREV to incorporate some required config fixes that have not been integrated into the oe-core recipe at this point in time. (From meta-yocto rev: 3b6d0ee17ac834a0521223eef67db3d39aaa1b78) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

yocto-bsp: drop 6.10 bbappend

2024-12-12T12:32:44+00:00

The 6.10 reference kernel has been removed from OE core, so we drop our bbappend. (From meta-yocto rev: 2a138947d9b2347873db6c9e568d41f9a58f75f7) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie