| Latest revision |
Your text |
| Line 1: |
Line 1: |
| − | ==Adding Ampere Altra processor==
| |
| − |
| |
| − | Hi David, may you add the Ampere Altra processor please ?
| |
| − |
| |
| − | ref: https://d1o0i0v5q5lp8h.cloudfront.net/ampere/live/assets/documents/Altra_Rev_A1_PB_v1.35_20220728.pdf
| |
| − |
| |
| | ==reintroducing sidebar menu== | | ==reintroducing sidebar menu== |
| | Hi I see you've been trying to fix the sidebar extension so that it works for 1.25. If you need any help I can provide assistance! --[[User:Jon|<font color="green" size="2px">Jonathan</font>]] ([[User talk:Jon|<font color="blue" size="2px">talk</font>]]) 12:31, 14 November 2015 (EST) | | Hi I see you've been trying to fix the sidebar extension so that it works for 1.25. If you need any help I can provide assistance! --[[User:Jon|<font color="green" size="2px">Jonathan</font>]] ([[User talk:Jon|<font color="blue" size="2px">talk</font>]]) 12:31, 14 November 2015 (EST) |
| Line 71: |
Line 65: |
| | I would also appreciate this! (sroelse) | | I would also appreciate this! (sroelse) |
| | | | |
| − | Any update on this? You have never responded.
| |
| | | | |
| | == High Resolution Pictures == | | == High Resolution Pictures == |
| Line 78: |
Line 71: |
| | | | |
| | : Hi there. Sorry, this isn't my photo (which is why the resolution is fairly low). It happens to be a photo provided by Intel/Mobileye itself so that's the resolution it came at originally (we don't downscale photos). --[[User:David|David]] ([[User talk:David|talk]]) 08:26, 21 September 2021 (EDT) | | : Hi there. Sorry, this isn't my photo (which is why the resolution is fairly low). It happens to be a photo provided by Intel/Mobileye itself so that's the resolution it came at originally (we don't downscale photos). --[[User:David|David]] ([[User talk:David|talk]]) 08:26, 21 September 2021 (EDT) |
| − |
| |
| − | :: Hi David, alright. That's unfortunate. Thanks for getting back! Sam [[Special:Contributions/217.229.171.177|217.229.171.177]] 05:21, 29 September 2021 (EDT)
| |
| − |
| |
| − | == Properties ==
| |
| − | Hi David, when I edit declarative properties on a Property: page the changes don't take effect. [[User:QuietRub|QuietRub]] ([[User talk:QuietRub|talk]]) 20:15, 9 November 2021 (EST)
| |
| − |
| |
| − | == 4LPE and 5LPE design rules ==
| |
| − | Hi David, I just fixed an apparent error in https://en.wikichip.org/wiki/5_nm_lithography_process but since I don't have original sources or first-hand data on 4LPE/5LPE design rules, and the tables don't cite any sources either, I would suggest you check the edit and add sources for 4LPE/5LPE design rules (and other processes, time permitting) used when making this page.
| |
| − |
| |
| − | Edit: https://en.wikichip.org/w/index.php?title=5_nm_lithography_process&type=revision&diff=100069&oldid=99958
| |
| − |
| |
| − | With kind regards,
| |
| − | AM.
| |
| − |
| |
| − | ==Spam==
| |
| − | Hi David, You're probably aware of this but there's a severe spam problem. I've been reverting it when I spot it, some are very subtle changes to articles that are just weird but it's getting worse. Please respond here with what you end up doing and so I can make an account before you close off IP access (if you use that tool) - if not just make sure you patrol and watch every page basically. Good luck
| |
| − | : [[Special:Contributions/90.219.59.92|90.219.59.92]] 23:58, 10 March 2023 (EST)
| |
| − |
| |
| − |
| |
| − | :: Much of the recent spam is very subtle changes and I have no idea how to deal with it unfortunately (other than blocking out large swaths of IP addresses/subnets). If you want to create an account, I can temporarily open it up so you can register. --[[User:David|David]] ([[User talk:David|talk]]) 11:50, 15 March 2023 (EDT)
| |
| − |
| |
| − | == Module:packaging data ==
| |
| − | Hi David. Module pages on Wikichip are not editable by mere mortals and as of 2023-03-13 [[Module:packaging data]] is missing entries for AMD socket AM5 and SP5, maybe you could add those? This also exposes a bug in [[Module:chip]] and [[Module:core]], which is getting in the way of editing pages referencing those sockets, where they attempt to access <code>package_info</code> fields without checking if this came up nil:
| |
| − |
| |
| − | <source lang="Lua">
| |
| − | local package_info = pdata['packages'][package_location[1]][package_location[2]]
| |
| − | </source>
| |
| − |
| |
| − | Alternatively I propose Module:chip and Module:core try to retrieve that data from the SMW database and also link to a package page <span class="plainlinks">[https://en.wikichip.org/wiki/Category:all_ic_packages if one exists]</span>, example below. You will notice the code accepts a page name like "amd/packages/socket am4" in addition to "vendor,name" which I think beats guessing names in the pdata table. In fact even "Socket AM4" would work in this case because that happens to be a redirect to that page.
| |
| − |
| |
| − | <source lang="Lua">
| |
| − | [...]
| |
| − | </source>
| |
| − |
| |
| − | Of course it would help if [[Module:package]], which already accepts the required data as parameters, would set corresponding package and socket properties, as below for instance. Note the example adds a missing 'package pitch 2' parameter and limits 'package dimension' to three values rather than ten. The proposed property names were already used in subobjects by templates like [[Template:packages/cavium/fcbga-1217]] invoked by the obsolete Module:chip 'package module' parameter. I would prefer a property 'package contacts' over 'package pins' though. Regrettably most of these properties are currently undefined and default to type Page <span class="plainlinks">([https://en.wikichip.org/w/index.php?title=Special%3AProperties&property=package 1] [https://en.wikichip.org/w/index.php?title=Special%3AProperties&property=socket 2])</span> so they won't display nicely. For another obstacle on Wikichip property page changes do not seem to enter the SMW database voluntarily. Take for instance [[Property:l1$ size]] which requests to be displayed in KiB but shows MiB, or [[Property:integrated gpu execution units]] which is typed as Number but still defaults to Page. Also package properties may not enter the database immediately even if listed in a package page fact box, a [[Special:Ask/-5B-5BCategory-3Aall-20ic-20packages-5D-5D/-5B-5Bamd-2Fpackages-2Fsocket_sp5-5D-5D/-3Fpackage/-3Fpackage-20type/-3Fpackage-20pins/-3Fpackage-20pitch/-3Fpackage-20length/-3Fpackage-20width/-3Fpackage-20height/-3Fsocket|manual query]] will show the problem.
| |
| − |
| |
| − | <source lang="Lua">
| |
| − | [...]
| |
| − | </source>
| |
| − |
| |
| − | Kind regards, [[User:QuietRub|QR]] ([[User talk:QuietRub|talk]]) 03:47, 13 March 2023 (EDT)
| |
| − |
| |
| − | : Thanks for the admin rights. I made the proposed changes, seems to work as planned. May I suggest an infobox class for Module:chip, core, microarchitecture, and package? They duplicate a lot of code, it could be more readable, and shared code would promote a common appearance. For instance core and package use in-text annotations to set properties, so e.g. [[amd/cores/milan]] displays a warning about the "7 nm+" process using an unknown unit. SMW also displays conversion pop-ups for quantity properties, perhaps useful to compare metric and customary units like inches or mils. Module:chip and microarchitecture use #set exclusively, so [[apple/ax/a12x]] has no pop-ups and is quiet about several improper values and why 'base frequency' is not set. Well an infobox class taking care of such details could do either and switch easily. [[User:QuietRub|QR]] ([[User talk:QuietRub|talk]]) 02:36, 2 April 2023 (EDT)
| |
| − |
| |
| − | == Semantic citations ==
| |
| − | What is your opinion on semantic citations? Citations are useful to track obscure facts or record documents which may be of interest to other researchers, but one has to look up document details (title, author, publication date, URL, etc.) every time, corrections on multiple pages e.g. when the URL changes are laborious, and long references clutter up the page. Semantic citations would keep all the details in semantic properties on one page and use a query to insert them on other pages.
| |
| − |
| |
| − | There is a promising [https://www.mediawiki.org/wiki/Extension:Semantic_Cite Semantic Cite extension], however it comes with downsides such as not being installed on Wikichip, using admin-only pages to control its operation, enforcing conventions like having a single list of references at the bottom of the page (unlike e.g. {{amd|CPUID}}), and not cooperating with the Cite extension so if documents outside the SMW database are referenced one may end up with two reference tables. Fortunately something similar can be implemented using basic SMW features and templates:
| |
| − |
| |
| − | Each citable document has a page which sets properties containing the document details. That could be a File: page although for copyright reasons I would expect more often an ordinary, very short page with an external link to the document. Another option, not mutually exclusive, is to store details in one subobject per document. Subobjects can be placed on pages listing documents in any number, and a template can help structure the data. Subobjects have no name or category but a query can find "citation resource" subobjects because they all set a citation_key property. The key is one way to retrieve document data, and a suitable template can format it. A less taxing option is to format the citation at the source, a side effect of the subobject template, and store the output in a citation_text property. A Template:cite would simply insert the retrieved citation_text in a page, e.g. in the bibliography section. A Template:citeref can create a reference by adding <ref> tags. Document tables could be produced in the same way as chip tables, with free text search in titles or keywords, the subobject template setting additional properties as needed. [[User:QuietRub|QR]] ([[User talk:QuietRub|talk]]) 02:36, 2 April 2023 (EDT)
| |
