• davelA
    link
    fedilink
    English
    arrow-up
    10
    ·
    9 months ago

    As another tid-bit, in the early days of the open-source AMD driver effort there were concerns around exposing GPU video acceleration in the open-source driver as to not potentially compromise HDCP / digital video restrictions with MPEG-LA and the like.

    How much of this fuckery boils down to the corporate media imposing DRM—all of it, or only most of it?

    • The Doctor@beehaw.org
      link
      fedilink
      English
      arrow-up
      5
      ·
      9 months ago

      Most of it. There are still a small handful of “open source is worthless, forget about it” holdouts in this particular problem space.

  • notaviking@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    9 months ago

    This reminds me of like how Deadpool’s test scene “accidentally” leaked to push through the Deadpool movie after it was rejected by the studio. Ended up benefiting everyone and opened the door to R-rated superhero movies

  • AutoTL;DR@lemmings.worldB
    link
    fedilink
    English
    arrow-up
    5
    ·
    9 months ago

    This is the best summary I could come up with:


    For three years there has been a bug report around 4K@120Hz being unavailable via HDMI 2.1 on the AMD Linux driver.

    As covered back in 2021, the HDMI Forum closing public specification access is hurting open-source support.

    AMD Linux engineers have spent months working with their legal team and evaluating all HDMI features to determine if/how they can be exposed in their open-source driver.

    AMD had code working internally and then the past few months were waiting on approval from the HDMI Forum…

    Sadly, the HDMI Forum has turned down AMD’s request for open-source driver support.

    AMD Linux engineer Alex Deucher commented on the ticket: "The HDMI Forum has rejected our proposal unfortunately.


    The original article contains 297 words, the summary contains 113 words. Saved 62%. I’m a bot and I’m open source!