RSS Bot

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

Description tiny housekeeping. update major_minor to match collabora tree View the full article

Description This reverts https://github.com/armbian/build/pull/5615 Need to split and fix. View the full article

Backport DTS/DTSI changes from linux-6.4.y to 6.1.y Add meson64-reboot driver to all boards Add board: ODROID N2L Add uart_A uart_AO_B uart_B uart_C where appropriate U-Boot v2023.07.02: ODROID N2/N2L/N2Plus/C4 Meson64-reboot driver: (source: tobetter) While the current meson64-reboot driver is cleaner and doesn't depend on modding other kernel sources, its functionality leaves much to be desired. One example can be found in the ODROID C4. Using the current driver, the board will not properly power off, leaving the POWER LED still on. The new driver powers off the unit completely. Fan control: (ODROID N2L/N2PLus) Added service and script for controlling the trip point. fanctrl: arguments: 65 55 45 35 25 menu run ┌──┤ Fan Control ├──┐ │ │ │ 6) 65°C │ │ 5) 55°C │ │ 4) 45°C │ │ 3) 35°C │ │ 2) 25°C │ │ E) Exit .. │ │ │ │ │ │ <Ok> │ │ │ └───────────────────┘ NOTES: (N2L/HC4): I do not own the units so I can't run tests. 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

khadas-vim4: add modprobe config to avoid kernel panic during ISP firmware loading khadas-vim4: add modprobe config to avoid kernel panic during ISP firmware loading See https://armbian.atlassian.net/browse/AR-1801?focusedCommentId=11995 View the full article

rockpro64: bump ATF to lts-2.8.8 rockpro64: bump ATF to lts-2.8.8 View the full article

Description irony of using bleeding edge uboot was to take advantage of the native rock 4SE support in uboot....which is broken. using generic rockpi-4i uboot defconfig for now.. which works.. leaving placeholder so that we can one day, embrace what is pure. View the full article

