RSS Bot
Bot-
Posts
4244 -
Joined
-
Last visited
Never
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by RSS Bot
-
Description Various minor fixes to rockchip rk3318/rk322x based tv boxes: usb ports gain resets in uboot and kernel, so hopefully they gains some more compatibility and/or less hangups rk3318-box now uses the ddrbin from vendor; it was accidentally switched to uboot TPL during last uboot update some patches have been removed because useless or because things could merged into board dtbs Except for a change in dwc2.c driver in rockchip 32 bit (that may have an effect on OTG port on ASUS Tinkerboard, which is usually unused due to being the power connector), no other boards are affected by these changes. It looks like that USB resets,at least on rk3318/rk3328, are good for USB gadgets and makes the audio gadget work in both UAC1 and UAC2 modes. During previous tests, without these patches, audio gadget were totally refusing to work. How Has This Been Tested? USB device have been tested on all USB OTG/EHCI or hubbed ports on these systems: [x] Tested current 6.6 kernel on rk322x live system, complied edge 6.8 kernel [x] Tested current 6.6 kernel on rk3318 live system [x] Tested current 6.6 and edge 6.8 kernels on rk3328 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] My changes generate no new warnings View the full article
-
Description Cut and sewing work around mailing list/libreelec patches to include a minimum set of patches that attempt to solve the various issues with HDMI on rockchip64 family. This affects both current kernel 6.6 and edge kernel 6.8. References on the forums: https://forum.armbian.com/topic/26818-opi-4-lts-no-hdmi-output/ https://forum.armbian.com/topic/37166-hdmi-issues-on-6x-kernel/ One kind guy tested the kernel package on rockpro64 and reported success: https://forum.armbian.com/topic/26818-opi-4-lts-no-hdmi-output/?do=findComment&comment=189646 Also remove a patch named "rk356x-vop2-support", that was not about vop2 support but rather tweaks the HDMI phy timings and code because it has been already included in this more general clock fixes. Jira reference number AR-2118 How Has This Been Tested? [x] Tested on a live Orange PI 4 LTS system [x] Tested on a rk3328 tv box [x] Tested on rockpro64 by the guy in the description 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 ArmSoM Sige1 is a rk3528 board with emmc, dual ethernet, rtl8852bs wifi/bt, HDMI, usb. https://docs.armsom.org/armsom-sige1 I just use the uboot defconfig from hinlink-h28k and it works fine. At the moment only vendor 6.1 kernel is supported. This pr depends on https://github.com/armbian/linux-rockchip/pull/178 How Has This Been Tested? [x] ./compile.sh BOARD=armsom-sige1 BRANCH=vendor BUILD_DESKTOP=no BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=bookworm KERNEL_GIT=shallow 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 Removing myself as maintainer for Raspberry Pi and Allwinner boards as I no longer have time to maintain them. As some of the boards no longer have maintainer, changed them to csc. 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
-
Description As per the title. Allows using emmc for boot partition and nvme or usb for root partition when installing via armbian-install. How Has This Been Tested? [X] Created and booted image on VIM1S with emmc+USB combo 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 [X] Any dependent changes have been merged and published in downstream modules View the full article
-
Description Use radxa's next-dev-v2024.03 branch for armsom's boards. Note that I have to remove CONFIG_OPTEE_ALWAYS_USE_SECURITY_PARTITION=y from defconfig to boot the board. So boards affected by https://github.com/armbian/build/pull/6534 like nanopi6 and nanopc-t6 should also check this. @efectn @Tonymac32 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 BOARD=armsom-sige7 BRANCH=vendor BUILD_DESKTOP=no BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=bookworm KERNEL_GIT=shallow 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 Add support to build VIM1S/VIM4 images on arm64 platform. Currently only x86_64 platform was supported as build host as the gcc-linaro-aarch64-elf compiler version 7.3.1-2018.05 was not available for aarch64 platform. I have built the compiler myself on vim4 using the commands given here How Has This Been Tested? [X] Compiled u-boot for VIM1S and VIM4 [X] Created a minimal bookworm image for VIM1S and booted on the same 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 [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article
-
Description Add huawei matebook e go support How Has This Been Tested? Tested on HUAWEI MateBook E Go installed on sd card and device is booting fine 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 Update the kernel to use the preset configurations so that you don't need an external keyboard to access the desktop Jira reference number [AR-9999] 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] Flash and directly boot to the desktop 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 [x] Any dependent changes have been merged and published in downstream modules View the full article
-
As part of our commitment to social responsibility, we've been part of the 1% for the Planet Network since 2022. The environmental partners we support help to better the planet. View the full article
-
Description Add basic support for the new Orange Pi 5 Pro. 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 U-Boot and Legacy 5.10 kernel [x] System boots as expected [ ] WiFi and Bluetooth work 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 You can get the event details directly from the github action environment and also just pass the secret directly into the step. Removed excess steps/processing to simplify the action. https://docs.github.com/en/actions/learn-github-actions/contexts#github-context How Has This Been Tested? I have tested and used this in my repo here Checklist: I can add additional comments if needed but I don't believe they are. [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 View the full article
-
Description This PR makes two changes for the bcm2711 family: Use FS UUID for mounting the root filesystem instead of the FS label, bringing this family in line with most other boards. Write config.txt and cmdline.txt earlier, allowing it to be modified from customize-image-host.sh or customize-image.sh. These two changes are conceptually independent, but touch the same area of code, so I put them in a single PR instead of splitting them. Documentation summary for feature / change No documentation needed. How Has This Been Tested? Built for rpi4b, with customizations to cmdline.txt and config.txt in customize-image-host.sh. Tested on rpi3b+ board. I do not have a rpi5 to test with, but I expect no issues there. 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 There is a 6.6 kernel available from hardkernel: https://forum.odroid.com/viewforum.php?f=226. Start migrating from 6.1to it. How Has This Been Tested? Reboot of my Odroid HC1 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
-
GStreamer 1.24 was recently released, and with it came with a new plugin to help separate pipelines into different processes. View the full article
-
Seattle is hosting this year's Embedded Open Source Summit, the umbrella conference for a collection of open source events. This is the premier space for the open source community and we'll be there with 6 talks! View the full article
-
This skips all git checkout, patching, configuring and cleaning when USE_EXISTING_KERNEL_TREE=yes is passed. This can be useful when doing kernel development by making changes directly to the kernel sourcetree in cache/sources, while still allowing to use the compile.sh to use the same compilation commands, deb package building, ccache, etc. It is also useful when bisecting a kernel issue. Can be used something like this: USE_EXISTING_KERNEL_TREE=yes ./compile.sh default kernel To produce a kernel deb in a few minutes ready to be installed on a device. This is mostly a proof of concept to explore the usecase. In particular: I am not happy with the USE_EXISTING_KERNEL_TREE name yet. I wonder if this variable should maybe be split into different ones (e.g. for skipping git checkout, patching, config, clean already has one that can be used). Or maybe it would be better to split off some code out of compile_kernel() and expose a kernel_build and/or kernel_package command from ./compile.sh instead? View the full article
-
As we reflect on the strides made in recent months, it's remarkable to see how OpenXR and Monado have evolved and are shaping the future of XR development. Let's take a closer look at the progress made and noteworthy achievements. View the full article
