RSS Bot

Description Created udev config for renaming interfaces to WAN, LAN1, LAN2 Created device tree overlay rockchip-nanopi-r5s-leds for enabling front panel status LED's for NICs. enabled by default How Has This Been Tested? Built image. Leds work when cable plugged in. interface names are friendly root@nanopi-r5s:~# ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wan: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 link/ether 12:ad:f7:2a:2f:a3 brd ff:ff:ff:ff:ff:ff altname end0 3: lan1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether c2:3b:8d:34:73:49 brd ff:ff:ff:ff:ff:ff altname enp1s0 4: lan2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether a6:5c:a3:ad:4c:33 brd ff:ff:ff:ff:ff:ff altname enP1p1s0 `` # 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

After rtw_usb_alloc_rx_bufs() has been called rx urbs have been allocated and must be freed in the error path. After rtw_usb_init_rx() has been called they are submitted, so they also must be killed. Add these forgotten steps to the probe error path. Besides the lost memory this also fixes a problem when the driver fails to download the firmware in rtw_chip_info_setup(). In this case it can happen that the completion of the rx urbs handler runs at a time when we already freed our data structures resulting in a kernel crash. This has been applied to wireless-next https://lore.kernel.org/linux-wireless/8b4b4228bfd140119665417137a087ea@realtek.com/T/#t [ ] 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 I had kept it back because I wasn't sure about what values to use for CONFIG_DRAM_SUN50I_H616_DX_ODT, CONFIG_DRAM_SUN50I_H616_DX_DRI, CONFIG_DRAM_SUN50I_H616_CA_DRI and CONFIG_DRAM_SUN50I_H616_TPR10. I found them on BigTreeTech's u-boot repository https://github.com/bigtreetech/u-boot/blob/v2023.07-cb1/configs/bigtreetech_cb1_defconfig 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] 2023.07.02 uboot builds successfully for BigTreeTech CB1 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

thinkpad-x13s: move image customizations to bsp-cli thinkpad-x13s: move image customizations to bsp-cli should result in the same, except we can now update stuff via the bsp-cli pkg View the full article

Description They don't apply as they have been merged upstream and build fails. View the full article

odroidm1: really fix flashcp --partition non-usage for old mtd-utils (bullseye etc) odroidm1: really fix flashcp --partition non-usage for old mtd-utils (bullseye etc) we should probably refactor this into a shared library's functions... flashcp --partition is much more efficient than just dd'ing to mtdblockX but only supported on bookworm+ / jammy+ View the full article

pipeline: add userspace inventory capabilities config_post_main: sanity checks for RELEASE (vs ARCH) and RELEASE+DESKTOP_ENVIRONMENT (vs ARCH) the interactive menus didn't allow interactive users to select invalid combinations... ... but if specified directly on cmdline, no checks were done at all. introduce exit_with_target_not_supported_error(), which is just exit_with_error (code 43) but with code 44 this way the targets pipeline can just warn instead of break; sometimes it's easier multiplying matrixes and skipping the few that can't be built rpi4b: use exit_with_target_not_supported_error() instead of exit_with_error() if RELEASE is not supported pipeline: add userspace inventory capabilities digs into config/distributions and config/desktops for info this produces output/info/all_userspace_inventory.json this is now passed down to the targets-compositor in cli-jsoninfo targets-compositor now accepts userspace: as items-from-inventory extra: add targets-composed CLI command, to stop after targets-compositor pipeline: handle exit_with_target_not_supported_error() (retcode 44) as warning and not error split errors and warnings into multiple lines, so a bit easier to see in the logs what the real error was also turn down a few spurious warnings to debugs pipeline: use ncores * 4 for info gathering View the full article

Description This brings early support for Linux kernel v6.5 for allwinner boards. Following patches are changed Megous patches: disabled patches.megous/video-fbdev-eInk-display-driver-for-A13-based-PocketBooks.patch to prevent build failure. Will work on re-enabling the same Fixes patches: disabled Fix-depends-only-ARM-eInk-display-FB.patch as it changes code introduce by patch disabled above Armbian patches: disabled drv-clk-sunxi-ng-ccu-sun50i-a64-revert-ccu-Pinebook-A64.patch due to patch application failure. Will check if its still needed. Need help from someone who has a PInebook A64 for the same. removed drv-pmic-add-axp313a.patch as it is upstreamed reworked the overlay support patches to reuse the upstream dtbo support. Due to this rework, overlay patches are updated to use dtso as the file extension Config change: Enabled CW1200 wireless driver as this might bring support for xradio xr819 due to patches from megous kernel 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 succeeds 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 Fixed driver compilation for RTL8811CU and RTL8723CS on 6.5 kernel 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 creating build for nanopiduo2 with 6.1, 6.4 and 6.5 kernels to make sure build succeeds 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

The recommended name for enable GPIOs property in regulator-gpio is enable-gpios. This is also required by bindings: meson-g12b-bananapi-cm4-cm4io.dtb: regulator-vddio-c: Unevaluated properties are not allowed ('enable-gpio' was unexpected) 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

Set in the captivating city of Berlin, All Systems Go! is ready to explore foundational user-space Linux technologies after a 4-year hiatus. View the full article

Description Mainline mirror is not supported since armbian-next. Current code support google, tuna and bfsu as mainline kernel source: https://github.com/armbian/build/blob/main/lib/functions/configuration/main-config.sh#L170-L187. We have to use kernel source from git.kernel.org to support curl. 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 with MAINLINE_MIRROR=tuna 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 nanopi-r5s device tree now in 6.5 and uboot RC. borrowing odroid-m1 family for now. verified working. NVME needs attention. View the full article

