Announcement

Collapse
No announcement yet.

AMD's Vulkan Driver Will Only Work With The AMDGPU Kernel Driver

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

  • AMD's Vulkan Driver Will Only Work With The AMDGPU Kernel Driver

    Phoronix: AMD's Vulkan Driver Will Only Work With The AMDGPU Kernel Driver

    I've just received confirmation from AMD that their forthcoming Vulkan driver will only work with the AMDGPU DRM kernel driver. This means that unless this AMDGPU kernel driver is extended to support pre-VI hardware, only the very latest AMD GPUs on Linux will work with Khronos' next-generation API...

    http://www.phoronix.com/scan.php?pag...an-Driver-Only

  • antar1nd
    replied
    As a SI card owner (R7250), I was inspired by Michael's post to explore the possibility of contributing to the amdgpu support. However, it seems even AMD's not clear about the path to take on that effect. While we are definitely going to rely on libdrm-amdgpu for vulcan, the call hasn't been made between whether libdrm-amdgpu should be extended to use radeon or adding SI support within amdgpu kernel driver.

    In my opinion the first makes more sense if it results in support for older hardware (pre GCN), while the second makes more sense if SI is the extent to what we want to extend this support to (talking about the long term of course). Whatever way we go has to be decided by AMD I guess, before the community support kicks in.

    Leave a comment:


  • smitty3268
    replied
    Originally posted by DoctorWho View Post
    CI includes M6100, which is Bonnaire, Sea Islands? There's Sea Islands and Southern Islands too. Can't keep track of all these geographical references.
    M6100 = Sea Islands = CI = GCN1.1

    Leave a comment:


  • DoctorWho
    replied
    Originally posted by bridgman View Post
    What smitty3268 said. We developed amdgpu on CI hardware and kept the code in, but unless/until we can enable it by default we need to mark it as experimental because the open source stack over amdgpu won't have the test coverage that radeon gets.

    From a hybrid driver perspective (mix of open and closed userspace on amdgpu kernel driver) the plan has always been to support CI and up, with various options being explored to cover SI as well. This works because the initial amdgpu-based Catalyst replacement drivers will be out of tree builds anyways, so having amdgpu not be default upstream for earlier GCN parts doesn't matter.
    Wrote a reply and it didn't post when I clicked "post reply". It always says "saved to drafts". Where are these drafts??
    Rewriting it again ugh.

    CI includes M6100, which is Bonnaire, Sea Islands? There's Sea Islands and Southern Islands too. Can't keep track of all these geographical references.
    Having the initial amdgpu be out of tree is less convenient but what's important to me is that it will still work with both open and closed source, is that the case even initially?

    Will the amdgpu eventually be in tree for M6100, which will make it more convenient for upgrading?

    Another totally unrelated question, way off topic which you don't have to answer, will the Polaris mobile workstation gpus be ready in time new HP and Dell refreshes by Sept/Oct this year? The gpu in this mobile workstation is upgradable to even the W7170M or other MXM-B gpu but not sure if I want to do that.

    Leave a comment:


  • DoctorWho
    replied
    Originally posted by bridgman View Post
    What smitty3268 said. We developed amdgpu on CI hardware and kept the code in, but unless/until we can enable it by default we need to mark it as experimental because the open source stack over amdgpu won't have the test coverage that radeon gets.

    From a hybrid driver perspective (mix of open and closed userspace on amdgpu kernel driver) the plan has always been to support CI and up, with various options being explored to cover SI as well. This works because the initial amdgpu-based Catalyst replacement drivers will be out of tree builds anyways, so having amdgpu not be default upstream for earlier GCN parts doesn't matter.
    CI includes M6100, i.e. Bonnaire or is it SI? There's Sea Islands and Southern Islands too. Can't keep track of all these geographical references.
    So you're saying the initial amdgpu out of tree drivers will work with both open and closed source userspace, is that correct? It's less convenient that they're not in tree but it's not that much of a problem. What's important is that they work with both thereby letting me use whatever I need regarding graphics systems such as X or Wayland.

    Will the code that covers the M6100 eventually be in tree thereby making upgrades much easier for me?

    Leave a comment:


  • bridgman
    replied
    "Replies below are on the next page. Click here to go to the next page".... and post #130 unapproved again.

    EDIT - now that's really interesting... this time I got a second "next page" message, one above and one below my unapproved post... and once again it was a bogus page break because the next post stayed on page 13 despite being equal length. Perhaps the server has been drinking Michael's good beer when he's not around.

    BTW I think we've always said that the hybrid stack would support CI and up. Things just got confused recently when Michael's article suggested that what we supported in the hybrid stack might be limited to what was enabled by default upstream today, which was never the case.
    Last edited by bridgman; 01-25-2016, 08:19 AM.

    Leave a comment:


  • bridgman
    replied
    What smitty3268 said. We developed amdgpu on CI hardware and kept the code in, but unless/until we can enable it by default we need to mark it as experimental because the open source stack over amdgpu won't have the test coverage that radeon gets.

    From a hybrid driver perspective (mix of open and closed userspace on amdgpu kernel driver) the plan has always been to support CI and up, with various options being explored to cover SI as well. This works because the initial amdgpu-based Catalyst replacement drivers will be out of tree builds anyways, so having amdgpu not be default upstream for earlier GCN parts doesn't matter.

    Leave a comment:


  • smitty3268
    replied
    Originally posted by DoctorWho View Post
    For my workstation I chose the M6100 gpu which is Bonnaire, Sea Islands, GCN 1.1 if I understand correctly.
    Yep, that's a GCN 1.1 CI card.

    When I read in articles and when you say that amdgpu is "experimental" and not enabled by default I interpret that to mean that AMD is just testing that code but will drop support for it and will only support GCN 1.2 and higher for amdgpu. Is that the case?
    Nope. There was no information one way or the other before, but bridgman confirmed here that's not the case.

    Are we who bought these workstations SOL?
    Nope.

    I had hoped in 2016 to eliminate dependence on X and switch to Wayland which I think can only be done with amdgpu.
    If you want to stick to the proprietary drivers, then yes you'll need amdgpu. If you want to use Mesa, then any GPU at all will work. Your card will be supported by amdgpu, so you're fine either way.

    Will I regret with sticking with AMD for my current and past systems?
    Well, I guess you're the only one who can answer that.

    Leave a comment:


  • DoctorWho
    replied
    Hoping http://www.phoronix.com/forums/member/8184-bridgman can clear this up

    So just to be clear let me tell you my situation.

    Some buyers of $3000 - $4000 mobile workstations like me are independent contractors. Sometimes we use enterprise linux distros and sometimes not. I use customized hardened kernels, stock kernels, distro kernels, and customized kernels with various options. It all depends on the job and whatever else I'm working on. So just because it's a mobile workstation doesn't automatically mean I will be using the enterprise drivers.

    For my workstation I chose the M6100 gpu which is Bonnaire, Sea Islands, GCN 1.1 if I understand correctly. These are workstations shipping today from vendors like HP and Dell not systems that are 1 or 2 years old. Yes I know the last refresh might have been early last year but the point is they are being sold today and people are buying them with either AMD gpus or Nvidia.

    When I read in articles and when you say that amdgpu is "experimental" and not enabled by default I interpret that to mean that AMD is just testing that code but will drop support for it and will only support GCN 1.2 and higher for amdgpu. Is that the case? Are we who bought these workstations SOL?
    Edit: What I'm saying is will the M6100 have official amdgpu support with closed source as well as open source?

    I had hoped in 2016 to eliminate dependence on X and switch to Wayland which I think can only be done with amdgpu.

    I might be buying a new workstation by the end of the year or early next year (hoping the Polaris mobile gpus will make it into those by then). Will I regret with sticking with AMD for my current and past systems? (meaning: based on how AMD handles this Vulkan issue I might decide to go with Nvidia rather than AMD. I hope to stick with AMD)
    Last edited by DoctorWho; 01-25-2016, 01:00 AM. Reason: Edit: for clarity

    Leave a comment:


  • bridgman
    replied
    Page break and moderated again. Woo hoo !!

    EDIT... OK, that's really wierd... when I saved the previous post I got a message saying "following posts were on next page" and my post was unapproved. Then when I refreshed the page I'm still on page 13. Maybe it's because this post is shorter than the previous one...

    Let's try
    making
    the post
    longer
    and see
    if we
    were close
    to a break

    Nope. Curiouser and curiouser.
    Last edited by bridgman; 01-24-2016, 07:10 PM.

    Leave a comment:

Working...
X