<chewitt>
^ noticing that yours appears to be different to mine
<Armbian-Discord>
<adeepv> from armbian-firmware package. this was mix from linux-firmware and my firmware
<chewitt>
so your firmware works, and the one upstream linux-firmware doesn't
<chewitt>
do you have the original files in a Jethome git repo along with Realtek license details?
<chewitt>
or are they obtainable from a realtek website location?
<chewitt>
(upstream cares deeply about blob provenance)
<chewitt>
at least that means everything works with M2S dts now .. although I will need to drop the WiFi/BT bits into an overlay since it's an optional board
<chewitt>
now to decide whether to cripple CPU opp-points like BPI did, or leave them as-is on the assumption anyone sane will use a heatsink fan with an A311D board
<chewitt>
and add the GPIO details
<chewitt>
the second one is connected via PCIe so needs CONFIG_R8169 enabling in defconfig (normally not set for ARM)
<Armbian-Discord>
<adeepv> chewitt: i received this firmware with full android repo. there are no licenses or extracts from them. this firmware is not available on the realtek website.
<chewitt>
thanks
<chewitt>
I've narrowed the problem to rtl8822cs_config.bin
<chewitt>
I can run the latest upstream fw file, but need to use your config.bin
<chewitt>
I'll report the regression upstream and see what happens
<Armbian-Discord>
<adeepv> chewitt: I would love to watch this 🙂
<Armbian-Discord>
<adeepv> chewitt: did you get the rtl8822cs to run on the new rtw88 driver?
<chewitt>
Yes, no problems with that
<chewitt>
So (to check) origins of the Armbian files are an Amlogic BSP codebase provided to Jethome?
<Armbian-Discord>
<adeepv> chewitt: I'll check if we can say that officially) btw i checked the repository again, there are new files now..
<chewitt>
please share the latest files somehow (email if needed)
<chewitt>
but I don't think it changes anything .. I can use latest upstream fw file, but only your config
<chewitt>
so there's either a driver bug that prevents upstream config working .. or the config is missing something
<chewitt>
(is my guess)
<chewitt>
is there any commit history in the repo you're looking at?
<Armbian-Discord>
<adeepv> chewitt: i've sent to you binaries
<Armbian-Discord>
<adeepv> chewitt: commit log is empty: "Cherrypick: merge all code from internal to google" but tv.tar has one more message: "wifi: Android R support multibt"
<chewitt>
that sounds like a bt version of dhd
<chewitt>
one config described in device-tree and magic to find/use the right sub-driver/firmware
<Armbian-Discord>
<adeepv> chewitt: ¯_(ツ)_/¯
<chewitt>
the bt.tar file you shared has the oldest/original upstream firmware inside, but fw+config load fine
<chewitt>
the tv.tar file appears to have the same firmware
<chewitt>
different config file (different hash) but also working fine
<chewitt>
so upstream has much newer firmware, but bad config
<chewitt>
oddly, the firmware that Armbian is using is newer than the one from the Amlogic repo
<Armbian-Discord>
<adeepv> this repo seems to be 1-2 years old already
<chewitt>
I'll act surprised :)
<chewitt>
btw, does Jethome have any interest in media capabilities?
<Armbian-Discord>
<adeepv> chewitt: on our boards no audio/video interfaces. maybe for hw transcoding video
<chewitt>
the encoding drivers look quite simple (unlike the decoders)
<chewitt>
i'm in search of someone/anyone to poke the decoders :)