3 ms·
This would absolutely all be done with upstreamability in mind, and upstreamed as soon as is practical. All that horrible forked kernel stuff is the realm of c
by marcan_42 6y ago
This would absolutely all be done with upstreamability in mind, and upstreamed as soon as is practical.
All that horrible forked kernel stuff is the realm of companies with closed development teams who don't care and just want a product out the door.
The PS4 Linux stuff I did was not upstreamed for lack of time/interest, but I absolutely considered it being decent enough to upstream when writing it. PS3 Linux running under GameOS mode patches were indeed upstreamed (though there was a bit of a lawsuit along the way so all of my code ended up attributed to a friend instead since I was keeping a lower profile at the time...).
- lmm 6y ago> All that horrible forked kernel stuff is the realm of companies with closed development teams who don't care and just want a product out the door. Or people who gave upstreaming an honest try but got fed up. It's not the easiest project to contribute to.
- marcan_42 6y agoYou do need to know what you're doing, meet quality standards, and do things in a way that fits existing architecture (unless you have a really good reason to revamp something). It's not beginner-friendly for sure, but I can tell you the vast majority of non-upstreamed vendor code is not upstreamed because it's terrible (which is also bad for users: things like blatant security problems are much more common in forks than upstream).
- krageon 6y agoIf you can't be bothered to learn how to write linux kernel patches properly you shouldn't be making them at all, in a forked kernel or otherwise.