RSS Bot
Bot-
Posts
4252 -
Joined
-
Last visited
Never
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by RSS Bot
-
Description Bump rockchip64 edge kernel to 6.9. The same fix that has been proposed in https://github.com/armbian/build/pull/6690 has been ported here too and it works as well. Note: at the current status, helios64 board patches have been disabled because the base device tree does not apply on kernel 6.9. Jira reference number AR-2348 How Has This Been Tested? [x] Compiled successfully [x] Upgrade the kernel (and device trees obviously) on a rk3318/rk3328 live system, dtbo applies correctly and system boots fine [ ] Upgrade the kernel on a live rk3399 system Checklist: Please delete options that are not relevant. [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 View the full article
-
Description As per subject, bump rockchip 32 bit edge kernel to 6.9. Patches have been left as is because all of them applied fine, except for the device tree overlay compilation and installation. The device tree things have changed in 6.9 and the patch does not apply anymore. After some headeaches with the terrible makefiles, the second commit of this PR contains some hints on how I did the job and can serve as a icebreaker for other families perhaps. In particular: Some little accomodations in the overlay Makefile. the kernel makefile already supports dtbo files, but it wants the sources with .dtso extension, so all the device trees in overlay directory must be renamed with .dtso extension. This also greatly simplifies the existing general-add-overlay-support-compilation patch the kernel lacks support for .scr, but it is simple to add into scripts/Makefile.lib (see general-add-overlay-compilation-support.patch patch) architectures that have the flattening device tree directory kernel config option enabled (like rockchip), really flattens everything. Changing a line in scripts/Makefile.dtbinst strips away the base vendor name (rockchip/ in this case) and keeps the subdirectories (perhaps this can be generalized to work with all families, but makefile are awkward and I could not find a simple way to strip just the first directory entry in the path) With such changes, the dtb deb package contains this in the boot directory: paolo@armbian-build:~/armbian-build/output/debs/dtbs$ find boot/ | sort boot/ boot/dtb-6.9.3-edge-rockchip boot/dtb-6.9.3-edge-rockchip/overlay boot/dtb-6.9.3-edge-rockchip/overlay/README.rk322x-overlays boot/dtb-6.9.3-edge-rockchip/overlay/README.rockchip-overlays boot/dtb-6.9.3-edge-rockchip/overlay/rk322x-bt-8723cs.dtbo boot/dtb-6.9.3-edge-rockchip/overlay/rk322x-cpu-hs-lv.dtbo boot/dtb-6.9.3-edge-rockchip/overlay/rk322x-cpu-hs.dtbo boot/dtb-6.9.3-edge-rockchip/overlay/rk322x-cpu-stability.dtbo ...cut... boot/dtb-6.9.3-edge-rockchip/overlay/rk322x-fixup.scr ...cut... boot/dtb-6.9.3-edge-rockchip/overlay/rockchip-ds1307.dtbo boot/dtb-6.9.3-edge-rockchip/overlay/rockchip-fixup.scr boot/dtb-6.9.3-edge-rockchip/overlay/rockchip-i2c1.dtbo boot/dtb-6.9.3-edge-rockchip/overlay/rockchip-i2c4.dtbo ...cut... boot/dtb-6.9.3-edge-rockchip/rk3188-radxarock.dtb boot/dtb-6.9.3-edge-rockchip/rk3228-evb.dtb boot/dtb-6.9.3-edge-rockchip/rk3229-evb.dtb boot/dtb-6.9.3-edge-rockchip/rk3229-xms6.dtb boot/dtb-6.9.3-edge-rockchip/rk322x-box.dtb boot/dtb-6.9.3-edge-rockchip/rk3288-evb-act8846.dtb ...cut.. boot/dtb-6.9.3-edge-rockchip/rk3288-rock-pi-n8.dtb boot/dtb-6.9.3-edge-rockchip/rk3288-rock2-square.dtb boot/dtb-6.9.3-edge-rockchip/rk3288-tinker-s.dtb boot/dtb-6.9.3-edge-rockchip/rk3288-tinker.dtb boot/dtb-6.9.3-edge-rockchip/rk3288-veyron-brain.dtb boot/dtb-6.9.3-edge-rockchip/rk3288-veyron-fievel.dtb ...cut... which seems quite ok (.dtbo, .src and readme files are all in overlay directory, .dtb files are outside) compared to a live installation I have around. Jira reference number AR-2347 How Has This Been Tested? [x] Compilation works without errors [x] Manually checked dtb file [ ] Upgrade of a living system - this is crucial, since the previous overlay compilation involved other steps that have been removed and I don't know if they are still necessary (perhaps they aren't, since dtc matured in the years). 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 View the full article
-
Adds the needed files support the spidev on the NanoPi Neo3 with a different address. Tested on my own NanoPi Neo3 with a LoRaWAN concentrator connected via SPI. I am unsure about the changes in rockchip-fixup.scr-cmd. It needs a user to use a not very convenient device "number" specific to the NanoPi Neo3. But I did not know how to do this differently without possibly breaking other boards. Any suggestions on how this is usually done are welcome. Still it seems I am the only person on this planet to use SPI on the NanoPi Neo3 as no one else seems to have reported anything... Any constructive feedback is very welcome. View the full article
-
Description Currently, dtbo path in boot.ini is wrong. So we cannot load device tree blob overlays for cloudshell2. This commit fix this path in boot.ini How Has This Been Tested? Path was tested and dtbo's are succesfully loaded. Checklist: Please delete options that are not relevant. [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 [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
-
Description ssh.service activation fails on first boot due to a race condition with armbian-firstrun (missing host keys at ssh.service startup) By changing armbian-firstrun.service to run After=ssh.service SBC is always reachable realibaly via ssh, even on first run, so that it can be configured headlessly by remote login IT also reverts commit IDs: #911c756083164c32051d533ca3f2de488f202130 and #30c47f6f6cebd75f5c28866918fea093b8c82b44 disabling ssh.socket - this fixes SSH Deamon behavious to honour ListenAddress directive when set via sshd_config Jira reference number [AR-2356] How Has This Been Tested? [x] Compiled and first-run vanilla armbian Bookworm-Edge [x] Compiled and first-run vanilla Armbian Trixie-Edge [x] Simulated additional first-run(s) via systemd enable armbian-firstrun.service and touch /root/.not_logged_in_yet(Bookworm-Edge && Trixie-Edge) Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings 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. Adding support for the fine3399 board. Documentation summary for feature / change Please delete this section if entry to main documentation is not needed. If documentation entry is predicted, please provide key elements for further implementation into main documentation and set label to "Needs Documentation". You are welcome to open a PR to documentation or you can leave following information for technical writer: Adding support for the fine3399 board 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. The system can boot normally and all other functions work fine, including PCIe support, but the WiFi and Bluetooth functionalities are not available due to the lack of corresponding drivers for AP6236 in the Armbian/firmware.I have submitted the corresponding driver for AP6236 to Armbian/firmware. Please kindly review and accept it. Checklist: Please delete options that are not relevant. [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 [x] 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 Check for errors: https://github.com/armbian/scripts/actions/workflows/pull-maintainers-from-database-and-make-a-pr.yml 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 Add dummy regulators to pinctr dts for orangepione SBC. This will prevent the kernel driver from issuing warnings "supply vcc-xx not found, using dummy regulator" for the dummy regulators added. Documentation summary for feature / change How Has This Been Tested? Initially the dts entries were manually added to a running system using the dts editor in armbian-config to verify that the changes produced the desired result. Then a kernel patch was created, put into a git repository and an image generated from that repository. After installing the image on an orangepione the dtb was examined via the dts editor of armbian-config to confirm the presence of the required entries and the relevant output of dmesg was compared to a dmesg prior to the changed image. Patched pinctr: pinctrl@1c20800 { reg = <0x1c20800 0x400>; interrupt-parent = <0x1c>; interrupts = <0x00 0x0b 0x04 0x00 0x11 0x04>; clocks = <0x03 0x36 0x1a 0x1b 0x00>; clock-names = "apb\0hosc\0losc"; gpio-controller; #gpio-cells = <0x03>; interrupt-controller; #interrupt-cells = <0x03>; compatible = "allwinner,sun8i-h3-pinctrl"; vcc-pa-supply = <0x15>; vcc-pc-supply = <0x15>; vcc-pd-supply = <0x15>; vcc-pg-supply = <0x15>; phandle = <0x16>; Before dmesg: [ 1.624523] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 1.627934] sun8i-h3-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver [ 1.628539] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 1.630347] sun8i-h3-r-pinctrl 1f02c00.pinctrl: initialized sunXi PIO driver [ 1.630717] sun8i-h3-pinctrl 1c20800.pinctrl: supply vcc-pa not found, using dummy regulator [ 1.631449] printk: console [ttyS0] disabled [ 1.631881] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 138, base_baud = 1500000) is a 16550A [ 1.631943] printk: console [ttyS0] enabled [ 1.662003] sun4i-drm display-engine: bound 1100000.mixer (ops 0xc0bb3530) [ 1.664046] sun4i-drm display-engine: bound 1200000.mixer (ops 0xc0bb3530) [ 1.664515] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xc0baed88) [ 1.664916] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops 0xc0baed88) [ 1.665001] sun8i-dw-hdmi 1ee0000.hdmi: supply hvcc not found, using dummy regulator [ 1.665983] sun8i-dw-hdmi 1ee0000.hdmi: Detected HDMI TX controller v1.32a with HDCP (sun8i_dw_hdmi_phy) [ 1.666767] sun8i-dw-hdmi 1ee0000.hdmi: registered DesignWare HDMI I2C bus driver [ 1.667325] sun4i-drm display-engine: bound 1ee0000.hdmi (ops 0xc0bb28fc) [ 1.668197] [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 0 [ 1.668296] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 1.672029] sun8i-h3-r-pinctrl 1f02c00.pinctrl: supply vcc-pl not found, using dummy regulator [ 1.672085] sun8i-h3-pinctrl 1c20800.pinctrl: supply vcc-pf not found, using dummy regulator [ 1.672396] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 1.676045] sun8i-h3-pinctrl 1c20800.pinctrl: supply vcc-pg not found, using dummy regulator After dmesg (note that supply vcc-pa and pg warnings are not present): [ 1.993966] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 1.997326] sun8i-h3-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver [ 1.997891] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 1.999757] sun8i-h3-r-pinctrl 1f02c00.pinctrl: initialized sunXi PIO driver [ 2.000715] printk: console [ttyS0] disabled [ 2.001152] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 138, base_baud = 1500000) is a 16550A [ 2.001213] printk: console [ttyS0] enabled [ 2.031315] sun4i-drm display-engine: bound 1100000.mixer (ops 0xc0bb3530) [ 2.033318] sun4i-drm display-engine: bound 1200000.mixer (ops 0xc0bb3530) [ 2.033766] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xc0baed88) [ 2.034153] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops 0xc0baed88) [ 2.034238] sun8i-dw-hdmi 1ee0000.hdmi: supply hvcc not found, using dummy regulator [ 2.035482] sun8i-dw-hdmi 1ee0000.hdmi: Detected HDMI TX controller v1.32a with HDCP (sun8i_dw_hdmi_phy) [ 2.036244] sun8i-dw-hdmi 1ee0000.hdmi: registered DesignWare HDMI I2C bus driver [ 2.036617] sun4i-drm display-engine: bound 1ee0000.hdmi (ops 0xc0bb28fc) [ 2.037494] [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 0 [ 2.037592] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 2.041301] sun8i-h3-r-pinctrl 1f02c00.pinctrl: supply vcc-pl not found, using dummy regulator [ 2.041356] sun8i-h3-pinctrl 1c20800.pinctrl: supply vcc-pf not found, using dummy regulator Checklist: [ x ] My code follows the style guidelines of this project [ x ] I have performed a self-review of my own code [ x ] My changes generate no new warnings View the full article
-
Description Uboot v2024.01 leaves HDMI/VOP and USB ports in a state that is not liked by vendor kernel tools (eg. the Multitool), thus making their usage difficult or impossible. These patches will assert the resets for HDMI, VOP and USB ports and deassert them on uboot exit, so the kernel (any kernel) will find them in active and "clean" state. Nerd note: the USB nodes in uboot device tree do not have the reset properties. Adding the reset properties makes the USB ports undetectable to the kernel because uboot - on purpose - leaves the devices with the reset asserted. To let the kernel detect the ports, you have to add the reset properties in the kernel device tree too, so the kernel is able to deassert them. A more complete device tree is not always to be a good thing, for uboot at least. Jira reference number AR-2349 How Has This Been Tested? [x] Compiled uboot via armbian tools [x] Tested produced uboot on various live systems [x] Tested uboot in conjuction with tools using vendor kernel (multitool) 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 View the full article
-
Description Radxa Rock 3C has a variant with aic8800 wifi 6 module using sdio, marked as board rev 1.4. The dkms driver is added to the image by reusing the extension recently added in #6670. 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.sh build BOARD=rock-3c BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=yes DEB_COMPRESS=xz KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=trixie Build log: https://paste.armbian.com/epehanekey [x] Wifi is detected on image first boot on my Rock 3C rev 1.4. Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article
-
Join us at Augmented World Expo for a first-hand look at our recent XR work including ElectricMaple remote rendering, and xrdesktop showcasing a fully open-source 3-window desktop configuration with gaze-driven window selection. View the full article
-
The world of AI has made leaps and bounds from what it once was, but there are still some adjustments required for the optimal outcome. With the help of WhisperLive, VoxAI was able to improve its response time and oratory abilities. View the full article
-
Description Rock 5c has an on board aic8800 usb wifi module, which need dkms packages from https://github.com/radxa-pkg/aic8800. Add an extension to preinstall these packages to image. 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.sh build BOARD=rock-5c BRANCH=vendor BUILD_DESKTOP=no BUILD_MINIMAL=yes DEB_COMPRESS=xz KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm. Build log: https://paste.armbian.com/jabulawezu [ ] I don't have rock 5c at my hand to test, I will share my built images to my friends to test. Checklist: Please delete options that are not relevant. [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 [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
-
Description Maint. How Has This Been Tested? [ ] CI Checklist: [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
-
Description Maint How Has This Been Tested? [x] CI Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
-
Description Maint task. How Has This Been Tested? [ ] CI Checklist: [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
-
Description Main. Kernel config rewrite applied. How Has This Been Tested? [ ] CI Checklist: Please delete options that are not relevant. [ ] 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
-
Description station-m3: use radxa's new u-boot. Fix station-m3 audio issue. 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] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
-
Description Add support for a rk3568 based SBC Lubancat2 in my hand. The u-boot and linux kernel support is landing mainline for a few months. How Has This Been Tested? Test: ./compile.sh build BOARD=lubancat2 BRANCH=edge BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers chat desktop_tools editors email internet multimedia office programming remote_desktop' DESKTOP_ENVIRONMENT=xfce DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base DOWNLOAD_MIRROR=bfsu ENABLE_EXTENSIONS=mesa-vpu EXPERT=yes EXTRAWIFI=no KERNEL_CONFIGURE=no PREFER_DOCKER=no RELEASE=noble VENDOR=Armbian Write the image to tf card, insert the card to the board, the board can boot into desktop. Checklist: Please delete options that are not relevant. [ ✓] 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 [ ✓] My changes generate no new warnings [ ✓] Any dependent changes have been merged and published in downstream modules View the full article
-
"重命名add-new-borad-tinker-edge-r.patch -> patch/u-boot/u-boot-rockchip64/add-new-board-tinker-edge-r.patch;添加了对xiaobao-nas的支持" Description add-new-borad-tinker-edge-r.patch -> patch/u-boot/u-boot-rockchip64/add-new-board-tinker-edge-r.patch;Adding support for xiaobao NAS. add config/boards/xiaobao-nas.csc,add atch/kernel/archive/rockchip64-6.1/add-board-xiaobao-nas-dts.patch,add patch/kernel/archive/rockchip64-6.6/add-board-xiaobao-nas-dts.patch,add patch/kernel/archive/rockchip64-6.8/add-board-xiaobao-nas-dts.patch,add patch/u-boot/u-boot-rockchip64/add-new-board-xiaobao-nas-dts.patch. 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. There were no errors during compilation in the local environment, which was Ubuntu 22.04. Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article
