RSS Bot

Changes to be committed: modified: VERSION Description It bugs me that nightlies are at 24.5 but main is still at 24.2 Jira reference number [AR-9999] Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code View the full article

Description When booting from UHS-I cards on VIM4 and VIM1S, mine was Samsung EVO Plus card (MB-MC64KA), booting only worked 1 out of 5 reboots. Other times the device either tried booting from EMMC or from SPI flash. The following logs appear when booting doesn't work from sdcard mmc0 is current device sd: resp crc error, cmd17, status=0x1ff2400 ** Can't read partition table on 0:0 ** sd: resp crc error, cmd17, status=0x1ff2400 ** Can't read partition table on 0:0 ** ** Invalid partition 1 ** Using git bisect brought me to bfa451f commit and reverting the same solves the issue. Booting now works reliably from SD card every time I restart the same. Jira reference number AR-2070 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Tested rebooting multiple times when booting from sdcard on VIM4 Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Enable uboot gpio command. This would allow to set up rk3318-box'es LED display in custom uboot script. For example, to show "boot", this snippet can be added (gpio pins and letter codes should be adjusted for different STB/LCD models): FD650_MODE_WRCMD='0 1 0 0 1 0 0 0' DISPON='0 0 0 0 0 0 0 1' FD655_BASE_ADDR='0 1 1 0 0 1 1 0' Z='0 0 0 0 0 0 0 0' B='0 1 1 0 0 1 1 1' O='0 1 1 0 0 0 1 1' T='0 1 0 0 0 1 1 1' setenv d0 gpio clear C22 setenv d1 gpio set C22 setenv LC gpio clear C19 setenv HC gpio set C19 setenv send 'run d0 LC; for b in $cmd; do run d$b HC LC; done; run HC d1' cmd="$FD650_MODE_WRCMD 1 $DISPON 1" run send cmd="$FD655_BASE_ADDR 1 $Z 1 $B 1 $O 1 $O 1 $T 1" run send How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Compile and boot rk3318-box Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

mekotronics 3588: fix entering RK LOADER mode by keeping the RECOVERY button pressed during boot mekotronics 3588: fix entering RK LOADER mode by keeping the RECOVERY button pressed during boot those patches are a mess, hopefully I'll find time to squash soon mekotronics 3588: squash u-boot patches same as before but not touching the same file twice+ View the full article

artifact-uboot: include BOOTCONFIG in u-boot artifact version hash artifact-uboot: include BOOTCONFIG in u-boot artifact version hash HOW did we get this far without this? should cause rebuild of all u-boots, hopefully View the full article

Collabora's engineers presented six talks over the course of the weekend, with topics including a review of recent improvements to GStreamer, a look at the state of video offloading on the Linux desktop, and more. View the full article

Build the Kernel DRDB as a module in linux-mvebu-config current and edge. close #6268 View the full article

Description Bump the K2 to u-boot 2024.01, let's try to get old u-boots out of our hair. How Has This Been Tested? builds and boots, everything works. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description This patch fixes the high interrupt issue on the Orange Pi5 Plus. Forum discussion available here. https://forum.armbian.com/topic/33360-orangepi-5-plus-rtc-hym8563-irq-issue/ The patch also adds poweroff support. Right now the Orange Pi 5 Plus just reboots when poweroff or shutdown -h now is executed. Third fix of the patch is to correct gpio_pwrctrl1 typo. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Build command ./compile.sh BOARD=orangepi5-plus BRANCH=edge RELEASE=trixie KERNEL_CONFIGURE=no BUILD_MINIMAL=yes BUILD_DESKTOP=no COMPRESS_OUTPUTIMAGE=img BOOTSIZE=512 [x] Booted the image and went through the first-run wizard [x] Checked the system via top and procinfo and monitored the cpu usage and interrupts Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description This PR adds support for the Texas Instruments SK-AM68 and SK-AM69 boards. Notable features of SK-AM68 board: 16GB LPDDR4‐4266 with support for inline error correction code (ECC) DisplayPort 4K resolution with MST support and HDMI Two CSI-2 ports compatible with Raspberry Pi 8 TOPS deep-learning performance and hardware-accelerated edge AI Three USB 3.0 Type A ports, one USB 3.0 Type C port Gigabit Ethernet and 4x CAN-FD Headers One M.2 key M connector Notable features of SK-AM69 board: 32GB LPDDR4‐4266 with support for inline error correction code (ECC) DisplayPort 4K resolution with MST support and HDMI Three CSI-2 ports compatible with Raspberry Pi 32 TOPS deep-learning performance and hardware-accelerated edge AI Three USB 3.0 Type A ports, one USB 3.0 Type C port Gigabit Ethernet and 4x CAN-FD Headers One M.2 key E connector and one M.2 key M connector Further details like features, schematics and purchase links can be found on the board page: SK-AM68 SK-AM69 Note: To support SK-AM69 board, we had to switch U-Boot source for K3 family devices to ti-u-boot:2023.04 (commit 1), since boot configs for SK-AM69 board has not been upstreamed yet. How Has This Been Tested? First, we verified that the changes introduced do not deprecate any existing board support by: [ ] Build and boot SK-AM62B Jammy CLI/Standard on Edge(v6.6) kernel [ ] Build and boot SK-AM64B Jammy CLI/Standard on Current(v6.1) and Edge(v6.6) kernels [ ] Build and boot SK-TDA4VM Jammy CLI/Standard on Current(v6.1) and Edge(v6.6) kernels Further, the functionalities of new boards were tested by: [ ] Build and boot SK-AM68 Jammy CLI/Standard on Current(v6.1) and Edge(v6.6) kernels [ ] Build and boot SK-AM69 Jammy CLI/Standard on Current(v6.1) and Edge(v6.6) kernels [ ] Gbit Ethernet works [ ] USB 3.0 ports work Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Engineers have widely adopted GStreamer to build video analytics pipelines, and while many companies have indeed built their machine learning analysis framework around GStreamer, no one had made the effort to contribute upstream, until now. View the full article

