alexc

Hi all, Over the past few months working on the A7Z, I’ve successfully ported a number of BSP drivers to Linux 6.18. The code is available here: https://github.com/alexcaoys/allwinner-bsp/tree/linux-6.18.y It’s currently tested on 6.18.19 and should, in theory, work with newer 6.18.y releases. I’ve tried to reuse as much upstream (mainline) drivers as possible, and have also upstreamed support for PCK600 and ET7304 used on the A7Z. Hopefully this helps accelerate ongoing mainline efforts. Feedback, issues, and PRs are very welcome. I may also look into creating branches for Linux 7.x in the future.

@Nick A No problem. Thanks for your Armbian build as well! I am also looking forward to mainline. Currently I still didn't find open source Mesa driver for Allwinner BSP, GLES is only available as pre-compiled binary for Debian (haven't tested it but it's in the Radxa images). There already are mainline Mesa/Linux IMG GPU supports so I hope things can be ported to mainline soon. Please let me know if anyone finds the source code for Mesa BSP.

@Nick A Oh yeah, I did change a few things as well for type c. Maybe the drm heap changes are not needed after all. Looking at my changes. husb311 is now under drivers/power/typec, so just enable it. et7304 is not included in the original bsp, radxa team added them later so simply apply this same patch. https://github.com/radxa/allwinner-bsp/commit/156b6578cc173855b41ea311a229403ccbadb17c

@Nick A @Bones558 Hi there, I am not sure if that's definitely due to DRM heap. But I fixed that driver and it could be built now. I didn't know if USB C DP works or not before but it is working now (on a USB C monitor, maybe needs a few re-plug). I opened a PR on Radxa allwinner-bsp github (https://github.com/radxa/allwinner-bsp/pull/11), you can also test it out.

I have a Radxa Zero 3E and was facing the same issue. Since RK3566 is a stripped down version of RK3588. I figured the quirks on RK3588 might be able to apply to RK3566 as well. The issue seems to be fixed now after I implemented these quirks taken from rk3588-base.dtsi on top of rk356x-base.dtsi. tested on Linux 6.17.9 and 6.18.0-rc7(Armbian linux-edge-rockchip64) usb_host1_xhci: usb@fd000000 { compatible = "rockchip,rk3568-dwc3", "snps,dwc3"; reg = <0x0 0xfd000000 0x0 0x400000>; interrupts = <GIC_SPI 170 IRQ_TYPE_LEVEL_HIGH>; clocks = <&cru CLK_USB3OTG1_REF>, <&cru CLK_USB3OTG1_SUSPEND>, <&cru ACLK_USB3OTG1>; clock-names = "ref_clk", "suspend_clk", "bus_clk"; dr_mode = "host"; phys = <&usb2phy0_host>, <&combphy1 PHY_TYPE_USB3>; phy-names = "usb2-phy", "usb3-phy"; phy_type = "utmi_wide"; power-domains = <&power RK3568_PD_PIPE>; resets = <&cru SRST_USB3OTG1>; snps,dis_u2_susphy_quirk; + snps,dis_enblslpm_quirk; + snps,dis-u2-freeclk-exists-quirk; + snps,dis-del-phy-power-chg-quirk; + snps,dis-tx-ipgap-linecheck-quirk; status = "disabled"; }; If anyone else has other RK356x devices please try it out and I think it would be nice if someone could submit a patch to mainline kernel dts.

well I guess I am too naïve about this lol. That's not the same as Raspberry Pi OS. I think Armbian is built for certain use cases. I tried CoreELEC, CEC and hardware acceleration work as expected. I understand maybe it's hard to bring all the stuff to the same distro/repo. Thanks for all the effort! btw now I know CEC is not modularized so it's not in /lib/modules. But CEC (at least cec-client or kodi) still won't work on Armbian

I am trying to use radxa-zero with HDMI CEC support on Armbian debian. I tried all different Armbian debian versions, lsmod never give me module cec So I took a look at images provided by radxa (https://github.com/radxa-build/radxa-zero/releases/tag/20220801-0213, not armbian ones), cec is loaded by default I think this is the key: /lib/modules/SOME_KERNEL/kernel/drivers/media/cec/core/cec.ko This is in their image but not /lib/modules/6.1.11-meson64 folder (I guess also not in other kernel versions) If that's the case, CEC should not work on any meson64 devices. I saw CONFIG_CEC_CORE=y is in config. btw, another possible related missing module is meson_dw_hdmi.ko Could someone take a look and figure out why they are not there? Really appreciate your help!

Hi everyone, I think I found a "solution" for Radxa Zero 1GB, at least for Debian Bookworm. I used armbian 22.08.1 Bullseye (Armbian_22.08.1_Radxa-zero_bullseye_current_5.10.139.img.xz) and apt upgraded everything to the latest (kernel == 6.1.11) I guess armbian 23.02.1 Bullseye (Armbian_23.02.1_Radxa-zero_bullseye_current_6.1.14.img.xz) should work too? Anyway, and then I flashed armbian 23.05.1 Bookworm (Armbian_23.5.1_Radxa-zero_bookworm_current_6.1.30.img.xz) (kernel == 6.1.30). I copied the /boot folder with everything == 6.1.11 as well as /lib/modules/6.1.11* to the SD card (need to match the partition UUID in armbianEnv.txt with the new partition) mount /dev/sdb1 MNTPOINT cp -r 6.1.11-meson64/ MNTPOINT/lib/modules rm -r MNTPOINT/boot cp -r boot/ MNTPOINT cp boot_6.1.30/armbianEnv.txt MNTPOINT/boot cd MNTPOINT rm initrd.img.old ln -s boot/initrd.img-6.1.11-meson64 initrd.img.old rm initrd.img ln -s boot/initrd.img-6.1.11-meson64 initrd.img rm vmlinuz.old ln -s boot/vmlinuz-6.1.11-meson64 vmlinuz.old rm vmlinuz ln -s boot/vmlinuz-6.1.11-meson64 vmlinuz umount MNTPOINT It successfully booted into the system. I tried a lot of stuff, but looks like removing both plymouth and fuse3 works. sudo apt remove plymouth fuse3 && sudo apt autoremove I am not sure where plymouth is used, but fuse3 only used by ntfs3g which I don't use at all. after everything, copy everything back and run sudo update-initramfs -c -v -k 6.1.30-meson64 This should update the initramfs. After reboot there will no longer be bootloops. Essentially I believe the problem is in initramfs but I am not sure why.