Comment # 71
on bug 76490
from Maxim Sheviakov
(In reply to Tobias Droste from comment #70) > (In reply to Benjamin Bellec from comment #68) > > If I have to read the VBIOS and add I quirk in the kernel, why the kernel > > can't do this by himself ? > > > > Moreover, I saw the previous quirk in the kernel, the max memory clock is > > often set to "120000". I guess it stands for 1.2GHz QDR which is equivalent > > to 4.8GHz. My card, like all the R7 370 are supposed to work at 5.6GHz so > > this is a serious lost of performance. > > > > At the moment I will just return my card. > > For the record: > > This stuff *can't* be read from the VBIOS and has to be found by trial and > error. > You also don't have to google the steps, they are described in comment #48. > > But otherwise you are right, It will limit your card and replacing it with > another one seems like the only option you have right now. At least that's > what I did too, because I don't see this bug fixed in the near future. Hmm, nice point. By the way, is the MCLK kinda divided by four? So, if Memory Clock is 5600MHz, I'll have to do 5600/4*10000 to get the correct value? It's like, 120000 value = 1.2GHz*4 = Original frequency = 4800MHz, right? If that's it, I'll fix my quirk (AGAIN, LOL) and try using 970MHz and 5600MHz written as needed, 'cause my GPU is MSI R7 370 Armor 2X, and looks like values in quirk are *kinda* low for it.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
