@scaroo.bsky.social
Dunno about Metroid's HDR presentation, but you guys might be interested in this video from HDTVTest. Recent update fixed a lot of HDR calibration issues in docked mode.
www.youtube.com/watch?v=FDEo...
www.youtube.com/watch?v=FDEo...
Nintendo Just Updated HDR on Switch 2… Here’s What You Need to Change
YouTube video by HDTVTest
www.youtube.com
December 13, 2025 at 10:01 PM
Dunno about Metroid's HDR presentation, but you guys might be interested in this video from HDTVTest. Recent update fixed a lot of HDR calibration issues in docked mode.
www.youtube.com/watch?v=FDEo...
www.youtube.com/watch?v=FDEo...
And maybe some upload limits on the other side of the pipe (Steam/Epic/MS/... servers)
December 10, 2025 at 1:15 PM
And maybe some upload limits on the other side of the pipe (Steam/Epic/MS/... servers)
I guess network packets metadata (from Ethernet to TCP/IP) occupy a part of the bandwidth, also there might be some inefficiencies in the HW/SW of adapters drivers and OS network stacks.
December 10, 2025 at 1:14 PM
I guess network packets metadata (from Ethernet to TCP/IP) occupy a part of the bandwidth, also there might be some inefficiencies in the HW/SW of adapters drivers and OS network stacks.
"One of these is not like the others". Well, it is, the DL speeds looks very comparable to my eyes.
But yeah, I don't think I ever had a network connection, LAN or WAN, that actually hits its theoretical max.
But yeah, I don't think I ever had a network connection, LAN or WAN, that actually hits its theoretical max.
December 10, 2025 at 1:14 PM
"One of these is not like the others". Well, it is, the DL speeds looks very comparable to my eyes.
But yeah, I don't think I ever had a network connection, LAN or WAN, that actually hits its theoretical max.
But yeah, I don't think I ever had a network connection, LAN or WAN, that actually hits its theoretical max.
Am I understanding this wrong, or did we forget that a megabyte is 8 megabits, not 10 ?
Halo and Avatar downloads peaks at around 115-117 megabytes per sec, whereas Indy goes at 106 (848 / 8).
Not a notable difference, IMHO
Halo and Avatar downloads peaks at around 115-117 megabytes per sec, whereas Indy goes at 106 (848 / 8).
Not a notable difference, IMHO
December 10, 2025 at 12:41 PM
Am I understanding this wrong, or did we forget that a megabyte is 8 megabits, not 10 ?
Halo and Avatar downloads peaks at around 115-117 megabytes per sec, whereas Indy goes at 106 (848 / 8).
Not a notable difference, IMHO
Halo and Avatar downloads peaks at around 115-117 megabytes per sec, whereas Indy goes at 106 (848 / 8).
Not a notable difference, IMHO
Il aurait fallu mettre de l'aneth pour un saumon parfait.
Je connais la sortie.
Je connais la sortie.
December 8, 2025 at 10:28 AM
Il aurait fallu mettre de l'aneth pour un saumon parfait.
Je connais la sortie.
Je connais la sortie.
Blanchiment, transfert d'argent au noir, fraude fiscale, rémunération d'activités illégales... Que des trucs reluisants.
Et au-dessus de ces usages fournissant une valeur intrinsèque au bousin, la spéculation gonfle la baudruche.
Et au-dessus de ces usages fournissant une valeur intrinsèque au bousin, la spéculation gonfle la baudruche.
December 3, 2025 at 12:41 PM
Blanchiment, transfert d'argent au noir, fraude fiscale, rémunération d'activités illégales... Que des trucs reluisants.
Et au-dessus de ces usages fournissant une valeur intrinsèque au bousin, la spéculation gonfle la baudruche.
Et au-dessus de ces usages fournissant une valeur intrinsèque au bousin, la spéculation gonfle la baudruche.
I should again have done my homework then. Sorry for stating otherwise, and thank you for your involvement and investment in the ecosystem!
December 3, 2025 at 12:32 PM
I should again have done my homework then. Sorry for stating otherwise, and thank you for your involvement and investment in the ecosystem!
Ok, I read the article, what I should have done before reacting. Lesson learned. Valve was indeed there at the beginning of FEX, and supported nearly from day one its developer.
December 2, 2025 at 8:48 PM
Ok, I read the article, what I should have done before reacting. Lesson learned. Valve was indeed there at the beginning of FEX, and supported nearly from day one its developer.
You can't overstate their impact, their contribs and investment really gave those projects a shot in the arm, sometimes rescuing them from being totally unusable, to be fair. But let's not miscredit anyone or pretend we don't see all the other folks and companies who actually laid the groundwork.
December 2, 2025 at 8:32 PM
You can't overstate their impact, their contribs and investment really gave those projects a shot in the arm, sometimes rescuing them from being totally unusable, to be fair. But let's not miscredit anyone or pretend we don't see all the other folks and companies who actually laid the groundwork.
From what I understand, FEX was already around long before Valve got into the picture with direct contributions or financial backing.
The same goes for Wine, DXVK, VK3D, and RADV.
The same goes for Wine, DXVK, VK3D, and RADV.
December 2, 2025 at 8:32 PM
From what I understand, FEX was already around long before Valve got into the picture with direct contributions or financial backing.
The same goes for Wine, DXVK, VK3D, and RADV.
The same goes for Wine, DXVK, VK3D, and RADV.
Pour que les gens y... viennent.
Ah mince, je ne suis pas sur le chat de CPC, ni ne suis oscar_tilage!
Ah mince, je ne suis pas sur le chat de CPC, ni ne suis oscar_tilage!
December 2, 2025 at 4:06 PM
Pour que les gens y... viennent.
Ah mince, je ne suis pas sur le chat de CPC, ni ne suis oscar_tilage!
Ah mince, je ne suis pas sur le chat de CPC, ni ne suis oscar_tilage!
Something to also remember is that most (all?) of their datacenters deployments for AI, and their own little machine, the Spark, run on Linux.
-- written from my 6900xt (because, yeah, AMD, Red Hat, Valve, Collabora and other companies/individuals are much, much better FLOSS citizen, still) ;)
-- written from my 6900xt (because, yeah, AMD, Red Hat, Valve, Collabora and other companies/individuals are much, much better FLOSS citizen, still) ;)
December 1, 2025 at 7:53 PM
Something to also remember is that most (all?) of their datacenters deployments for AI, and their own little machine, the Spark, run on Linux.
-- written from my 6900xt (because, yeah, AMD, Red Hat, Valve, Collabora and other companies/individuals are much, much better FLOSS citizen, still) ;)
-- written from my 6900xt (because, yeah, AMD, Red Hat, Valve, Collabora and other companies/individuals are much, much better FLOSS citizen, still) ;)
Those kinks are currently being worked out, but the performance debt still surfaces.
That's why, in detailed analyses (like those Gamers Nexus benchmarks), you still occasionally see weird frame-time inconsistencies or unexpected performance drops for Nvidia vs. AMD.
That's why, in detailed analyses (like those Gamers Nexus benchmarks), you still occasionally see weird frame-time inconsistencies or unexpected performance drops for Nvidia vs. AMD.
December 1, 2025 at 7:46 PM
Those kinks are currently being worked out, but the performance debt still surfaces.
That's why, in detailed analyses (like those Gamers Nexus benchmarks), you still occasionally see weird frame-time inconsistencies or unexpected performance drops for Nvidia vs. AMD.
That's why, in detailed analyses (like those Gamers Nexus benchmarks), you still occasionally see weird frame-time inconsistencies or unexpected performance drops for Nvidia vs. AMD.
While the open ecosystem built around shared standards (like GBM and Explicit Sync), Nvidia's display pipeline lagged behind.
This led to inefficiencies and outright incomp that have required huge engineering effort to solve, often by making the open stack accommodate the proprietary one. 😩
This led to inefficiencies and outright incomp that have required huge engineering effort to solve, often by making the open stack accommodate the proprietary one. 😩
December 1, 2025 at 7:45 PM
While the open ecosystem built around shared standards (like GBM and Explicit Sync), Nvidia's display pipeline lagged behind.
This led to inefficiencies and outright incomp that have required huge engineering effort to solve, often by making the open stack accommodate the proprietary one. 😩
This led to inefficiencies and outright incomp that have required huge engineering effort to solve, often by making the open stack accommodate the proprietary one. 😩
Despite the great progress in drivers, Nvidia's historical decision to "do their own thing" in their corner left a lot of proprietary baggage.
The cost of that isolation became painfully clear during the mass transition to Wayland.
The cost of that isolation became painfully clear during the mass transition to Wayland.
December 1, 2025 at 7:44 PM
Despite the great progress in drivers, Nvidia's historical decision to "do their own thing" in their corner left a lot of proprietary baggage.
The cost of that isolation became painfully clear during the mass transition to Wayland.
The cost of that isolation became painfully clear during the mass transition to Wayland.
In 2022, hell froze over. Nvidia released their official Open Kernel Modules.
Because the GSP handles the sensitive proprietary work, Nvidia could finally release a GPL-compliant kernel driver. It’s not fully upstream yet, but it allows legal integration with the Linux kernel for the first time.
Because the GSP handles the sensitive proprietary work, Nvidia could finally release a GPL-compliant kernel driver. It’s not fully upstream yet, but it allows legal integration with the Linux kernel for the first time.
December 1, 2025 at 7:40 PM
In 2022, hell froze over. Nvidia released their official Open Kernel Modules.
Because the GSP handles the sensitive proprietary work, Nvidia could finally release a GPL-compliant kernel driver. It’s not fully upstream yet, but it allows legal integration with the Linux kernel for the first time.
Because the GSP handles the sensitive proprietary work, Nvidia could finally release a GPL-compliant kernel driver. It’s not fully upstream yet, but it allows legal integration with the Linux kernel for the first time.
Later, they moved the "secret sauce" (power management, scheduling) out of the driver and into the GSP firmware.
The driver became a "dumb" messenger. Since the logic was now in hardware, the kernel driver could finally be Open Source without leaking IP
The driver became a "dumb" messenger. Since the logic was now in hardware, the kernel driver could finally be Open Source without leaking IP
December 1, 2025 at 7:39 PM
Later, they moved the "secret sauce" (power management, scheduling) out of the driver and into the GSP firmware.
The driver became a "dumb" messenger. Since the logic was now in hardware, the kernel driver could finally be Open Source without leaking IP
The driver became a "dumb" messenger. Since the logic was now in hardware, the kernel driver could finally be Open Source without leaking IP
This isolation is why things like Wayland were a nightmare on Nvidia for so long.
While the ecosystem coalesced around standard allocators (GBM), Nvidia tried to force their own path (EGLStreams) because they weren't part of the shared DRM/KMS infrastructure used by everyone else.
While the ecosystem coalesced around standard allocators (GBM), Nvidia tried to force their own path (EGLStreams) because they weren't part of the shared DRM/KMS infrastructure used by everyone else.
December 1, 2025 at 7:38 PM
This isolation is why things like Wayland were a nightmare on Nvidia for so long.
While the ecosystem coalesced around standard allocators (GBM), Nvidia tried to force their own path (EGLStreams) because they weren't part of the shared DRM/KMS infrastructure used by everyone else.
While the ecosystem coalesced around standard allocators (GBM), Nvidia tried to force their own path (EGLStreams) because they weren't part of the shared DRM/KMS infrastructure used by everyone else.
This is where the friction started. Intel and AMD played ball, contributing to shared GPU subsystems like DRM (Direct Rendering Manager) and KMS (Kernel Mode Setting).
Nvidia? They ignored those standard interfaces because their proprietary blob couldn't legally/technically integrate with them.
Nvidia? They ignored those standard interfaces because their proprietary blob couldn't legally/technically integrate with them.
December 1, 2025 at 7:37 PM
This is where the friction started. Intel and AMD played ball, contributing to shared GPU subsystems like DRM (Direct Rendering Manager) and KMS (Kernel Mode Setting).
Nvidia? They ignored those standard interfaces because their proprietary blob couldn't legally/technically integrate with them.
Nvidia? They ignored those standard interfaces because their proprietary blob couldn't legally/technically integrate with them.
Because the GPL disallows linking the kernel with closed-source code, Nvidia had to use a "shim."
They shipped a massive, proprietary blob that sat outside the kernel, communicating via a thin open-source wrapper. This technically worked, but it made them a legal and structural alien.
They shipped a massive, proprietary blob that sat outside the kernel, communicating via a thin open-source wrapper. This technically worked, but it made them a legal and structural alien.
December 1, 2025 at 7:37 PM
Because the GPL disallows linking the kernel with closed-source code, Nvidia had to use a "shim."
They shipped a massive, proprietary blob that sat outside the kernel, communicating via a thin open-source wrapper. This technically worked, but it made them a legal and structural alien.
They shipped a massive, proprietary blob that sat outside the kernel, communicating via a thin open-source wrapper. This technically worked, but it made them a legal and structural alien.
The issue was never technical incompetence; it was Licensing.
The Linux Kernel is GPL. Ideally, drivers are open-source and part of the upstream kernel. Nvidia refused to open their source to protect their IP (the "secret sauce" of their scheduler and memory management).
The Linux Kernel is GPL. Ideally, drivers are open-source and part of the upstream kernel. Nvidia refused to open their source to protect their IP (the "secret sauce" of their scheduler and memory management).
December 1, 2025 at 7:37 PM
The issue was never technical incompetence; it was Licensing.
The Linux Kernel is GPL. Ideally, drivers are open-source and part of the upstream kernel. Nvidia refused to open their source to protect their IP (the "secret sauce" of their scheduler and memory management).
The Linux Kernel is GPL. Ideally, drivers are open-source and part of the upstream kernel. Nvidia refused to open their source to protect their IP (the "secret sauce" of their scheduler and memory management).
If you needed professional-grade OpenGL or high-FPS gaming on Linux in the 2010s, you bought Nvidia. Period.
Their proprietary driver was parity-matched with Windows. They were often the first to implement new Vulkan extensions and pushed the API forward massively. The silicon was never the problem.
Their proprietary driver was parity-matched with Windows. They were often the first to implement new Vulkan extensions and pushed the API forward massively. The silicon was never the problem.
December 1, 2025 at 7:37 PM
If you needed professional-grade OpenGL or high-FPS gaming on Linux in the 2010s, you bought Nvidia. Period.
Their proprietary driver was parity-matched with Windows. They were often the first to implement new Vulkan extensions and pushed the API forward massively. The silicon was never the problem.
Their proprietary driver was parity-matched with Windows. They were often the first to implement new Vulkan extensions and pushed the API forward massively. The silicon was never the problem.
@dachsjaeger.bsky.social @digitalfoundry.bsky.social Hot take: Historically, Nvidia didn't have "bad" Linux support. In fact, for a long time, they were the only option for serious perf.
The narrative that Nvidia failed Linux is a misunderstanding of a legal standoff masquerading as a technical one.
The narrative that Nvidia failed Linux is a misunderstanding of a legal standoff masquerading as a technical one.
December 1, 2025 at 7:36 PM
@dachsjaeger.bsky.social @digitalfoundry.bsky.social Hot take: Historically, Nvidia didn't have "bad" Linux support. In fact, for a long time, they were the only option for serious perf.
The narrative that Nvidia failed Linux is a misunderstanding of a legal standoff masquerading as a technical one.
The narrative that Nvidia failed Linux is a misunderstanding of a legal standoff masquerading as a technical one.