Valve tells Ars its "trying to unblock" limits caused by open source driver issues.
See full article...
See full article...
lol, not the part where they get their moneySurprise surprise, I thought that anything could be listed is as HDMI2.1 since much of the standard is optional. If valve was a blackhat I wonder if they could still LEGALLY say it's HDMI2.1![]()
They control the use of the logo, branding, and IP rights to the HDMI standard, and are the ones to certify compliance.I wonder how exactly the HDMI Forum exerts their authority. Are they saying Valve cannot advertise 2.1 support if they're using the open-source drivers? Could Valve just do the implementation and not advertise it? Has AMD signed some agreement with the Forum and they'd violate it with an open source implementation? Is it a patent issue?
Just guessing, but HDMI Forum probably has a patent pool that can only be licensed under certain conditions (not open-sourcing NDA'd inner workings). Do it anyway, and you're violating not only the NDAs you signed to get access to the spec, but also violating the license agreement and thereby opening yourself up to patent suits.I wonder how exactly the HDMI Forum exerts their authority. Are they saying Valve cannot advertise 2.1 support if they're using the open-source drivers? Could Valve just do the implementation and not advertise it? Has AMD signed some agreement with the Forum and they'd violate it with an open source implementation? Is it a patent issue?
Unless you're manufacturing your stuff in the US, they may also intercept and smash up your devices on entry to the country as counterfeit goods.Just guessing, but HDMI Forum probably has a patent pool that can only be licensed under certain conditions (not open-sourcing NDA'd inner workings). Do it anyway, and you're violating not only the NDAs you signed to get access to the spec, but also violating the license agreement and thereby opening yourself up to patent suits.
There are patents and licenses tied to the actual implementation of features such as HDMI-VRR. So it's not just that they can't advertise it or even advertise it with a wink under a different term, but they can't legally implement or enable something like HDMI-VRR without approval.I wonder how exactly the HDMI Forum exerts their authority. Are they saying Valve cannot advertise 2.1 support if they're using the open-source drivers? Could Valve just do the implementation and not advertise it? Has AMD signed some agreement with the Forum and they'd violate it with an open source implementation? Is it a patent issue?
which supports even more bandwidth than HDMI 2.1 (and which can be converted to an HDMI signal with a simple dongle).
seems like this machine is doa
Steam Machine is essentially a custom PC in a 6inch cube form.Given that the Steam Machine is made by themselves, can't they just use a close source driver for the HDMI 2.1 stuff?
Depends on the game, doesn't it? An older game that isn't as visually demanding might run at 120FPS at 4K just fine, no? It's not like you can only play the latest greatest games on Steam. . . they have a back catalog stretching what, 20 years?https://meincmagazine.com/gadgets/202...ems-with-8gb-gpus-but-valve-is-working-on-it/
From the tests of similar GPUs, this machine isn't going to be doing 120FPS while playing at 4K, so it's probably a non issue.
I wish there was a solution like this for the Switch 2 that has a similar issue because of the USB-C connection. The HDMI stranglehold on the industry is bad for everyone except for the people making money off it.This got me wondering if Valve could get away with "one little trick" and just make it internally a DP port (as far as the driver is concerned) and wire it to an external port that is just an HDMI 2.1 dongle in disguise?
To the user, it just looks like an HDMI port on the back of the case. . .
Although that probably means that in OS management tools, you have 2 DisplayPort ports show up, and zero HDMI, which might be a technical support issue as users get confused.
Patents can both help progress and innovation in the big picture and long term while also hobbling it in the short term. I'm curious what economists would have to report on the history of that, but I'm sure even they have plenty of different conclusions and arguments about it too. Either way, it stinks in the short termThe whole original justification for creating "Intellectual Property" (copyright, patents) laws was they were supposed to promote progress & innovation to benefit all.
But it's become mostly an extortion racket that hobbles progress & innovation. Instead of supporting creators, they reward gatekeepers.
If we're willing to play semantics, my AORUS FO48U monitor is basically just a rebadged LG C2 but with a DisplayPort and KVM instead of a tuner. There was also the Philips 558M1RY, which was a 55" monitor, but similarly had no TV functionality.So do DisplayPort TVs exist or is HDMI bribing TV makers to stay HDMI-only?
If you check out the other Ars article linked above, AMD literally wrote the driver to support it and the HDMI mafia barred them from releasing it.It sounds like it's a general Linux issue more than a Steam Machine issue. Hopefully Valve puts enough development effort into this to solve it for everybody running Linux.
And honestly, given what appears to be the relatively modest specs of the Steam Machine this doesn't seem likely to be a big issue. Pushing enough pixels to require HDMI 2.1 is probably beyond what the box can do on most games.
Does it even matter at this point other than for small indie games, older games, or the UI?
The hardware can barely handle 1080p/1440p60 at native resolution for most modern games, I doubt it'll be able to hit 4k/120 in most games...
As mentioned in the article, there's a DisplayPort 1.4 port if the user really cares that much.seems like this machine is doa
Just the opposite - if it could maintain 4K120 then it wouldn't need VRR. But since it can't, that makes VRR an even more useful feature to have.From the tests of similar GPUs, this machine isn't going to be doing 120FPS while playing at 4K, so it's probably a non issue.
It's not really a Linux issue, but an HDMI forum issue.It sounds like it's a general Linux issue more than a Steam Machine issue. Hopefully Valve puts enough development effort into this to solve it for everybody running Linux.
And honestly, given what appears to be the relatively modest specs of the Steam Machine this doesn't seem likely to be a big issue. Pushing enough pixels to require HDMI 2.1 is probably beyond what the box can do on most games.
They could (assuming they could write the code or license it from AMD), but using the same driver everybody else uses is a lot easier and leads to fewer bugs. Given that HDMI 2.1 features are of marginal utility for a computer of such modest power and you can just use DisplayPort anyway, Valve probably figures this is the HDMI Forum's problem to fix.Given that the Steam Machine is made by themselves, can't they just use a close source driver for the HDMI 2.1 stuff?
AMD has developed full HDMI 2.1 capability, but have decided not to release it as a proprietary driver after the HDMI Forum rejected their request to release it as open source. I don't know their reasoning, or if Valve could change their minds. One issue is that AMD doesn't hold the copyright on the entirety of the open source Linux driver. Since they have upstreamed it into the Linux kernel, there have been contributions from people outside of AMD, and those developers retain the copyright for their contributions. So they would need to audit and rewrite any portions that they didn't hold the copyright on in order to release a modified proprietary driver. Or find some way to have proprietary binary blobs that the open source driver uses, in a manner that satisfies both the HDMI forum, the GPL, and their driver architecture.Given that the Steam Machine is made by themselves, can't they just use a close source driver for the HDMI 2.1 stuff?