zlacker

>>todsac+(OP)
I totally understand the Frustration the author has here. But I'd rather have any working software version than 10 that don't work well at all and that has always been my pine64 experience. Great hardware, barely any documentation, important hardware and software features don't work at all or are locked behind a very old kernel version

>>dtx1+y9
According to TFA (which I don't know enough to verify), the >10 distributions that "don't work well" are the ones pushing the platform forward and solving problems one by one. The blessed monoculture distribution is about packaging other people's work and doesn't really contribute to the development, in fact they only add annoyance due to shitty packaging policy, so with the other distributions pissed off, they won't have stuff to pick up. That's not a promising path to "one working version".

>>oefrha+uo
The question is to what extent it's an accurate characterization.

There are two levels to this:

Kernel development / HW specific support. This is mostly being done by people unrelated to any distro, or unrelated to Pine64 at all. (linux-sunxi community, Google, linaro, bootlin, lima project, libreelec, and various individuals) One exception is Martijn, who did initial bringup for Pinephone Pro, and Mobian's maintainer. Nevertheless, vast majority of ongoing improvements, bugfixes, and HW support work comes from outside of mobile distros, and always did, even the work focused directly at the Pinephone SW support. And these efforts were not supported by Pine64 in any comparable way to how distros were supported initially.

Then there's userspace application work, and integrating all the normal user facing SW into a cohesive whole. This is where the distros come in. I don't know much about struggles with that.

So yeah, don't forget that TFA is just a view of one person, and the sky is not falling. (well, aside from the war, and energy crisis, ... but hey)

>>megous+gb2
Mobian and pmOS do a huge amount of work wrt. bringing up overall support for OEM devices. The other efforts you mention mostly work at lower levels of the stack, focusing on supporting individual SoC's or IP blocks. Both are very much necessary, but if you care about polishing support for a specific OEM device the mobile distros are doing much of that work.

>>zozbot+Wc2
I'm talking specifically about pinephone.

>>megous+gg2
The point still applies. Do you really expect Linaro or Bootlin to be working on completing mainline support for the PinePhone, Pinephone Pro and other Pine64 devices? That seems like it would be a job for the distros.

>>zozbot+4k2
I don't expect anything. I'm just telling you how it is, as a maintainer of the pinephone kernel that most of the distros use, and the rest heavily borrow patches from.