Announcement

Collapse
No announcement yet.

AMD Posts Open-Source Driver Patches For Vega 12

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

  • bridgman
    replied
    Originally posted by Michael View Post
    By chance did that get delayed?
    Yes - Marek had to pull in an updated addrlib in order to pick up a last-minute fix.

    Leave a comment:


  • Michael
    replied
    Originally posted by agd5f View Post
    Mesa patches will be out momentarily.
    By chance did that get delayed?

    Leave a comment:


  • bridgman
    replied
    This is not for the Kaby Lake GPU.

    Leave a comment:


  • chithanh
    replied
    Originally posted by valici View Post
    Eureka! What is the next AMD chip to be launched? It was already demoed BUT not by AMD and will need Linux support?
    And COINCIDENTALLY has exactly 5 SKUs? And the realease date is supposed to be late March?
    Intel said that they, not AMD, will be providing Kaby Lake G drivers to end users:
    Originally posted by PCWorld
    One interesting wrinkle: Intel will be responsible for supplying the drivers for the Radeon GPU, though company engineers won’t write the original code. An Intel representative said they’re working closely with AMD’s Radeon business to supply “day one” drivers for new games, when those drivers become available.
    https://www.pcworld.com/article/3235...-graphics.html

    Leave a comment:


  • wizard69
    replied
    Originally posted by Nille_kungen View Post

    I think the Vega has had the best naming ever.
    Vega tells the architecture and the number is the number of the compute units so one can estimate how powerful the chip is.
    Did you read the comments above. This thread is about an archtecture not a product.
    Like Vega 12 puts it between RX550 and RX560 so i guess i will see this in an laptop, integrated to a motherboard or in an APU.
    Again architecture! From the naterial in this thread you can't derive the statements you made above. Being a newish archetecture it could show up anywhere with any number of compute units. Now you might make assumptions based on data from outside this thread but that isnt what many are doing here.

    Leave a comment:


  • wizard69
    replied
    Originally posted by Drago View Post
    What a Vega MESS. Couldn't AMD come up with something less confusing, kinda Ryzen-Zen.
    it really isnt that difficult for anybody that has graduated high school maybe even grade school.
    In any case 60 000 lines of code for just one variant for just one chip. I wonder when Linux developers will say enough is enough. I guess in the future there will be different git repos for each kernel sub tree, and make install will download selectively depending on the kernel compile configuration.
    Agan read the article, it isnt that difficult to understand. The majority of the code is boiłerplate to define registers and stuff. Such info in no way burdens the kernel source code trees.

    Leave a comment:


  • bridgman
    replied
    Originally posted by hoohoo View Post
    Any news on ROCm support for RavenRidge?
    Making pretty good progress testing & bug fixing, not sure about release plans yet though.

    Leave a comment:


  • valici
    replied
    Eureka! What is the next AMD chip to be launched? It was already demoed BUT not by AMD and will need Linux support?
    And COINCIDENTALLY has exactly 5 SKUs? And the realease date is supposed to be late March?

    Yes, Vega chip inside the Intel Kaby Lake G. It will probably also be release separately by AMD as Vega Mobile but later.
    My bet the AMD chip inside Kaby Lake G is Vega 12 and it will have 24 CU.





    Leave a comment:


  • r1348
    replied
    Originally posted by FirstPersonBSOD View Post

    It's probably for the successor to Polaris 10/RX580.
    This is what I hope, been meaning to get one since a year now, but I won't submit to the cryptocurrency bubble and pay 400€ for one.

    Leave a comment:


  • bridgman
    replied
    Originally posted by rubdos View Post
    I wonder though; can't those generated headers be generated at kernel make/compile time? Seems kinda stupid to put generated code in the tree, esp. when it's that large.
    The headers are generated from our internal HW design database - a normal build system is not going to have access to that information.

    Leave a comment:

Working...
X