Jump to content

RSS Bot

Bot
  • Posts

    4244
  • Joined

  • Last visited

    Never

Everything posted by RSS Bot

  1. simply because we can View the full article
  2. Description This adds mainline support for the Radxa Zero 3 (E variant at least) SBC by utilizing kwiboo's patch series for both Linux and U-Boot. How Has This Been Tested? Test device: Zero 3E 2GB [x] build edge [x] boot edge http://paste.armbian.com/osofoyuqun.yaml [x] build vendor [x] boot vendor https://paste.armbian.com/lejunireni.yaml Issues: This PR cannot be merged as it is since I have no idea what I am doing so the kernel patchset lacks proper headers. I had to strip those since the framework did not accept the patch series as they were. I don't know how to fix. Those need to be restored to give proper credit. Source: https://patchwork.kernel.org/project/linux-arm-kernel/cover/20240521202810.1225636-1-jonas@kwiboo.se/ this only works for the 3E variant but not for 3W since the vendor variant is a combination of both but mainline provides separate dtbs. This needs attention/workaround as well. BOOTPATCHDIR is just fake so no patches are applied on top of upstream sources. I assume there is a more pretty way to solve this. Raising anyways to create awareness and maybe anyone wants to pick it up and fix things. Feel free to commit adjustments here and bring it in good shape. View the full article
  3. Description removing network manager dependency. Left over from moving networking into extensions. address errors when wireless networking is still not detected Jira reference number AR-2390 Documentation summary for feature / change How Has This Been Tested? [x] Several images on board without wifi only [x] Tested making wrong wifi password 3x, exits with "Unable to connect to AP" [x] Connecting with correct credentials [x] Choosing to not connect to wireless [x] Tested on NM and systemd networkd Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
  4. Description As mentioned here: https://github.com/armbian/build/pull/6810#issuecomment-2194178735 Out of date blobs can be an issue if the vendor ships boards with new blobs, as recently seen for FriendlyElec with the NanoPC T6 for example. The release docs do not mention any incompatibilities between versions for rk3528 and rk3568: https://github.com/armbian/rkbin/blob/master/patch-notes/RK3528_EN.md https://github.com/armbian/rkbin/blob/master/patch-notes/RK3568_EN.md For rk3566, only one warning is listed for rk3566_ddr_1056MHz_ultra_v1.19.bin but we're not using the ultra blob (what's the difference?): https://github.com/armbian/rkbin/blob/master/patch-notes/RK3566_EN.md#rk3566_ddr_1056mhz_ultra_v119bin ROCK_USB_BLOB bump depends on https://github.com/armbian/rkbin/pull/29 being merged. Other blobs have already been merged to armbian/rkbin in the past. How Has This Been Tested? [x] RK3568: ./compile.sh uboot ARTIFACT_IGNORE_CACHE=yes BOARD=nanopi-r5c BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [ ] RK3566: Not tested - @RadxaNaoki would be great if you could test on Raxda Zero 3 or similar board 😊 [ ] RK3528: Not tested - @amazingfate @sputnik2019 would be great if you could test on a RK3528 board 😊 (although the doc does not list any incompatibilities) Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
  5. Description Also group all u-boot make environment variables together for easier maintainability Fixes u-boot requiring pyelftools Fixes commit https://github.com/armbian/build/commit/04f619dc06d12449b1315f01bb8fe70003316761 GitHub issue reference: https://github.com/armbian/build/pull/6799#issuecomment-2196438786 How Has This Been Tested? [x] sudo apt remove python3-pyelftools and then ./compile.sh uboot ARTIFACT_IGNORE_CACHE=yes BOARD=nanopi-r6c BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie [x] ./compile.sh uboot ARTIFACT_IGNORE_CACHE=yes BOARD=radxa-zero3 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=trixie 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
  6. (partially) Revert "python: Move python3-setuptools and python3-pyelftools to requirements.txt" (partially) Revert "python: Move python3-setuptools and python3-pyelftools to requirements.txt" "Fixes" https://github.com/armbian/build/pull/6799 This (partially) reverts commit 04f619dc View the full article
  7. rtl_bt: Update RTL8822C BT UART firmware to 0xB5D6_6DCB View the full article
  8. Description Update odroidxu4-current kernel to 6.6.36. How Has This Been Tested? [x] Reboot of my Odroid HC1 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
  9. Description A new issue template for Tasks will make project/task tracking easier on GitHub. See for example how Pi-Hole does project tracking: https://github.com/orgs/pi-hole/projects/22 The tasks will be automatically uploaded to Jira, so no changes there. How Has This Been Tested? [ ] To be tested in future issues 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 View the full article
  10. Description station-m2: update u-boot patches. Add u-boot device tree for station-m2. 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
  11. With each board running a mainline-first Linux software stack and tested in a CI loop with the LAVA test framework, the Farm showcased Collabora's recent hardware enablement and Continuous integration (CI) efforts. View the full article
  12. 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. Jira reference number [AR-9999] 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: [] short description (copy / paste of PR title) [ ] summary (description relevant for end users) [ ] example of usage (how to see this in function) 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. [ ] Test A [ ] Test B 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
  13. rk3588: bump default blobs (DDR:1.16, BL31:1.45); remove board-specific blobs from boards that used those versions rk3588: bump default blobs (DDR:1.16, BL31:1.45); remove board-specific blobs from boards that used those versions in practice: boards that didn't specify their own blobs: bump DDR 1.08->1.16 ; BL31 1.28 -> 1.45 (example: rock-5b!) boards that specified 1.16/1.45 individually now follow the defaults (no change) boards that specified a different version: no change; just a TODO suggesting review/removal/go-with-the-defaults Mekotronics boards: bump from 1.11/1.38 to defaults (1.16 / 1.45) View the full article
  14. fix: partitioning: disable orphan_file (FEATURE_C12) for ext4 filesystems on 1.47+ e2fsprogs host fix: partitioning: disable orphan_file (FEATURE_C12) for ext4 filesystems on 1.47+ e2fsprogs host otherwise:fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1 has unsupported feature(s): FEATURE_C12 e2fsck: Get a newer version of e2fsck! orphan_file can only be disabled on recent-enough e2fsprogs, thus check version and compare View the full article
  15. kde-neon: use Neon's "user" repo for Jammy & return it to csc status kde-neon: use Neon's "user" repo for Jammy & return it to csc status for noble: keep on Neon's "testing" repo which now has a "noble" dist (instead of Jammy) - but keep it eos as it really doesn't build yet. See https://blog.neon.kde.org/2024/05/09/kde-neon-rebasing-on-ubuntu-noble/ - might take a while still View the full article
  16. Description The color hex code cannot be prefixed with #. See https://github.com/armbian/build/actions/runs/9683062190/job/26717603287 How Has This Been Tested? [ ] To be tested in future PRs Checklist: [x] My code follows the style guidelines of this project View the full article
  17. WirePlumber 0.5 arrived recently with many new and essential features including the Smart Filter Policy, enabling audio filters to automatically insert themselves in between client streams and devices. View the full article
  18. Description This example PR: https://github.com/armbian/build/pull/6804 has the "Framework" label while it only changes stuff in a bsp package. To make it clearer, add a new label for the auto-labeler. How Has This Been Tested? [ ] To be tested in future PRs 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 [ ] My changes generate no new warnings View the full article
  19. Description We can also use rkvdec2 on rk356x. Remove all non-coherent-dst-bufs patches because they are suggested by a chromium developer when using libyuvimageprocessor to do NV12->AR24 convert. Now we use wayland gbm to render NV12 directly, so these patches are not necessary. Add rkvdec2 nodes to devicetree of rk356x. Enable rkvdec2 in kernel config and change CMA size from 128M to 384M for chromium's 4K h264 decoding. Change hantro g1 vpu compatible string from rockchip,rk3568-vpu to rockchip,rk3328-vpu because they have exactly the same vpu variant data. Disable h264 decoder of rk3328-vpu because there are aleady rkvdec/rkvdec2 h264 decoders on rk3328 and rk356x. Multi H264 decoders will make gstreamer and chromium confused. Add chromium v4l2 decoder udev rule for rk3328-vpu 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 on orangepi3b noble edge with chromium from my ppa: https://launchpad.net/~liujianfeng1994/+archive/ubuntu/chromium, 1080p and 2160p h264 videos and 1080p vp8 video are played with hardware decoder. 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
  20. Changes to be committed: modified: config/boards/aml-s9xx-box.tvb modified: packages/bsp/aml-s9xx-box/boot/extlinux/extlinux.conf.template The aml-s9xx-box builds use the native TV Box u-boot. I've had as a todo item to figure out how to not build and include an unused u-boot. In a recent PR for a different board the opposite was being done (adding a u-boot where a board didn't previously ship one), thus I then had the info to remove it here. This also changes the generated extlinux.conf to include a fdt line by adding the boot_fdt_file to the board config file. This reduces the effort needed to manually modify the extlinux.conf. How Has This Been Tested? [x] Build aml-s9xx-box image and debs [x] Verify built contents 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 View the full article
  21. Description This PR is a cherry-picked commit from an old PR https://github.com/armbian/build/pull/4643 Unfortunately I seem to have borked the linked PR. Using git rebase main usually works, but with a PR going this far back, something seems to not have rebased as expected. Please let me know if you know why this is 😄 The commit includes a fix from https://github.com/armbian/build/commit/7488222b2aac8bc6a395b6714dbac3f88177585e View the full article
  22. This picks up from where we left off: https://github.com/armbian/build/pull/6771 Added Linux Legacy and Current. Legacy: 6.1.15 Current: 6.1.95 Wireless has been given its own function and patch directory. Bluetooth firmware added to armbian/firmware. esos.elf moved to: packages/blobs/riscv64/spacemit/ Host machine used for builds: Ubuntu Noble (aarch64) Images tested: Ubuntu Noble Minimal and Debian Sid Information: https://docs.banana-pi.org/en/BPI-F3/BananaPi_BPI-F3 https://gitee.com/bianbu-linux Flashing u-boot to eMMC: (This is not apart of the PR and needs to be added in the future.) echo 0 > /sys/block/mmcblk2boot0/force_ro sleep .50 dd if="bootinfo_emmc.bin" of="/dev/mmcblk2boot0" bs=512 conv=notrunc dd if="FSBL.bin" of="/dev/mmcblk2boot0" bs=512 seek=1 conv=notrunc dd if="FSBL.bin" of="/dev/mmcblk2boot0" bs=512 seek=512 conv=notrunc dd if="fw_dynamic.itb" of="/dev/mmcblk2" bs=512 seek=1280 conv=notrunc dd if="u-boot.itb" of="/dev/mmcblk2" bs=512 seek=2048 conv=notrunc sync Tested: Bluetooth and Wifi (useless without an ANT) Ethernet (1 and 2) PCIe USB HDMI Debug UART NOTE: One major difference between this build and the others available else where is the use of SYSLINUX/EXTLINUX instead of the ENV file. View the full article
  23. Description disable add requirements.txt to Dockerfile generation How Has This Been Tested? [x] Manual build passes Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article
  24. Changes to be committed: modified: aml-s9xx-box.tvb PR #6659 broke upgrades for the aml-s9xx-box package. That PR introduced two new files in /boot which is a fat filesystem on this box. The standard package upgrade fails on a fat filesystem when files already exist. PR #6659 failed to add the files to the remove list. This PR does that. 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 aml-s9xx-box image and debs [x] test upgrade of the bsp-cli deb Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code View the full article
  25. Description If we want to check if a file is not from one of the listed folders, it needs to be check that "NOT x AND NOT y AND NOT z" is true, instead of "NOT x OR NOT y OR NOT z" Example: This PR should not have the "Hardware" label: https://github.com/armbian/build/pull/6781 How Has This Been Tested? [ ] To be tested in future PRs Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code View the full article
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines