Announcement

Collapse
No announcement yet.

AMD Has Been Working On An Open-Source GPU Debug Tool, To Be Released Soon

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • chithanh
    replied
    Originally posted by bridgman View Post
    It was a personal project that turned out to be sufficiently useful to make public; we are using it with unreleased (and hence non-public) GPUs.
    I see. So without major changes in AMD's culture that such things happen in the open by default, this is not going to improve?

    Leave a comment:


  • geearf
    replied
    bridgman
    A bit unrelated, but is there a guess as to which kernel will land hdmi audio for SI on amdgpu?

    Thanks!

    Leave a comment:


  • bridgman
    replied
    Don't worry about open source driver support for Vega at release time (that is a given)... the only thing worth worrying about is upstream open source driver support at release time.

    We still want "upstream at release" if at all possible though, and that's what we are working towards.

    Leave a comment:


  • Nille_kungen
    replied
    Originally posted by Evil Penguin View Post
    Vega can't come soon enough.
    I worry about open source driver support for vega at release time but maybe they have it internally but i still think it will need DC (DAL).

    Leave a comment:


  • nomadewolf
    replied
    The good news keep pilling up.

    Leave a comment:


  • Evil Penguin
    replied
    Vega can't come soon enough.

    Leave a comment:


  • bridgman
    replied
    It was a personal project that turned out to be sufficiently useful to make public; we are using it with unreleased (and hence non-public) GPUs.
    Last edited by bridgman; 12 January 2017, 02:00 PM.

    Leave a comment:


  • chithanh
    replied
    Ah, the dreaded AMD approval process.
    Seriously though, why can't AMD develop such a thing in the open from the beginning?

    Leave a comment:


  • bridgman
    replied
    Originally posted by chithanh View Post
    What happened to "release early, release often"? Instead of three parties working independently on their debugging tools and duplicating work, they could have spent the months they worked in secret on them better by collaborating.
    You kinda have to write it before you can release it... and it's hard to get release approval in December because a lot of key people are off on vacation.

    Both tools are at very early stages anyways, although umr probably has an extra month of spare-time effort on it (Tom started writing it as a background project for his own use but it turned into something we thought was worth making public).

    We had talked to "the usual suspects" about it unofficially but I think we missed Andres because he moved to Valve around the time we started work on the tool. Until yesterday I thought he knew about it from internal emails.
    Last edited by bridgman; 12 January 2017, 12:14 PM.

    Leave a comment:


  • duby229
    replied
    Originally posted by chithanh View Post
    What happened to "release early, release often"? Instead of three parties working independently on their debugging tools and duplicating work, they could have spent the months they worked in secret on them better by collaborating.
    Straight up words of wisdom here. Fo Sho.

    Leave a comment:

Working...
X