User talk:Rubones

Rubones, the PS5 section is wrong. There is no standard clock vs boost clock. It's variable. Please site your sources if you are going to put that.

I agree with the guy above. Don't try to destroy Wikipedia!!! Cite your sources if there are any. <>


 * WARNING**** Any further attempt to interrupt the editing of the article at List of AMD graphics processing units will result in a permanent ban of your user account and blockage of all of the corresponding IP and MAC addresses. — Preceding unsigned comment added by Kasra Kimmich (talk • contribs) 13:14, 20 November 2020 (UTC)

November 2020
Your recent editing history at List of AMD graphics processing units shows that you are currently engaged in an edit war; that means that you are repeatedly changing content back to how you think it should be, when you have seen that other editors disagree. To resolve the content dispute, please do not revert or change the edits of others when you are reverted. Instead of reverting, please use the talk page to work toward making a version that represents consensus among editors. The best practice at this stage is to discuss, not edit-war. See the bold, revert, discuss cycle for how this is done. If discussions reach an impasse, you can then post a request for help at a relevant noticeboard or seek dispute resolution. In some cases, you may wish to request temporary page protection.

Being involved in an edit war can result in you being blocked from editing&mdash;especially if you violate the three-revert rule, which states that an editor must not perform more than three reverts on a single page within a 24-hour period. Undoing another editor's work—whether in whole or in part, whether involving the same or different material each time—counts as a revert. Also keep in mind that while violating the three-revert rule often leads to a block, you can still be blocked for edit warring&mdash;even if you do not violate the three-revert rule&mdash;should your behavior indicate that you intend to continue reverting repeatedly. Vossanova o&lt; 22:22, 19 November 2020 (UTC)

Notice of edit warring noticeboard discussion
Hello. This message is being sent to inform you that there is currently a discussion involving you at Administrators' noticeboard/Edit warring regarding a possible violation of Wikipedia's policy on edit warring. The thread is Administrators' noticeboard/Edit warring. Thank you. Vossanova o&lt; 22:39, 19 November 2020 (UTC)

Nomination of Consoles Hardware for deletion
A discussion is taking place as to whether the article Consoles Hardware is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or whether it should be deleted.

The article will be discussed at Articles for deletion/Consoles Hardware until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.

Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article. ZXCVBNM (TALK) 10:02, 6 December 2020 (UTC)

Reverting of the changes to List of AMD graphics processing units
Could you provide the reason for the reversal of the changes to List of AMD graphics processing units regarding the architecture of the Xenos and the formatting of the list of notes? TeraScale — that started with R600 — is a much newer architecture than the Xenos, featuring Direct3D 10 support (as opposed to 9.0c with R400-specific additions), including things such as integer shader ALU, 8x MSAA, and VLIW instruction co-issuing is done for 5 separate scalar instructions, rather than 1 vec4 instruction and 1 scalar instruction. The reference I provided, the R400 project folder history (individual documents require logging in on that website, but the "Download All" button works without login), contains various Xenos references, including a Perforce changelist about creating a Xenos branch from the R400 one, as well as various integrations between the R400 and the Xenos branches. In addition, the shader instruction set in the official R400 ALU emulator and the control flow documentation from that reference link exactly matches the instruction set used in the Xenia Xbox 360 emulator (which I am the core graphics developer of), as well as the Freedreno driver for the Qualcomm Adreno 200, also known as AMD Z430, being based on the Xenos and also being one of the most prominent references for the information used in the Xenia emulator. The R600 instruction set architecture, on the other hand, as I said earlier, has a different parallelism model, and overall many new instructions compared to the Xenos (such as the integer ones). The R400 specification also contains the pixel shader "param gen" register layout, which matches the layout used in Xenia, as well as the GL_AMD_program_binary_z400 shader disassembly when gl_FragCoord or gl_FrontFacing is used on an Adreno 200 Android device. Other matching parts between the official R400 documentation and Xenia/Freedreno are export indices, the layout of the setup of the passthrough shader exports ("memexport") — again, these are very different on TeraScale. Also, you have reverted a few formatting changes, such as commas not aligned with superscript numbers, an unused superscript entry (3 has the description, but is not used anywhere), and the name of the Wii U console. If you wanted to make some additional changes in the latest revision, but have picked an outdated version as the base, could you merge your new additions with my changes please? — Triang3l (talk) 12:12, 12 December 2021 (UTC)
 * TechPowerUp is an untrustworthy source that receives information pretty much from the same places as you do, just like all those clickbait websites that state that my Xbox 360 emulator can also run Xbox One and PlayStation 3 games. Should I send you a picture where I draw arrows between the Xbox 360 GPU emulation code and the same things in the R400 specification documents? I work with this thing every day, the registers and the shader code there have almost nothing to do with the R520 or R5xx at all. — Triang3l (talk) 09:37, 31 May 2022 (UTC)