Description Ordered this WiFi key and it was not working out of the box. Adding pids (and also for Netgear variant) helps that it works OOB. Jira reference number AR-1803 How Has This Been Tested? [x] Build and booted USB wireless device (on Odroid N2 https://paste.armbian.com/onulekucil) 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] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Firmware update. Jira reference number AR-1700 How Has This Been Tested? [ ] Build test as HW is n/a 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 -- remember its not rockpi 4SE its rock 4SE now that RK3399-T friendly ddr blobs have been added, lets given this a discrete config..... and use mainline uboot with an official uboot defconfig. View the full article

odroidm1: de-infest Petitboot 🔥 use Kwiboo's 2023.10 u-boot; UMS works; bump kernel to 6.5-rcX odroidm1/edge (rk3568-odroid): bump to 6.4.y, update config, rebase patches to 6.4.10 odroidm1/edge (rk3568-odroid): bump to 6.5-rc6; manually fix RK808 breakage in .config; rebase patches add patch to remove Petitboot-mandated MTD partitions this way we have access to the full flash, and can write our own u-boot to it rebase all patches odroidm1/edge (rk3568-odroid): drop 6.3 and 6.4 patches odroidm1: de-infest Petitboot 🔥 use Kwiboo's 2023.10 u-boot; UMS works using Kwiboo's rk3568-2023.10 branch with BINMAN-handled blobs patches (defconfig unless indicated): boot usb first (rockchip-common) blink leds & keep red one one on preboot change usb_host0_xhci to otg (u-boot dtsi) enable DM_GADGET, UMS 🔥 and RockUSB usage instructions: build & burn image to SD card insert SD card into board hold the recovery (RCY) button and power on the board watch board boot de-infest Petitboot: use armbian-install to install bootloader to MTD if you don't, you'll need to hold the recovery button every boot optionally: use armbian-install to install OS to eMMC/NVMe/USB power-off board remove SD card (new u-boot always boots SD first!) boot into your newly de-infested machine boot order: USB, SD, MMC, NVME, SCSI de-infested machine can now boot (directly) from USB/SATA/NVMe: Armbian UEFI-arm64 Fedora 38 aarch64 Talos arm64 others... extra: new u-boot by Kwiboo (with GMAC patches) gives us stable MAC address although it is based on cpuid#, doesn't match the HK sticker on the board odroidm1: update DDR/BL31 blobs (this depends on https://github.com/armbian/rkbin/pull/20) View the full article

Description Enabled compilation options for the USB interface MT7921 chip driver module mt7921u. Need to work with the corresponding firmware https://github.com/armbian/firmware/pull/57 . How Has This Been Tested? [x] built and tested on nanopi-r4s The Wi-Fi is working well, Bluetooth was not tested. 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description bump atf to LTS v2.8 for Rockchip64 How Has This Been Tested? Rockpro64 boots 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

Update maintainers and board status synced status from the database rename to .csc where we don't have anyone If you want to become a board maintainer, adjust data here. Ref: Board Maintainers Procedures and Guidelines View the full article

Description I thought edge would carry the fixes forward, missed 6.4 folder. How Has This Been Tested? Carryover from 6.3 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 Debian moved riscv64 into 1st class so exceptions are not needed. But ports repository is still needed in the lists file as they didn't manage to move everything. Jira reference number AR-1824 How Has This Been Tested? [x] Generated image with clean rootfs Armbian_23.08.0-trunk_Star64_sid_edge_5.15.0.img 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] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

odroidm1: de-infest Petitboot 🔥 use Kwiboo's 2023.10-rc2+gmac u-boot odroidm1/edge (rk3568-odroid): bump to 6.4.y, update config, rebase patches to 6.4.10 odroidm1/edge (rk3568-odroid): bump to 6.5-rc6; manually fix RK808 breakage in .config; rebase patches add patch to remove Petitboot-mandated MTD partitions this way we have access to the full flash, and can write our own u-boot to it rebase all patches odroidm1/edge (rk3568-odroid): drop 6.3 and 6.4 patches odroidm1: de-infest Petitboot 🔥 use Kwiboo's 2023.10-rc2+gmac u-boot using Kwiboo's rk3568-2023.10-gmac branch with BINMAN-handled blobs patches: boot usb first preboot pci/usb enum/scan usage instructions: build & burn image to SD card insert SD card into board hold the recovery (RCY) button and power on the board watch board boot de-infest Petitboot: use armbian-install to install bootloader to MTD if you don't, you'll need to hold the recovery button every boot optionally: use armbian-install to install OS to eMMC/NVMe/USB power-off board remove SD card (new u-boot always boots SD first!) boot into your newly de-infested machine boot order: USB, SD, MMC, NVME, SCSI (SATA) de-infested machine can now boot (directly) from USB/SATA/NVMe: Armbian UEFI-arm64 Fedora 38 aarch64 Talos arm64 others... extra: new u-boot by Kwiboo (with GMAC patches) gives us stable MAC address although it is based on cpuid#, doesn't match the HK sticker on the board odroidm1: update DDR/BL31 blobs; cleanup old Petitboot stuff this depends on https://github.com/armbian/rkbin/pull/20 View the full article

Description The command takes long time to continue and it makes it seem like the build halted, so this adds an alert to mitigate this --> (3) COMMAND: fakeroot dpkg-deb -b -Znone /armbian/.tmp/work-cfd2d6ad-1f9b-473e-80e7-cbcf9d157c68/uboot-Bd1Ms /armbian/output/packages-hashed/gl> dpkg-deb: building package 'linux-u-boot-sipeed-lichee-pi-4a-current' in '/armbian/output/packages-hashed/global/linux-u-boot-sipeed-lichee-pi-4> --> (372) INFO: Built u-boot deb OK [ linux-u-boot-sipeed-lichee-pi-4a-current 2022.07-Se092-P0000-H6f49-V9cb9-B9963-R448a ] Jira reference number [AR-9999] How Has This Been Tested? Builds on my end 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