• TWeaK@lemm.ee
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    10
    ·
    1 year ago

    Maybe they should hurry up and fix Zenbleed first.

    • Alto@kbin.social
      link
      fedilink
      arrow-up
      32
      arrow-down
      1
      ·
      edit-2
      1 year ago

      You’re aware the team working on that is almost certainly not the same team working on this, correct?

      • TWeaK@lemm.ee
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        1 year ago

        Yup, just having a moan, and also bringing it up because it feels like it should be more widely known about (along with Intel’s similar issue).

        • Vilian@lemmy.ca
          link
          fedilink
          English
          arrow-up
          9
          ·
          1 year ago

          it’s already fixed, and merged in the linux kernel, they can’t do more than that

    • phx@lemmy.ca
      link
      fedilink
      English
      arrow-up
      10
      ·
      1 year ago

      Fixes have been added at a kernel level for many OS’s, but microcode is still forthcoming for many models. It sounds like they’ve got it out for the EPYC 7002 (server) chips first - which makes sense as they’re likely running VMs which may be internet exposed - and most of the rest are expected between Oct - Dec

    • TheRealKuni@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 year ago

      I have a feeling the team finalizing the launch of new Radeon cards have nothing to do with the team fixing Zenbleed.