3 ms·
Correct me if I'm wrong, but this seems to confuse hardware support (e.g. drivers) for "working out of the box" with a particular distro. I have a CM4. It worke
by public_defender 4y ago
Correct me if I'm wrong, but this seems to confuse hardware support (e.g. drivers) for "working out of the box" with a particular distro. I have a CM4. It worked out of the box with RPi OS, but needed some hacking to get working with Alpine. The important thing is that it was possible to pull some configs from RPi OS to set up wifi on Alpine. The drivers were all in both kernels, so I assume they were in upstream, but had no reason to check.
I think the point of GP is that some hardware on these SBCs has no open source drivers and you can't get them, which is way different.
Also, again maybe I don't understand something, but the RPi OS is not "bastardized" in any special way. The whole point of the Linux ecosystem is that you bastardize things. It's actually good that there is a distro customized for RPi and that it submits some changes upstream but not all, right? I think GP was saying that they didn't want to depend on some weird hacks the manufacturer did to get closed hardware to work, which again is different.
- ilyt 4y ago> The drivers were all in both kernels, so I assume they were in upstream, but had no reason to check. Nope, not all is upstreamed, IIRC camera gave me grief, I just installed rasbpian after
- rwmj 4y agoFedora ships only upstream kernels, so working out of the box with Fedora is the same as being in the mainline (Linus) kernel.
- public_defender 4y ago> working out of the box with Fedora is the same as being in the mainline (Linus) kernel. That's not right. For example, in my case with wifi the microcode was named incorrectly and one of the other configs needed to be updated, but the drivers were there. Nobody has said what the problem is/is not in Fedora.
- rwmj 4y agoUnless Fedora renamed the microcode blob that's likely to be an upstream problem too.