62
edits
 |
Progress Continues
We've already had 21536 updates since Dolphin 5.0. Keep up with Dolphin's continuing progress through the Dolphin Blog: February, March, and April 2024 Dolphin Progress Report. |
 |
The Dolphin Emulator Wiki needs your help! Dolphin can play thousands of games, and changes are happening all the time. Help us keep up! Join in and help us make this the best resource for Dolphin. |
User talk:Incassum: Difference between revisions
→AMD CPU Naming: added a bit to the discussion.
(→AMD CPU Naming: added a bit to the discussion.) |
|||
| Line 6: | Line 6: | ||
With this in mind, it seems that the only option left to us if sticking with giving official/manufacturer-given names is to skip the "BE" altogether and either use "9xx" or "9xx Black Edition", as those are the only officially valid/correct names. If, however, we are prepared to let go of being manufacturer-loyal in our writing/naming-conventions, it's up to us to choose whether we'd like to use "BE" with or without a space, in which case I suggest without a space as that seems to be the consistently most used across the web, especially amongst hardware-geeks. One notable exception to this is Anandtech, which uses a space. [[User:Incassum|incassum]] ([[User talk:Incassum|talk]]) 22:32, 13 January 2014 (CET) | With this in mind, it seems that the only option left to us if sticking with giving official/manufacturer-given names is to skip the "BE" altogether and either use "9xx" or "9xx Black Edition", as those are the only officially valid/correct names. If, however, we are prepared to let go of being manufacturer-loyal in our writing/naming-conventions, it's up to us to choose whether we'd like to use "BE" with or without a space, in which case I suggest without a space as that seems to be the consistently most used across the web, especially amongst hardware-geeks. One notable exception to this is Anandtech, which uses a space. [[User:Incassum|incassum]] ([[User talk:Incassum|talk]]) 22:32, 13 January 2014 (CET) | ||
Thanks for the further investigation Incassum. You did confirm something I suspected, but hadn't looked into in that typically BE CPUs don't exist as non-BE, so it isn't a distinguishing factor. We had brought in the central manufacturer naming rule to help avoid the plethora of names that can arise for chipsets between general shortenings and sub-manufacture's naming. I believe you are right that AMD seems to never use the "BE" acronym, but you can see them vacillate between "Black Edition" and "Black", likely where they need to trim things up a bit. Given that the inconsistency there bothers me a bit, I may lean toward just purging the various BE texts generally, since it doesn't provide a distinguishing characteristic of things. We can already see higher overclocks those chips might allow in the "@ XXXGHz" postfixes. My main goal here is for there to be some consistency in the testing results to make them more generally applicable (and hopefully parsable for future metrics/compatibility list enhancements). [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 22:56, 13 January 2014 (CET) | Thanks for the further investigation Incassum. You did confirm something I suspected, but hadn't looked into in that typically BE CPUs don't exist as non-BE, so it isn't a distinguishing factor. We had brought in the central manufacturer naming rule to help avoid the plethora of names that can arise for chipsets between general shortenings and sub-manufacture's naming. I believe you are right that AMD seems to never use the "BE" acronym, but you can see them vacillate between "Black Edition" and "Black", likely where they need to trim things up a bit. Given that the inconsistency there bothers me a bit, I may lean toward just purging the various BE texts generally, since it doesn't provide a distinguishing characteristic of things. We can already see higher overclocks those chips might allow in the "@ XXXGHz" postfixes. My main goal here is for there to be some consistency in the testing results to make them more generally applicable (and hopefully parsable for future metrics/compatibility list enhancements). [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 22:56, 13 January 2014 (CET)<br/> | ||
<br/> | |||
No need to thank me, we are all working for free here.<br/> | |||
Hmm, I can see the point of that in GPU naming conventions, however, as far as CPUs go, there isn't really a problem of people using radically different names for them, is there? And we don't even request name-dropping the chipset (which in the case of AM3/AM3+ CPUs would be 7xxFx, 8xxFx and 9xxFx)in the case of CPUs, so I don't think that there is a problem there, short of what we are discussing now (i.e. the "BE"-issue). Futher, nowhere have I found a place where AMD themselves refer to any CPU as only "Black", as far as I've been able to find they consistently use "Black Edition", so if you found them using only "Black" from a reliable source, then it is a practice which seems to be deprecated/changed and retroactively removed, so at least we don't have to worry about that. | |||
In the interest of sticking with something that is already prevalent, I, as stated above, would prefer to not use a space; further, for the sake of future parsing and the like, any and all *nix-users should know that using spaces where they are not absolutely needed is evil, haha. [[User:Incassum|incassum]] ([[User talk:Incassum|talk]]) 17:39, 14 January 2014 (CET) | |||