> We're asking the community to help us polish RK3576 support so we can build a truly open platform together. We'd be glad for any kind of contribution, not just code. For example, maybe you can find a way to convince Rockchip to open up that last blob.
Then it seems like they're inviting anyone to participate in the entire development process too, should you be inclined:
> Openness has always been our thing. With Flipper One, we want to go further — not just open-source code, but an open development process. We're publishing our task trackers, internal discussions, half-finished docs, and architectural debates. All the messy stuff companies usually keep behind closed doors.
Seems the post mentions a bunch of stuff people can help with, CTRL+F "help" shows 16 hits even, but I am afraid even this does require actually reading the content. It kind of feels like if you can't be assed to read enough to figure out what they need help with, maybe you don't actually want to help them with even harder and involved stuff than that?
Having a few various RPi's (as one does), when they've been out of stock, I've looked into the huge variety of similar SBCs (OrangePi, etc) which can be even faster, with more ports and features for around the same money than an equivalent RPi. Many are powered by various RockChip SoCs, which extend up to desktop replacement-level, but the Linux driver support is usually lacking in some important way.
It's not Linux's fault, it's a small group of volunteers struggling with little manufacturer support or documentation. I don't get why RockChip doesn't budget the money in the business plan to fund full driver support for at least some of their more capable chips. I guess maybe too many of these chips are used in non-OS contexts to be worth it?
Heck, if nothing else, the lack of a clear CTA would be on brand with OSS Marketing.
Edit: and to the sibling commenters as well