Jump to content

RSS Bot

Bot
  • Posts

    4244
  • Joined

  • Last visited

    Never

Everything posted by RSS Bot

  1. Description update overlay prefix due to SoC family change remove rkbin repo override now that armbian rkbin repo has blobs install headers by default on both boards View the full article
  2. Description The raspberry pi images were broken since #6087 as armbian.list was no longer available to install the required packages. As the description for #6087 mentioned that the change was just to remove the dormant armbian.list.disabled file, this PR does the same simply by removing the file if its present after image-late. 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 Raspberry pi images and also verifying that there is no leftover armbian.list.disabled file. 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
  3. Description We already set to Armbian, but we didn't set default link. This fixes it for both, Debian and Ubuntu. 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-2012 Close https://github.com/armbian/build/issues/6118 How Has This Been Tested? [ ] Make an upgrade and see if it get fixed. 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
  4. mangopi-m28k is rk3528 new mini sbc box. The following hardware features are supported: 1.Two Gb ethernet(one gmac another is pcie) 2.Two usb 2.0 type A connecter 3.wifi6 aic8800 4.lpddr4(1-4GB)emmc(8-32)TF 5.micro hdmi connecter 6.IR Receiver 7.user uart/spi/iic extended interfaces 8.pd power View the full article
  5. Description The schedutil cpu frequency governor is more tightly coupled to userspace activity and performs more granular cpu frequency changes. I've personally be using it for years. I think it's prudent to change to this default.. especially given cpu-frequency utils is deprecated and no-longer enabled by default on armbian builds. I think if this is merged it's an opportunity to also remove some of the unmaintained on-demand governor tweaks in armbian-hardware-optimize as well. Quoting the kernel docs: This governor generally is regarded as a replacement for the older ondemand and conservative governors (described below), as it is simpler and more tightly integrated with the CPU scheduler, its overhead in terms of CPU context switches and similar is less significant, and it uses the scheduler's own CPU utilization metric, so in principle its decisions should not contradict the decisions made by the other parts of the scheduler. View the full article
  6. Description Expose rk322x-dmc driver load, upthreshold and downthreshold attributes via sysfs objects to monitor and manipulate dmc behaviour via userspace. Implemented only on edge 6.6 kernel, which will become current very soon. Tunables will be available in /sys/class/devfreq/11200000.dmc/device directory How Has This Been Tested? [x] Compiled kernel and tested on live system 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
  7. …et/browse/AR-1904 Description Using the Rock Pi S with 10mbps Ethernet connection is not possible. A connection is shown but data transmission is not possible. Note that this patch is only for the "current" kernel. The "edge" kernel no longer boots RockPI-S. Jira reference number AR-1904 How Has This Been Tested? Built 23.05 Minimal image for RockPI-S Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. Verified Ethernet transfer @100Mbit/s initially ethtool -s end0 advertise 3 Verified Ethernet transfer rate now only 10Mbit/s ethtool -s end0 advertise f Verified Ethernet transfer rate restored to 100Mbit/s Bug was a regression first seen in the 5.15 Armbian kernel caused by a rewrite of speed setting for rk3308 in dwmc-rk.c that for some bizarre reason completely omitted the code needed to reprogram the MAC clock as appropriate for the selected Ethernet speed. 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
  8. Description We certainly don't need dual mode compilation while armbian_repo variant is anyway broken due to other changes. How Has This Been Tested? [x] Build Debian [x] Build Ubuntu and boot 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
  9. hi, I recently bought an Orange Pi 5 Plus and the RTL8852BE wireless module (http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-R6.html). can I add a kernel module to run the RTL8852BE on the Orange Pi 5 Plus? Description Adding CONFIG_RTW89_8852BE to linux-rockchip-rk3588-edge.config How Has This Been Tested? built the img and booted it. checked that RTL8852BE is working (need firmware-realtek). 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
  10. Description Some users reported bluetooth not working sometimes after reboot. Turns out that sometimes hciattach binary that we use segfaults during reboot. Replacing the binary with the one present in orangepi_build repository as it seems it solves the issue. 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 by the user by rebooting their device 5 times. Bluetooth worked fine consistently after every reboot. 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
  11. Description Fixed the compilation issue with new khadas u-boot. The fix is actually quite ugly. We are now compiling u-boot twice, once with gcc 11.4 and then with linaro toolchain v7.3.1. Also as Linaro's compiler is only available for x86 platform, uboot for these boards will not build on arm platforms. But I guess we have to live with it for now. 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 building uboot for khadas vim1s 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
  12. Description Cosmetic / syntax. Jira reference number AR-2010 Checklist: [x] My code follows the style guidelines of this project [x] My changes generate no new warnings View the full article
  13. Description Userpatches folder is hard-coded in extensions loading. Jira reference number AR-2009 How Has This Been Tested? [x] Enable extension located in USERPATCHES_PATH (with PREFER_DOCKER="no") 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
  14. Description Bumped Allwinner edge kernel to 6.7-rc7 Added HDMI support for H616/H618 boards. The hdmi driver patch is based on changes from Orange Pi's 6.1 repo but is heavily modified to get applied on top of drm patches of megous tree. Removed 4.9 Orange Pi Zero 2 vendor kernel and legacy u-boot utilities Added WIP Orange Pi Zero3 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. [ ] Testing current and edge kernel on Orange Pi Zero3 using XFCE desktop image [ ] Need someone to test on Orange Pi Zero2 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
  15. Description This will be our base for official build tool. Current variant has only enabled basic features which should be enough to push it to GitHub marketplace. Requirements. Jira reference number AR-1459 How Has This Been Tested? [ ] SDK image building 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
  16. Description I'm rewriting patches with command PREFER_DOCKER=no ./compile.sh rewrite-kernel-patches BOARD=rock-5b BRANCH=edge on armbian jammy, but I get all commit index length changed from 12 to 13. Maybe that's because envirmonts are different between docker and bare metal. So add --abbrev=12 to always get commit index length 12. 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] PREFER_DOCKER=no ./compile.sh rewrite-kernel-patches BOARD=rock-5b BRANCH=edge 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 [ ] 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
  17. odroidm1: set OVERLAY_PREFIX; rockchip64: default, but don't override, OVERLAY_PREFIX odroidm1: set OVERLAY_PREFIX; rockchip64: default, but don't override, OVERLAY_PREFIX View the full article
  18. cleanup a few lost/old/forgotten/replaced code/patches [cleanup] extensions: flash-kernel: removed (and a few references to it) thanks to Gunjan for replacing it [cleanup] rk3399: remove defunct patches & dangling symlinks for rk3399-legacy and rk35xx-legacy [cleanup] rockchip64 legacy: remove long dead 4.4 patches (family/common didn't define legacy branch for a while) [cleanup] remove old rk35xx-4.19 archive patch folder that is unused View the full article
  19. use hooks for main kernel/u-boot version defaulting/overriding; remove symlink usage from many families [cleanup] extensions: flash-kernel: removed (and a few references to it) thanks to Gunjan for replacing it [cleanup] rk3399: remove defunct patches & dangling symlinks for rk3399-legacy and rk35xx-legacy [cleanup] rockchip64 legacy: remove long dead 4.4 patches (family/common didn't define legacy branch for a while) core: semantic change, KERNELSOURCE must be explicitly 'none' to avoid kernel compilation (not unset) main-config: mark mirror variables readonly; add todo's lib/family config: remove resquices of KERNELDIR which is completely unused for a long time also MAINLINE_KERNEL_DIR not needed then main-config: arches: don't default KERNELSOURCE to mainline (already done in common), cleanup comments main-config: arch common: kernel/u-boot config defaulting+overriding via hook instead of pre-setting common.conf delegating to new mainline_kernel_decide_version hooks special case handling for v6.7-rc7 some examples late-stage "use rolling branch version" uefi: don't spell out KERNELBRANCH anymore, KERNEL_MAJOR_MINOR is sufficient now meson64: family common: drop KERNELBRANCH, rely on KERNEL_MAJOR_MINOR only, no more symlinks rockchip64: family common: drop KERNELBRANCH, rely on KERNEL_MAJOR_MINOR only, no more symlinks rockchip64_common is used by BOARDFAMILY's with their own LINUXFAMILY, so we can't be very generic here meson (32-bit): family common: drop KERNELBRANCH, rely on KERNEL_MAJOR_MINOR only, no more symlinks [move] rockchip-rk3588 edge 6.7: move patches to archive, do not add symlinks sunxi/sunxi64: move version locking to shared hook in mainline-kernel.conf.sh rockchip (32-bit): move version locking to shared hook in mainline-kernel.conf.sh main-config: arch common: review logging levels, squash some todo, add some todo lib: implement and sprikle some very basic config var change-tracking across board/family sourcing and several hook calls View the full article
  20. 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
  21. uefi: rollover current to legacy, edge to current, bump edge to 6.7, fix drivers, remove symlinks uefi: common: stop using symlinks, instead point directly to KERNEL_MAJOR_MINOR uefi: common: drop kernel symlinks remove duplicate decls simplify some comments thinkpad-x13s: set explicit LINUXCONFIG to compensate for changes in uefi-common uefi: all: update all .config's, no changes; edge: 6.6.y; current 6.1.y; legacy 5.15.y uefi: all: rollover current 6.1.y to legacy, taking over 5.15.y uefi: all: rollover edge 6.6.y to current, taking over 6.1.y uefi-arm64 6.7: copy patches from 6.6 uefi: all: edge: bump to 6.7-rc7; arm64: fix Phytium stmmac patch (by Igor) Co-authored-by: Igor Pecovnik igor.pecovnik@gmail.com uefi: arm64: drop obsolete patch archives for 6.2, 6.3, 6.4, 6.5 drivers_network: bumps to drivers from upstream repos (by Igor, from AR-2005) Co-authored-by: Igor Pecovnik igor.pecovnik@gmail.com uefi: all: update edge 6.7.y .config's, no changes uefi: arm64: edge: 6.7: rebase patches onto 6.7-rc7 uefi: arm64: current: 6.6: rebase patches onto 6.6.8 View the full article
  22. RFC: mixtile-blade3 / rockchip-rk3588 edge 6.7: add DT from Joshua Riek + some fixes mixtile-blade3 / rockchip-rk3588 edge 6.7: add DT (original from Joshua Riek) base for https://github.com/Joshua-Riek/linux/pull/1 mixtile-blade3 / rockchip-rk3588 edge 6.7: cleanups for Mixtile Blade3 arm64: dts: rockchip: cleanups for Mixtile Blade3 drop hym8563 pinctrl (don't think the blade3 has an RTC) i2c5 is exposed on the 30-pin, add comment fix tab in pcie30phy mixtile-blade3 / rockchip-rk3588 edge 6.7: pci3x4 for Mixtile Blade3 (rpardini's bad take) arm64: dts: rockchip: pci3x4 for Mixtile Blade3 pinctrl for 1 RK_PB2 pull_up regulator vcc3v3_pcie30 always-on and boot-on there is probably a much better fix than this, but I couldn't find it mixtile-blade3 / rockchip-rk3588 edge 6.7: slow down eMMC from hs400 to hs200 mixtile-blade3 / rockchip-rk3588-edge 6.7: enable tsadc for thermal sensors thanks AmazingFate mixtile-blade3: enable edge branch with new dt; all branches use vendor u-boot here's some work I've been sitting on for a while for the Mixtile Blade3 - schematics - vendor kernel DT I took @Joshua-Riek 's DT and worked it a bit. All credit to him. Most stuff works, but it's not really stable, and pcie3x4 works "sometimes". Similar stuff works for (vendor) u-boot, where it always works. I'm using their u.2 to m.2 breakout board. Any ideas? View the full article
  23. rockchip-rk3588 edge: bump to 6.7-rc7; add overlays rockchip-rk3588 edge 6.7-rc4: rewrite/rebase patches in the process, MAINTAINERS file patches are dropped rockchip-rk3588 edge 6.7: bump to 6.4-rc7; rebase patches rockchip-rk3588 edge 6.7: add overlay support; add rockchip-rk3588-sata2 overlay rockchip-rk3588 edge 6.7-rc7: update .config, no changes View the full article
  24. Description Current kernel deb package script ignores localversion of linux-next like -next-20231222, which will not pass deb building. This commit will add this localversion when grabbing kernel version. 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 kernel BOARD=rock-5b BRANCH=edge DEB_COMPRESS=xz KERNEL_GIT=shallow, tested with KERNELSOURCE changed to https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git. [x] Built kernel runs normally. [x] Normal non-next kernel source 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 [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
  25. Description Big pull request that consolidates rockchip 32bit and rk322x families together, for less painful kernel patch adaption during maintance cycles. Jira reference number AR-1988 Despite this is the minor nightmarish part of the rockchip patches archive, consolidation could and has been done. In particular, this PR do: merge patches from rockchip and rk322x families for current and edge kernels, moving everything into rockchipfamily migrate edge kernel rockchip-6.6 into patch series, rename all patches with more understandable names with alphabetical prefixes in place of numeric ones (sunxi inspired) implement new style dt and overlay directories for edge and current kernels to leverage the build system automatic makefile handling rework kernel configs for both edge and current: some things have been added, some removed, but will require some fine tuning that will be subject of another PR probably adjust patches for tinkerboard to remove some cruft and overclocking, cleaning up dmesg also fix rk322x dmc to avoid lockup on rk3288 remove non-LTS rk322x archives from patch directory; remaining rk322x kernel archives can be removed in the future as well, since they are kept only for historical purposes and not in use anymore; also removes rk322x legacy, current and edge symlinks remove non-LTS rockchip archives from patch directory (acutally the only removed leftover was rockchip-6.5) remove legacy kernel target for rk322x-box add gen-series.sh script in tools directory (it is a naive tool to create patch series from scratch when you don't want to rebase everything, script is fully commented and usage help provided also) How Has This Been Tested? [x] Debian Bookworm image built and tested for rk322x-box [x] Debian Bookworm image built and tested for tinkerboard [x] Ubuntu Jammy image built and tested for rk322x-box [x] Ubuntu Jammy image built and tested for tinkerboard [x] Several edge 6.6 and current 6.1 kernel compilations [x] Cores, gpu, hdmi, hdmi audio, ethernet, wifi, hardware decoding, usb tested on tinkerboard current 6.1 [x] Cores, gpu, hdmi, hdmi audio, ethernet, wifi, hardware decoding, usb tested on tinkerboard edge 6.6 [x] Cores, gpu, hdmi, hdmi audio, ethernet, wifi, hardware decoding, usb tested on rk322x-box current 6.1 [x] Cores, gpu, hdmi, hdmi audio, ethernet, wifi, hardware decoding, usb tested on rk322x-box edge 6.6 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 [ ] 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
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines