Mostly that it doesn’t work on Steam Deck. Hits memory limits IIRC.

Harsh words for someone who continues to be their client

It would allow them to do HDMI FRL also, which is probably what you mean when you say HDMI 2.1. AMD cards also do HDMI FRL I thought. FRL is what allows things like 4k120Hz (higher bandwidth modes). The VRR that the Dock does is the VRR standardized with 2.1, which is why it works on TVs and devices that do not support freesync (see: LG TVs).

Anyway, the Dock doesn’t have a fast enough HDMI converter to do that. It’s not a licensing issue. Next gen Deck/Dock will probably do it.

Actually it works fine on Steam Deck. It uses VRR over DP to the dock, which then translates it to HDMI with VRR. The dock has proprietary firmware to do this.

Intel and Nvidia hardware with open source kernel drivers also do a similar trick where the HDMI part is in a firmware blob. Only AMD does not work with HDMI VRR.

Exactly. That’s why it’s a trash motherboard as soon as root access is gained. It can never again be trusted.

How do you trust that the flash was done properly if you did it from the compromised system? This would only work if you flashed it externally somehow without the system running.

Yes it is. It’s not in mainline wine, it’s been in kernel for a long time now.

It’s annoying all the articles are focusing on performance versus stock wine here when basically everyone uses Proton or a fork of it anyway, which has had fsync for years now that does similar performance uplift.

The story here should be that we’re getting fsync level performance with fewer bug and it can be upstreamed to wine. There is no relevant performance uplift for Proton users, but I guess performance gets clicks so that’s the story all the press are going with.

It’s not merged, but the benchmarks are against upstream wine. Proton has hacks (fsync) that have almost identical performance uplift but were not suited to upstreaming.

So basically this will improve “correctness” versus current Proton, not performance. Should fix some bugs and improve compatibility.

Versus stock wine, it’s a huge perf uplift though.

Knowing Mozilla it’s probably done client side (meaning it sends weather data for all major regions or something and the client filters what is needed)

Technically AMD also offers an open Vulkan driver (AMDVLK), it’s just dog shit, and an open compute driver (Rocm), its just also bad, and an open OpenGL driver (Radeonsi), which is solid.

Those three are all primarily developed by AMD engineers and are fully open. Nvidia has no such open equivalents.

Uhh nvidia has had native Linux drivers since the 1990’s…

I stopped getting those once I got rid of my +1 number. For some reason even after 6 years my +31 doesn’t get them.

The last one was on a QPR beta, and the one before that was on the A14 stable launch version.

This case is definitely more understandable but after 2 worse ones it’s still a bad look.

So… Third major data loss update in the last 6 months?

Ok… That’s too long. Weird decision.

I suspect the small delay is just to prevent them from going crazy if you swing your mouse over the tab bar, it’s not going to be like a second or something. Sounds useful for the case of multiple tabs on the same site with similar titles, especially at higher resolutions.

I haven’t used it because most games don’t work or have as good of performance. Benefits in short term will be things like in-tree kernel module, better working relationship and bug fixes with open projects like KDE/Gnome and maybe things like Gamescope or VR.

Now, if you want. There will probably always be tradeoffs between the two drivers so I doubt this will ever match Nvidia’s across the board, just have to pick your poisons.

Yes, and? That reinforces what I’m saying. As long as they don’t install the cookies, the user can browse the site without seeing the banner. Therefore if the user blocks the banner, they can’t install the cookies, that doesn’t mean they can’t show the user the site.

Not sure what’s hard to understand here.