Description Z96a is a cloud laptop designed by Sunniwell.co from China, using rk3568b2 chip, 4g memory, 32g emmc, 1080p screen. Because of the manufacturer's special design, such as power chip rk817 etc.. drivers needs to be patched, so a new board family needs to be created. After creating a new board family, Added code will not affect the armbian historical or other boards. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Test A: Image which compiled by new code has been flashed in z96a, and everything works fine. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description The idea is to generate output/git_sources.json file that will contain url, branch and commit hash combo. The easiest way to generate file for all devices is to run ./compile.sh targets. Then at the time of release we will copy the output/git_sources.json file to config/sources/git_sources.json. Once the file is copied, the hash information from the file will be used to fetch resources for git repositories where branches are specified instead of tags or commits. There can be other ways to do this as well. I am just too tired to experiment more on the same. Raising it to be a communication starter. I have also added the json file that I have generated today. I think it can be used to freeze sources for 24.02 release. Hence I have raised this PR again v24.02 branch How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [ ] Tested output/git_sources.json file generation using ./compile.sh targets command [ ] Copied generated file to config/sources and modified it to use a different commit hash for 6.6 kernel. Then tested that kernel is being built from that hash instead of the latest available 6.6 kernel. Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Patch for #6268 View the full article

Description Refresh kernel config to match fenix 1.6.4. This enables CONFIG_W1_SLAVE_THERM which was enabled on fenix as well. On bookworm, and also possibly on newer version of ubuntu, systemd starts all of the services present on first boot. Making the /etc/machine-id file empty ensures that machine id is still initialized on first-boot, while other services are not started automatically. This also seems to be observed by alex3d as well as reported in #6264 . However I was not able to reproduce the same issue on any of the other boards I have. Hence I have currently only handled it for meson-s4t7 family. This also makes the previous hack of masking chrony-wait.service unnecessary and hence I have reverted that change. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Tested on bookworm xfce image on vim1s. Lightdm no longer pops up before first login setup and also first login doesn't starts immediately as chrony-wait service is no longer started. Checklist: [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Continuing our Kernel Integration series, we're excited to introduce DRM-CI, a groundbreaking solution that enables developers to test their graphics subsystem patches across numerous devices within the community's shared infrastructure. View the full article

