Linux's Sole Wireless/WiFi Driver Maintainer Is Stepping Down - Phoronix
-
I mean, probably someone at qualcomm will likely take his place? They need drivers for themselves anyway and will probably continue providing them. I have no idea who the contributors of similar drivers are but I'd imagine Intel makes drivers for their wifi chips themselves and contributes them to the kernel since they count as one of the biggest contributors.
-
It's better if the titular Steve isn't from US. Right now at least.
-
Steve burned out a long time ago after all the free work he did on top of his day job.
-
And Intel, Qualcomm, or AMD. Or probably several others as well.
-
Post in addition to the link.
-
Seems like nowadays Nebraska guy is more likely to be a rabid Trump supporter who likes the way things have been so far in 2025. š¤®
-
It turns out people switch jobs, retire, or just burn out. Other maintainers can cover while they select a new one.
-
Except OP.
-
That also happens. I'm honestly surprised they lasted that long, doing any OS work on Apple hardware sucks. You have a small user base and an even smaller contributor base, poor documentation, and zero support from the manufacturer. It's the perfect storm of headwinds.
-
That's great! Any idea who?
-
It's gotta change to true community, where we lift each other up, looking to the future, readying others to take our mantle when we retire. That's the only way FOSS will thrive and have a chance to compete with corpos.
-
Note that this isn't exclusive to FOSS, but it's just more transparent.
Over the last decade I've seen my work retire and replace with something not quite the same about 3 times now, owing mainly to some lead retiring and the replacement getting to finally throw it all away like he thought should have been done years ago.
But even in the more mundane case of things continue, it happens all the time in long standing corporate projects. Sometimes you can catch a whiff of a strong shift in direction (e.g. Windows 8 went hard on UWP and actively discouraged development using any of the long standing interfaces that Windows applications were traditionally built on). An announcing of retiring doesn't mean anything will necessarily change at all, or if it changes in a bad way there may be course correction.
-
Where did you read that? I only saw Johannes Berg saying he couldn't maintain that stack too, after three days.
-
You're right that there are many drivers and people from manufacturers responsible for hardware families, but there still needs to be a maintainer for the subsystem as a whole.
That person reviews what the manufacturers and other contributors send in, to validate that things are still compatible where they touch in the kernel, and that the code is good enough. They then prep the commits of the subsystem for inclusion into the next kernel version and pass that to Linus, is my understanding.
-
A number of them have written about their reasons- I can't speak for the maintainer this article is about but the general sentiment I've seen from the ones I've been hearing about is that the culture around kernel development is dogwater. Lots of it surrounding refusal to make any space for R4L and shitting on devs working on it, but then also spinning out of that are maintainers likening their quality control responsibilities to being "the thin blue line".
-
This is the kind of stuff that makes it really hard to justify using linux.
I was told to use Mint because I was told it would work with modern hardware.
Can I just update the Kernal sonehow? or does that require a reinstall of Mint?
-
You could install an alternative kernel and install that, but this would most likely fuck your mint install since it is built for that specific major kernel version eg. You only get x.xx.->yy<- updates, rest needs major mint upgrade which they release ālateā compared to rolling distros like openSuse Tumbleweed.
Maybe there is an up to date out of tree version of the kernel from lwfinger that you can install, which dongle did you get?
The problems you encounter exist, because of the popular chicken and egg problem, where chip designer ignore linux due to user base and user base is small because of not same chip support as proprietary OSs.
-
Ah cool, the one time I read the article it's wrong and saying that there hadn't been someone who had stepped up yet.
Well, I'll go back to making uninformed comments based solely on the headline, because clearly the articles are not adding any value. (/s, etc.)
-
If you can't bite it, it doesn't exist.
-
Weird thatās what my girlfriend says.