Announcement

Collapse
No announcement yet.

AMDVLK 2021.Q4.1 Released As First Code Drop In Over A Month

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

  • #11
    Originally posted by smitty3268 View Post

    Bridgman's silence on the whole ray-tracing debacle speaks volumes, IMO. Usually he'd be telling us to just be patient and that it's coming as soon as they are able to scrape enough people together to implement it. This time, nothing.

    There is obviously no current plan to bring ray-tracing to amdvlk. Maybe not ever. At the very least, probably not until the rocm team decides they need it.

    The only question is if this is some kind of legal IP issue, a business decision to try and hide their RT code for trade-secret reasons, or if they just don't care about linux consumer support enough to spend the time making LLVM work properly with it. Or maybe all of the above.



    Oh, and the delay in code drops is almost certainly just down to the 1 person who's responsible for doing so going on vacation. I doubt they have anyone as a backup because it's not important enough to worry about.
    Honestly, I feel as though AMD is aware that everyone uses RADV and therefore puts little-to-no effort into AMDVLK, I mean why spend resources on a driver no one uses? Similar to the proprietary OpenGL driver, they keep it runnable but that's about it.

    Comment


    • #12
      Originally posted by smitty3268 View Post
      Bridgman's silence on the whole ray-tracing debacle speaks volumes, IMO. Usually he'd be telling us to just be patient and that it's coming as soon as they are able to scrape enough people together to implement it. This time, nothing.
      Geez, if I had known I was able to speak volumes by shutting up I would have done that years ago and made a lot of people happy

      As you know we only stabilized RT support in the closed source Linux driver recently, and there was some debate about how much of that to expose in the AMDVLK version, ie what parts if any needed to be rewritten before release.

      Not sure what the current situation is but will see if there is something I can say about it.
      Last edited by bridgman; 05 November 2021, 11:50 PM.
      Test signature

      Comment


      • #13
        Originally posted by bridgman View Post
        As you know we only stabilized RT support in the closed source Linux driver recently
        6 months ago. And it was itself 6 months late.

        Not sure what the current situation is but will see if there is something I can say about it.
        Appreciated.

        By the way, I don't intend this to come off as overly rude, but honestly even if amdvlk raytracing support comes out tomorrow it's still a giant debacle for AMD in my mind. But better late than never, obviously.
        Last edited by smitty3268; 06 November 2021, 01:06 AM.

        Comment


        • #14
          Originally posted by JoshuaAshton View Post
          As is to be expected -- this is more of a source available driver than open source, as it isn't developed in the open at all.

          The code drops really suck and it's clear they don't want or care about external contributions or issues. Large code drops make bisecting impossible.
          isn't still good just to see how amd does (did) something and since it is open source, couldn't mesa project incorporate things from it they like? or at least use it to build something off of?

          Comment


          • #15
            Originally posted by middy View Post
            isn't still good just to see how amd does (did) something and since it is open source, couldn't mesa project incorporate things from it they like? or at least use it to build something off of?
            It's mostly useful as hardware documentation. Particularly in cases where there are hardware bugs that need to be worked around that may not be obvious.

            Comment

            Working...
            X