0x4E4F

They're still waiting to be mainstreamed into the kernel. The process of integrating drivers into the kernel is complicated. Coding practices of the coder that wrote the driver play a large part in that. Buggy or badly written code will not get accepted. Not all of these drivers have the code quality that is required in order to be merged with the kernel.

What's the deal with Nebraska? Are people from there like really polite and helpful?

Yeah, I know, that's why the kernel with the drivers is not more than 150MB. Otherwise, you'd have the Windows situation where driverpacks compressed with 7z (LZMA2, solid archive, 273 word dictionary size and 2GB decompression memory, which requires about 128GB of RAM to compress) take about 30GB.

You have to pack the driver from each manufacturer because of signatures, even though they might even be the same with other drivers in the pack... but, REV differs and oh well, the driver installer doesn't recognize that driver as a valid one for that device.

It's mind boggling just thinking that things like this depend on the effort of one or two guys... while on the other hand, it's not so uncommon that a team of engineers and developers fails to deliver a working (mostly) bugfree product.

I think management is who is responsible for the shitty decisions, as always... and, in general, just holding the team back.

Damn... now that's a wholesome moment 🥹.

To be honest, yes. In general, not just tech or Linux related stuff. You look at humanity and what it has come down to, and then you notice these people... and hope fills your heart again.