AMDGPU blog #54
AMDGPU blog #54
Conversation
There was a problem hiding this comment.
Thanks for taking time to write this article, @jcfrosty!
I found some minor bits (Most the times I commented them once, but they explain to further occurences in this text).
I request changes mainly because I would like to see more level-two-headlines (##), in order to help the reader grasp the content easier. As an example read only the headlines and tell me, what the content is about.
Since the topic is quite technical, you should add link to a wiki (ours or Wikipedia) for technical terms like fgrlx, DC or similiar (my personal opinion).
If you add the headlines, I approve the PR. The other changes just ease reading IMHO.
| Currently, there are some gaps in support. Where PRO supports Freesync, HDMI 2.0, | ||
| HDMI Audio, OpenCL, etc., the AMDGPU driver will eventually attain all that | ||
| through what is known as Display Code (DC) or DAL/HAL (Display/Hardware abstraction | ||
| layer). The old DAL was just as it sounds, an abastraction layer. This |
There was a problem hiding this comment.
There are two spaces after the period of the sentence concerning DAL, HAL.
| a HAL was a simple method. They could write code that (mostly) worked for | ||
| both Windows and Linux at the same time. So primary focus on Windows translated | ||
| to some focus on Linux. Unfortunately, this doesn't mean it worked well. | ||
| We all remember how 'lovely' fglrx was a times with broken crossfire support, |
There was a problem hiding this comment.
Could you please use proper quotation marks? Like „, “ or ”?
|
|
||
| OK so small software dev team, HAL isn't fully working in this instance, | ||
| what is the solution? They decided to go open source. "Great, shouldn't this | ||
| be simple?" Short answer, No. They have to go over code with a fine tooth comb |
There was a problem hiding this comment.
Again, please use proper quotation marks: „, “ and ”.
| be simple?" Short answer, No. They have to go over code with a fine tooth comb | ||
| to make sure they aren't releasing code they "don't own" persay. Can't exactly | ||
| opensource DirectX related etc. After that, they also have to remove the HAL and recreate | ||
| code from scratch to make a native/direct communication line for the linux kernel. |
There was a problem hiding this comment.
Here you used a lowercase Linux. On purpose?
| bumped more frequently due to the constant development for AMDGPU. | ||
|
|
||
| We understand you may feel some frustration in this time awaiting fixes, | ||
| but let it be known this issue is affecting all Linux distributions. |
There was a problem hiding this comment.
Hm, I would need to think about how to interpret the phrase „let it be known” …
| and performance boosts, but maintaining stability. | ||
|
|
||
| We hope you're enjoying Sabayon just as much as we do! | ||
| -Frosty |
There was a problem hiding this comment.
That line will be placed after the one above. Are you fine with that?
|
Hi, @jcfrosty! Could you tell me, why you closed this PR? |
|
I didn't? Or at least I didn't mean to? I'm trying to correct the problems
you listed currently.
…On Mon, Jun 26, 2017, 12:01 PM André Jaenisch ***@***.***> wrote:
Hi, @jcfrosty <https://github.com/jcfrosty>!
Could you tell me, why you closed this PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#54 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ANERGQOis4KQjkes8M7CNZmv_c3Bac3Nks5sH-PqgaJpZM4OEGqZ>
.
|
| So when can we expect to see support for all items the display code brings us? | ||
| Thats an excellent, but daunting question. | ||
| AMD is about to meet the crossroads in which they either: | ||
| * Do not support their latest graphics cards at all ,VEGA and beyond, upon release |
| quickly. radv is the radeon opensource vulkan project. Have you tried DOTA2 | ||
| with vulkan lately? It works. [See the benchmarks and gaming results here.](https://www.phoronix.com/scan.php?page=article&item=amdgpu-new-1710&num=1) | ||
|
|
||
| Valve has also offered is services to help forward AMDGPU. [Looking forward to VR.](https://www.phoronix.com/scan.php?page=news_item&px=AMDGPU-PRO-VR-Linux) |
| quickly. radv is the radeon opensource vulkan project. Have you tried DOTA2 | ||
| with vulkan lately? It works. [See the benchmarks and gaming results here.](https://www.phoronix.com/scan.php?page=article&item=amdgpu-new-1710&num=1) | ||
|
|
||
| Valve has also offered is services to help forward AMDGPU. [Looking forward to VR.](https://www.phoronix.com/scan.php?page=news_item&px=AMDGPU-PRO-VR-Linux) |
| Thats an excellent, but daunting question. | ||
| AMD is about to meet the crossroads in which they either: | ||
| * Do not support their latest graphics cards at all ,VEGA and beyond, upon release | ||
| * Push their team to get the DC conversion completed and submitted to the linux kernel |
There was a problem hiding this comment.
It could be worth to "unwind" the acronym here.
There was a problem hiding this comment.
"Push their team to get the display code converted and submitted to the Linux kernel"
Better but now it reads like a generic display code (so why would it need converting?), not that DC stat stands next to HAL and DAL.
|
Sorry for the mess. as you can tell, I'm not completely familiar with github yet. I'm learning ;) |
|
General comment: I enjoyed the read but my feel is that the article is more technical (due to vocabulary and style being used), I could said nerdy, and can be harder by the less technical ones, or can leave readers with less knowledge of the video/GPU ecosystem some questions. By itself, this is not a bad thing, especially given that it's signed by your name (meaning the style /can/ be personal as I think of it), and in my option it could be left as is, but you might keep this in mind when writing futher articles on the website. (I'm not for dumbing down content; reading something like this actually allows someone to learn from it which is great, so take what I wrote with a grain of salt.) |
This one could be reopened instead, to keep everything in one place. Please do this like this in the future. |
|
Glad you liked it. Yeah, I figured the only people who would be interested in the AMDGPU blog would be people with an AMD card looking for answers (both techy and non). I don't plan on them all being techy, but there are those who are upset with AMD in general and I felt they deserved some sort of explanation. Even if it was a little over the top, they could still get something out of it. I'll keep in mind the ability to reopen next time. I was looking at the closed image at the top and looking to see if I could click it and get it to reopen, but it doesn't work that way. I just noticed the "reopen and comment" button on the bottom. I should have checked that before opening a new one. |
|
Changing "radeon" to something like "the radeon driver" should make it much easier for those non-AMD device owners in the following sentence. "Some of you may still be using radeon on |
|
Good point, also fixed. |
this is my first time attempting to add to the blog. Can someone please double check my work?