Description This commit re-applies previously utilized 'HACK' patches aimed at addressing eMMC phase clock configuration issues exclusively on JetHub D1, D1+, and H1 devices. No impact on other devices. Jira reference number AR-2049 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] D1+/H1 boots correctly Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Jira reference number AR-2050 How Has This Been Tested? Boots current and edge kernel from SDcard images Built-in WiFi works in both cases However, board will not allow clocking >1.0Ghz Built-in WiFi antenna is very weak Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [ x ] Generate current image [ x ] Generate edge image Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Removed slick-greeter on desktop environments that have gdm3 or sddm installed. Installing slick greeter installs back lightdm as well. On vim4 during first boot with gnome images, lightdm was getting started immediately on boot hiding the firstlogin setup screen. This fixes the same How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Tested bookworm gnome image on vim4 Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Removed lcd node when screen is not attached. Turns out the Khadas u-boot has some code hidden deep within pxe.c file to enable and disable lcd screen. As we don't use extlinux for vim1s and vim4, that doesn't get executed for us leaving the device to detect ghost screens. Hence copied the code to bootscript in order to disable the lcd screens when they are not really present. This makes the vim4 and vim1s a lot more responsive. Also fixes issue where we can't login to gnome because login screen was being rendered on non-existent lcd screen. Fixed issue that prevented armbian-bsp-cli package for meson-s4t7 family to uninstall because of the added /etc/initramfs-tools/modules file. As this required custom code to be added in the postrm script of the package, I have added support for the same in armbian-bsp-cli package similar to how things worked for postinst script. Disabled chrony-wait service as it on meson-s4t7 devices as it was causing firstlogin to get stuck for 4 minutes. I had to mask it as its not really enabled when hook executes and gets enabled sometime later (not really sure when, was not able to track that down). How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Tested with Debian gnome bookworm image on VIM4 Checklist: [ ] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description stmmac ethernet driver is in use on all rockchip SoCs; its statistics system has been revised on kernel 6.6, but something is not working correctly right now on 32 bit platforms and a lock contemption happens very often when an userland process tries to read the statistics of the ethernet device. One of the most common victim is vnstat daemon, which often gets stuck hogging a cpu core and skyrocketing the average load. This also makes the whole kernel angry, RCU complains, processes hang, and so on... The patch provides a horrible workaround (remove the mutual exclusion in the reader) to fix the problem temporarely. This may break ethernet statistics that can supply freaky numbers, but at least fixes the problem for the time being. This is the kernel dump from the hung task: [ 696.614056] Sending NMI from CPU 0 to CPUs 2: [ 696.614071] NMI backtrace for cpu 2 [ 696.614079] CPU: 2 PID: 24 Comm: migration/2 Tainted: G C 6.6.12-current-rockchip #25 [ 696.614088] Hardware name: Generic DT based system [ 696.614092] Stopper: multi_cpu_stop+0x0/0x128 <- stop_machine_cpuslocked+0x118/0x180 [ 696.614113] PC is at rcu_momentary_dyntick_idle+0x44/0xc4 [ 696.614122] LR is at multi_cpu_stop+0xe4/0x128 [ 696.614130] pc : [<b0197d74>] lr : [<b01e03b4>] psr: 60070113 [ 696.614135] sp : f0889ed0 ip : 00000000 fp : f0889edc [ 696.614140] r10: 00000001 r9 : 00000000 r8 : 00000000 [ 696.614143] r7 : b1505058 r6 : f093dddc r5 : 00000001 r4 : f093ddf0 [ 696.614148] r3 : ee6b7598 r2 : 2aaeeb3c r1 : 00000000 r0 : 3d234000 [ 696.614153] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none [ 696.614160] Control: 10c5387d Table: 6f38806a DAC: 00000051 [ 696.614163] Backtrace: [ 696.614167] rcu_momentary_dyntick_idle from multi_cpu_stop+0xe4/0x128 [ 696.614181] multi_cpu_stop from cpu_stopper_thread+0x78/0x148 [ 696.614200] r10:f093ddf4 r9:ee6b606c r8:ee6b6074 r7:f093dddc r6:b01e02d0 r5:b9322b00 [ 696.614204] r4:ee6b6068 [ 696.614207] cpu_stopper_thread from smpboot_thread_fn+0xc0/0x15c [ 696.614223] r10:00000000 r9:00000002 r8:b15dd06c r7:00000001 r6:b9322b00 r5:b927dcc0 [ 696.614228] r4:00000000 [ 696.614231] smpboot_thread_fn from kthread+0xe8/0x104 [ 696.614246] r10:00000000 r9:f0821d8c r8:b927df00 r7:b927dcc0 r6:b014e190 r5:b9322b00 [ 696.614250] r4:b927de00 r3:00000000 [ 696.614254] kthread from ret_from_fork+0x14/0x28 [ 696.614263] Exception stack(0xf0889fb0 to 0xf0889ff8) [ 696.614269] 9fa0: 00000000 00000000 00000000 00000000 [ 696.614277] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 696.614283] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 696.614292] r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:b0149778 r4:b927de00 [ 696.615072] CPU: 0 PID: 1258 Comm: vnstatd Tainted: G C 6.6.12-current-rockchip #25 [ 696.615084] Hardware name: Generic DT based system [ 696.615091] PC is at stmmac_get_stats64+0x38/0x1a0 [ 696.615104] LR is at 0x1 [ 696.615115] pc : [<b098c188>] lr : [<00000001>] psr: 20000013 [ 696.615123] sp : f2d6dbf4 ip : f2d6dc20 fp : f2d6dc1c [ 696.615130] r10: 01000001 r9 : b96a0000 r8 : b633e4c8 [ 696.615138] r7 : 00000001 r6 : 00000000 r5 : b098c150 r4 : b96a3000 [ 696.615146] r3 : 000370b7 r2 : b96a2e48 r1 : f2d6dcc8 r0 : b96a0000 [ 696.615155] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none [ 696.615164] Control: 10c5387d Table: 6f08006a DAC: 00000051 [ 696.615170] Backtrace: [ 696.615180] stmmac_get_stats64 from dev_get_stats+0x44/0x168 [ 696.615203] r10:01000001 r9:b96a0000 r8:b633e4c8 r7:b1087af8 r6:b96a0000 r5:b098c150 [ 696.615210] r4:f2d6dcc8 [ 696.615216] dev_get_stats from dev_seq_printf_stats+0x34/0x178 [ 696.615241] r9:b96a0000 r8:b633e4c8 r7:f2d6de20 r6:00000000 r5:b633e4b0 r4:b96a0000 [ 696.615247] dev_seq_printf_stats from dev_seq_show+0x18/0x34 [ 696.615264] r5:00000000 r4:b633e4b0 [ 696.615271] dev_seq_show from seq_read_iter+0x3cc/0x50c [ 696.615288] seq_read_iter from seq_read+0x8c/0xbc [ 696.615310] r10:f2d6df68 r9:00000400 r8:00000000 r7:00004004 r6:00000400 r5:b2f38600 [ 696.615319] r4:f2d6df68 [ 696.615326] seq_read from proc_reg_read+0xb4/0xd8 [ 696.615347] r8:01c70fa0 r7:b2f38600 r6:00000000 r5:b0343274 r4:b9448c00 [ 696.615355] proc_reg_read from vfs_read+0xb8/0x2dc [ 696.615374] r10:b0395cb4 r9:b56ba040 r8:01c70fa0 r7:f2d6df68 r6:b2f38600 r5:00000400 [ 696.615381] r4:00000000 r3:f2d6df68 [ 696.615388] vfs_read from ksys_read+0x68/0xec [ 696.615406] r10:00000003 r9:b56ba040 r8:b01002c8 r7:00000000 r6:00000000 r5:b2f38600 [ 696.615415] r4:b2f38600 [ 696.615420] ksys_read from sys_read+0x10/0x14 [ 696.615436] r7:00000003 r6:a6f425a0 r5:000005e8 r4:01c571a8 [ 696.615443] sys_read from __sys_trace_return+0x0/0x10 [ 696.615457] Exception stack(0xf2d6dfa8 to 0xf2d6dff0) [ 696.615468] dfa0: 01c571a8 000005e8 00000004 01c70fa0 00000400 00000000 [ 696.615480] dfc0: 01c571a8 000005e8 a6f425a0 00000003 0000000a aed87604 00000000 00000000 [ 696.615489] dfe0: 00000003 aed874f0 a6d339a7 a6cadb06 Important notes: this issue may affect other 32 bit platforms as well! stmmac driver is in most SoCs supported by armbian, with the curious exception of Allwinner H3. Meson8/Meson8b (S802/S805) also use it and may be affected by the same problem. 64 bit platforms are not affected, since the locking mechanism is a no-op on 64 bit archs. Jira reference number AR-2048 - Celebrate 2^11th ticket :smile_cat: How Has This Been Tested? [x] Kernel 6.6 compiled and tested on live system [x] Kernel 6.7 compiled Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Turns out the Khadas u-boot has some code hidden deep within pxe.c file to enable and disable lcd screen. As we don't use extlinux for vim1s and vim4, that doesn't get executed for us leaving the device to detect ghost screens. Hence copied the code to bootscript in order to disable the lcd screens when they are not really present. This makes the vim4 and vim1s a lot more responsive. Also fixes issue where we can't login to gnome because login screen was being rendered on non-existent lcd screen. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Tested new build on vim4. Only hdmi was getting detected as expected as I don't have any lcd screens attached Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Jira reference number [AR-9999] How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Test A [ ] Test B Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Submitted upon request to make user's life easier Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Jira reference number [AR-9999] How to test $ git clone https://github.com/Kreyren/armbian-build-kreyren.git -b olimex-A20-OLinuXino-MICRO # Clone the source code with the specified branch # Change directory to the cloned repository $ ./compile.sh BOARD=olimex-a20-olinuxino-micro EXPERT=yes How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [ ] Test A [ ] Test B Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description thead: add pwm-fan support. How Has This Been Tested? [x] Successfully built. [x] System startup. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article