The HDMI Forum rejected AMD's open source HDMI 2.1 implementation
The HDMI Forum rejected AMD's open source HDMI 2.1 implementation
Why? Most software wasn’t propreitary before companies realised they could make more money at your expense, not all went into making a better product.
If given the choice of an uncomfortable dormitory or a comfortable jail, at least the residents can improve the living areas in the former.
VESA requires an annual membership fee to access the DP standard. Perhaps that’s fine but that makes regular people unable to “open” the door to the standard. VESA has in the past claimed implementing DP can mean you own them royalty fees but they apparently backed down from that.
Implementation of Content ““Protection”” isn’t in the spirit of an open standard to me, rather the opposite. Why have an open standard if not to weed-out corporate anti-features from existence for the benefit of the users?
Alright this sent me down a rabbit hole so I’m going to try to and summarize really quickly.
1^st^, VESA requires a membership but in reality you need a company that has a vested interest in what VESA does. So you have to pay a huge due to be apart of it. This is quite BS according to me, the fact that they can do this and still claim to be an open standard. Source
2^nd^, VESA never tried to implement a royalty based off the Display Port Standard. The company that did that was MPEG LA, LLC, they aren’t affiliated with VESA. Rather this company is a patent pool company that attempted to enforce their clients (such as Sony) licensing fees. They seemed to have backed off of this back in 2016 as the last patent used was for the Display Port Standard 1.4. Source
3^rd^ Content Protection was necessary if you want wide spread adoption. Companies aren’t going to want to do business with you if you allow for their IP to be ripped. As well, VESA is just a collection of companies that have voting shares in the company. So those corporate features are just par for the course.
Quick answers to common questions are found here. Can’t find what you are looking for? Submit your question via Ask DisplayPort to get an answer from one of our subject matter experts. General VESA FAQs Q: How do I order VESA Standards? How much are they? A: Some VESA Standards are offered electronically in PDF […]
indeed, parent’s conflation of C64 and *nix threw me off (as I guess it did others), but your comment helps to put it into perspective.
proprietary can drive FLOSS innovation, but its so hard to get around proprietary entrenchment - especially wrt consumer facing tech.
Linux never ran on the Commodore 64 (1984). That was way before Linux was released by Linus Torvalds (1991).
I’d also like to point out that we do all rely on non-proprietary protocols. Examples you used today: TCP and HTTP.
If we didn’t have free and open source protocols we’d all still be using Prodigy and AOL. “Smart” devices couldn’t talk to each other, and the world of software would be 100-10,000x more expensive and we’d probably have about 1/1,000,000th of what we have available today.
Every little thing we rely on every day from computers to the Internet to cars to planes only works because they’re not relying on exclusive, proprietary protocols.
It does since version 1.0 it seems?
Thank God, for a moment I thought I had auditory hallucinations.
Visual are ok though
I believe USB-C is the only connector supported for carrying DisplayPort signals other than DisplayPort itself.
The biggest issue with USB-C for display in my opinion is that cable specs vary so much. A cable with a type c end could carry anywhere from 60-10000MB/s and deliver anywhere from 5-240W. What’s worse is that most aren’t labeled, so even if you know what spec you need you’re going to have a hell of a time finding it in a pile of identical black cables.
Not that I dislike USB-C. It’s a great connector, but the branding of USB has always been a mess.
USB 3.2 2x2 with 20 Gbps is the same as USB 4 Gen 2×2 with 20 Gbps
USB 4 Gen3x2 has 40 Gbps and was then renamed to USB 4 1.0
USB-C with Thunderbolt currently had a limit of 40Gbit/sec. Wikipedia has a table of what DisplayPort can do at that bandwidth:
en.wikipedia.org/wiki/DisplayPort
See the section “Resolution and refresh frequency limits”. The table there shows it’d be able to do 4k/144hz/10bpp just fine, but can’t keep above 60hz for 8k.
Its an uncompressed video signal, and that takes a lot of bandwidth. Though there is a simple lossless compression mode.
What? I’m talking about people who would like to use the full capabilities of their HDMI TVs, when using Linux. I’m not sure what you’re on about.
My understanding is the adapters do not provide all the features of the HDMI 2.1 spec. Is that no longer the case?