Description Patch tzselect text to be more neutral. Jira reference number AR-1826 How Has This Been Tested? Text change only. Manual test of execution. Checklist: [x] My code follows the style guidelines of this project View the full article

Description Dropped support for host OSes that can not build crust Jira reference number AR-1811 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 add armsom-w3.wip github: https://github.com/ArmSoM/armsom-w3-bsp wiki: http://wiki.armsom.org/index.php/ArmSoM-w3 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] 2.5Gb Network r8125 ok [x] Headphone ok [x] usb 2.0 * 2 ok [x] typec ok [x] usb3.0 ok [x] hdmi tx * 2 ok [x] 40pin-Header ok [x] LED ok [x] RTC ok [x] debug ok [x] Fan ok [x] M2 E key ok [x] MIPI CSI ok [x] MIPI DSI ok [x] POE ok 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Enabled CONFIG_MT7915E on all kernels. Requires corresponding firmware to work https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/mediatek Jira reference number AR-1817 https://armbian.atlassian.net/browse/AR-1817 [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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

In Linux, the Industrial Input/Output subsystem manages devices like Analog to Digital Converters, Light sensors, accelerometers, etc. On the other hand, the Input subsystem handles keyboards, mice, touchscreens, and any device that has a human interface. View the full article

Description We had autofocus patches for ov5640 camera in allwinner current and edge kernel that were disabled due to patch application failure. This PR fixes the patch application failure and re-enables 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] Checked that patches applies on 6.4 kernel [X] Checked that patches applies on 6.4 kernel [X] Tested that autofocus works with 6.1 kernel on NanoPi Duo2 The following procedure was used to test autofocus with 6.1 kernel Compiled and enabled device tree overlay for ov5640 camera taken from the forum post Took the ov5640_af_2.bin autofocus firmware and placed it in /lib/firmware directory with filename ov5640_af.bin Ran the following commands to start a camera stream # v4l2-ctl --device /dev/video1 --set-fmt-video=width=640,height=480,pixelformat=YUYV # media-ctl --device /dev/media1 --set-v4l2 '"ov5640 0-003c":0[fmt:YUYV8_2X8/640x480]' # ffmpeg -i /dev/video1 -q 10 -pix_fmt yuv420p -video_size 640x480 -r 5 -listen 1 -f avi http://192.168.29.128:8080/stream& # v4l2-ctl --device /dev/v4l-subdev0 -c auto_focus_start=1 Verified that autofocus firmware loaded successfully from dmesg output # dmesg | grep ov5640 [ 8.022346] ov5640 0-003c: supply DOVDD not found, using dummy regulator [ 8.022698] ov5640 0-003c: supply AVDD not found, using dummy regulator [ 8.022928] ov5640 0-003c: supply DVDD not found, using dummy regulator [ 2808.787047] ov5640 0-003c: firmware upload success [ 2808.787609] ov5640 0-003c: fw started after 0 ms verified that camera lens moves to focus when moving the subject 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 legacy - 5.15.126 -> 5.15.127 current - 6.1.45 -> 6.1.46 edge - 6.4.10 -> 6.4.11 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] Booted legacy, current and edge images on Orange Pi Prime (sun50i H5) [X] Booted legacy, current and edge images on NanoPi Duo2 (sun8i H3) 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

odroidn2l: add board file for ODROID N2L; on meson64 edge; add N2L-specific FIP handling to g12b odroidn2l: add board file for ODROID N2L; on meson64 edge; add N2L-specific FIP handling to g12b current (6.1) does not yet carry the DTB u-boot (up to at least 2023.10-rc2) does NOT have ADC detection for N2L, so force the DTB meson-g12b.conf: add a specific if for odroidn2l before the odroidn2* for FIP blobs View the full article

bsp-cli: allow hooks to cleanly add code to the bsp-cli postinst; fix helios4 to match bsp-cli: allow hooks to cleanly add code to the bsp-cli postinst; fix helios4 to match bsp-cli: postinst is now generated after the hooks are run hooks are allowed to append to postinst_functions array hooks are not allowed to modify DEBIAN/postinst directly anymore (it won't even be there) rewrite the postinst stuff in helios4's family_tweaks_bsp() to use new way introduce add_file_from_stdin_to_bsp_destination(), a helper for easy heredoc-based adding of files to bsp-cli First and only argument is the destination path, relative to the root of the package -- do NOT include $destination -- it is already included. Containing directory, if any, is created automatically (no more "mkdir -p x; cp y x/z") The full path (including $destination) is set in $file_added_to_bsp_destination, declare in outer scope to get it if needed. View the full article

debian: add Trixie (Debian 13, testing) csc target & build host debian: add Trixie (Debian 13, testing) csc target & build host Trixie, like Bookworm and Sid, does not have python2 anymore View the full article

rootfs-image: don't fail synaptic/xapian index creation if update-apt-xapian-index is not there rootfs-image: don't fail synaptic/xapian index creation if update-apt-xapian-index is not there allows us to remove_package apt-xapian-index synaptic in userpatches View the full article

RFC: partitioning: stop disabling 64bit and metadata_csum for mkfs.ext4 RFC: partitioning: stop disabling 64bit and metadata_csum for mkfs.ext4 this has been a contention point for many years View the full article