The HDMI Forum rejected AMD's open source HDMI 2.1 implementation
The HDMI Forum rejected AMD's open source HDMI 2.1 implementation
If you were hoping at some point to see HDMI 2.1+ on Linux with AMD + Mesa, you're out of luck right now as it's simply not going to be happening.
You're viewing a single thread.
If we had to relay exclusively on non-proprietary protocols, I doubt that GNU/Linux would have gone anywhere beyond the Commodore 64
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. Weird shit like HDMI is the exception, not the rule.
History demonstrates that proprietary protocols and connectors like HDMI only stick around as long as they're convenient, easy, and cheap. As soon as they lose one of those properties a competitor will spring up and eventually it will replace the proprietary nonsense. It's only a matter of time. This news about HDMI being rejected is just another shove, moving the world away from that protocol.
There actually is a way for proprietary bullshit to persist even when it's the worst: When it's mandated by government.
AV1 is a good example of a non-proprietary protocol replacing proprietary protocols (h.264, h.265, ...)
DRM is mandatory in any spec you expect content owners to support. We don’t have to like it, but it’s absolutely not going away.
There are couple of ways, not buying the content for example. DRM is for paying customers.
That’s 99% of the reason we use HDMI…
Who is we?
Well said, content owners, not creators.
Why? Most software wasn't proprietary before companies realized they could make more money at your expense (not all the profit is going 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.
Parent is right though. Unix being proprietary is why the GNU project was started, and why the Linux kernel and BSDs rose above.
Hopefully HDMI being proprietary leads to others creating an alternative, open standard which eventually can push HDMI to open up or push it out.
Isn't that what DisplayPort is? At least that is what Dell is claiming.
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 pastclaimed implementing DP can mean you own them royalty feesbut 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.
1st, 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
2nd, 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
3rd 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.
Corporate Protection in MY hardware is a hill I'd die on, wide spread adoption be damned if not possible without it.
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.