ColorfulRhino

> I was unaware that the RTW88 had difficulties with AP mode. I didn't check on how many cards this statement might apply, but I can imagine the experience may...

I didn't realize there were more discussions going on here 😅 I apologize if I annoyed anyone, that was not my intention. I also apologize if my earlier comments were...

> The CURRENT patch dir is 16M. I'm not a mathematician, but if you add those two numbers together it doesn't seem like we are adding much to `armbian/build`. Plus....

> At first login armbian can't detect SSIDs so I just press Enter for null ssid and password. Maybe we need to 1) check if the network can be connected...

> `Package.xz` is smaller and need less time to download. I've been avoiding everything `xz` since the malicious takeover was uncovered (yes I know the known malicious code was ripped...

> As for me I never had an issue with missing xz-utils on any host I did building. Thanks for sharing your experience! I have changed it to xz since...

> I've a stop-gap workaround (needs manual updating) Needing to manually update anything is the bane of many projects 😅 Automation is key imho, even if it costs more energy...

> CMA turns as "reserved" memory to the linux kernel and therefore it cannot be used by userland processes. Since the rockchip64 kernel also applies to smaller rk3328 devices, reserving...

I wonder how mainline does/will handle this CMA size 😄

Nice! This will clash with https://github.com/armbian/build/pull/6822 though. I think we can integrate `ROCKUSB_BLOB` into `rockchip64.conf` instead of having it on each board separately, what do you think?