

RSS Bot
Bot-
Posts
4209 -
Joined
-
Last visited
Never
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by RSS Bot
-
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 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
-
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
-
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