

RSS Bot
Bot-
Posts
4235 -
Joined
-
Last visited
Never
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by RSS Bot
-
Description Adding a command that can be used to refresh kernel configs without launching menuconfig interface. This can be helpful to refresh kernel configs when doing kernel upgrades for all kernels being bumped by running in a for loop and can be also be used in some automation to periodically refresh kernel configs 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 running ./compile.sh BOARD=khadas-vim4 BRANCH=legacy rewrite-kernel-config. It refreshed and updated config/kernel/linux-meson-s4t7-legacy.config file based on the needed updates which in this case was mostly compiler and toolchain versions as this file has not been refreshed for sometime now. 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 meson: fix: Fail to register VCC_CORE regulator How Has This Been Tested? [X] Build [X] Burn and run Checklist: [ ] 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
-
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 Fixes compilation issue introduced by u-boot bump. Not sure why this was not caught in the test as I ran building of all allwinner u-boots in a loop. Anyways, now these are getting built correctly 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 u-boot builds for orangepizero2 [X] Tested u-boot builds 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
-
Description thead: fix LicheePi 4A audio problem. https://github.com/armbian/build/pull/5712#issuecomment-1741680089 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] Successfully built. [x] System startup (EMMC). 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 [x] Any dependent changes have been merged and published in downstream modules View the full article
-
Description Bumped u-boot for allwinner to 2023.10 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] All patches gets applied [X] U-boot build for all of the allwinner boards 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
-
Not sure why this hasn't been adjusted yet... View the full article
-
uefi-arm64/edge: bump to 6.6-rc4 uefi-arm64/edge: bump to 6.6-rc4 - initial copy from 6.5 uefi-arm64/edge 6.6.y: bump to 6.6-rc4 - fix phytium stmmac acpi patch for 6.6 uefi-arm64/edge 6.6.y: futher fix for phytium stmmac acpi glue View the full article
-
meson64/edge: bump to 6.6-rc4 meson64/edge: bump to 6.6-rc4; initial copy from 6.5 meson64/edge 6.6.y: bump to 6.6-rc4 - rebase patches meson64/edge 6.6.y: bump to 6.6-rc4 - fix patches board-bananapi-cm4-switch-to-enable-gpios.patch: landed upstream driver-power-meson64-reset.patch: fix manually, nearby driver POWER_RESET_OXNAS was dropped from upstream let's light a candle for OXNAS View the full article
-
rockchip64/edge: bump to 6.6-rc4 rockchip64/edge: bump to 6.6-rc4; initial copy patches from 6.5 rockchip64/edge: bump to 6.6-rc4; rebase patches rockchip64/edge 6.6.y: manually fix 2 patches rockchip64/edge 6.6.y: fix TB2's regulator patch after probe/probe_new dance rpardini: hammered .probe and probe_type = PROBE_PREFER_ASYNCHRONOUS to work on 6.6.y, after https://lore.kernel.org/all/20230505220218.1239542-1-u.kleine-koenig@pengutronix.de/ rockchip64/edge 6.6.y: update overlay configfs patch from rpi from https://github.com/raspberrypi/linux/commit/b128f09592f14596f9cf79d2c8fd7355bb0e9b5c.patch found via https://github.com/raspberrypi/linux/commits/rpi-6.6.y/drivers/of/configfs.c rockchip64 + sunxi*: drivers_network: enable uwe5622 driver also for 6.6 rockchip64 + sunxi*: drivers_network: add patch for uwe5622, fixing build on 6.6.y rockchip64/edge 6.6.y: update .config to v6.6-rc4, no changes rockchip64/edge 6.6.y: add montjoie's rk3588/68/66 rk2 crypto patches (v1) rockchip64/edge 6.6.y: enable CONFIG_CRYPTO_DEV_ROCKCHIP2 and the rk crypto debugs View the full article
-
rk3568-odroid/edge: bump to 6.6-rc4 rk3568-odroid/edge: bump to 6.6-rc4; initial copy from 6.5 this is getting long in tooth, should merge with rockchip64 "soon" rk3568-odroid/edge 6.6.y: update .config for v6.6-rc4, no changes rk3568-odroid/edge 6.6.y: add montjoie's rk3588/68/66 rk2 crypto patches (v1) rk3568-odroid/edge 6.6.y: enable CONFIG_CRYPTO_DEV_ROCKCHIP2 and the rk crypto debugs View the full article
-
patching: 6.5+ armhf Makefile autopatcher; better summary patching: enhance the DT Makefile Autopatcher to work with armhf's new 6.5 subdir Makefiles as well as arm64 arm64: one-rule-per-dtb arm32: single-rule, multi-dtb patching: show the patch number for multi-patch mbox files in summary table patching: show auto-patch'ed in summary table (in blue); remove spurious warnings View the full article
-
docker (launcher): small fixes docker (launcher): fix un-needed grep escape \: (fixes "grep: warning: stray \ before :" on recent coreutils) docker (launcher): fix DOCKER_PASS_GIT=yes to actually work it still sucks (very slow) but is a way to get ${SRC}/.git in Docker if needed eg for patching archeology View the full article
-
rk322x/edge 6.5: enable Makefile Autopatcher, remove Makefile patches rk322x-config: shformat + fix 2 shellcheck errors rk322x/edge 6.5: update .config, no changes rk322x/edge 6.5: enable Makefile Autopatcher, remove Makefile patches remove add-board-makefile Patch remove overlay-y Makefile patch add note to the 6.1 version: Makefile autopatcher can't be enabled for 6.1, since the armhf move to subdirs only landed in 6.5-rc1 View the full article
-
base-files: add the upstream version both to the artifact_version and the reversioned; possibly fixes #5702 base-files: add the upstream version both to the artifact_version and the reversioned; possibly fixes #5702 OCI tags can't have "+" or "~" so replace those with "--" before using in OCI tag apt (repo) version will have whatever upstream has, including "+" and/or "~" View the full article
-
Description thead: add edge kernel support How Has This Been Tested? [x] Successfully built. [x] System startup (EMMC). 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 [x] Any dependent changes have been merged and published in downstream modules View the full article
-
This second installment explores the Rust libraries Collabora developed to decode video and how these libraries are used within the ARCVM codec stack to eventually replace CrosVM's dependency on the Chrome codec stack through libvda. 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 This PR will convert the existing dtb and dtbo patches into dt/overlay directories as in rockchip64 and other families for easier future handling of device trees. Also fixes a weird u-boot bug for device tree overlays and bring full support for R29_MXQ, R2B_MXQ and H20 boards. No other families other than rk322x have been touch by this PR. How Has This Been Tested? [x] Debian Bookworm images built and tested on live machine [x] Compiled current kernel 6.1 and tested on live installation 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 Maint. How Has This Been Tested? [x] Patch 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article