惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

T
The Blog of Author Tim Ferriss
Hugging Face - Blog
Hugging Face - Blog
F
Fortinet All Blogs
B
Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Microsoft Security Blog
Microsoft Security Blog
Blog — PlanetScale
Blog — PlanetScale
月光博客
月光博客
腾讯CDC
小众软件
小众软件
G
Google Developers Blog
V
Visual Studio Blog
罗磊的独立博客
GbyAI
GbyAI
V
V2EX
大猫的无限游戏
大猫的无限游戏
H
Help Net Security
L
LangChain Blog
Engineering at Meta
Engineering at Meta
量子位
The GitHub Blog
The GitHub Blog
博客园 - 司徒正美
WordPress大学
WordPress大学
B
Blog RSS Feed

LWN.net comments

tcmalloc's weird hack [LWN.net] Fixed? [LWN.net] mpd [LWN.net] Userspace AX.25 [LWN.net] RIP [LWN.net] My two cents... [LWN.net] pipx [LWN.net] Tragedy [LWN.net] A young man destined for glory [LWN.net] And 'less' won't let you search [LWN.net] A great loss [LWN.net] Sad and shocking news [LWN.net] Easy migration from Clementine [LWN.net] Sad coincidence [LWN.net] GNOME is actually usable thanks to Seth et al [LWN.net] Sad news :( [LWN.net] armhf supports preempt_rt [LWN.net] MusicBrainz accurracy [LWN.net] On open source maintainership [LWN.net] Let's stop here [LWN.net] Not a new thing [LWN.net] uv is indeed great pgmoneta Some comments on this on a Postgres blog feed [LWN.net] uv [LWN.net] going to Debian [LWN.net] Upgrading 64-bit-capable systems to 64-bit kernels? [LWN.net] Free Software foundations Maintainers can wait for code review but not for publish review? A reasonably extreme point of view [LWN.net]
Proprietary software enablement, not hardware [LWN.net]
farnz · 2026-05-15 · via LWN.net comments

Proprietary software enablement, not hardware

Posted May 15, 2026 10:57 UTC (Fri) by farnz (subscriber, #17727)
In reply to: Seriously? by AdamW
Parent article: Friction in Fedora over AI developer desktop initiative

Yeah - that's kinda my point. When you strip this proposal down to the concrete actions that will be taken, it's just "we should enable people to use NVidia's proprietary userspace on Fedora", and nothing else - calling it "hardware enablement" isn't really accurate, either, because it's not just about enabling the use of NVidia hardware, but about enabling the use of NVidia's proprietary APIs, too.

I would feel very differently about it if it was (say) "we're going to make ZLUDA work on all the big Mesa Vulkan drivers so that you could use CUDA code on AMD, Intel or NVidia hardware", or even "we're going to support running ML models on NVidia proprietary Vulkan to the same extent they're supported on RADV and ANV". But instead, it's "well, NVidia's proprietary CUDA userspace is popular, so we should support that".