From WikiChip
WikiChip's General Discussion

An archive box archives 


Welcome to Wikichip's General Discussion!

Trying to find your way? check WikiChip:welcome.

Click here to start a new topic.


  • Don't be a jerk
  • Don't bite the newcomers
  • Off-topic discussions are allowed but should be keep at minimum
  • If a topic has its own article, comments should be posted on its talk page



any has access to this book or other similar books?; 1978, English, Book, Illustrated edition: Microprocessor data manual : from Electronic design / edited by Dave Bursky. --ChipIt (talk) 12:36, 3 January 2016 (EST)

"model name" redirecting[edit]

Hey guys, in an attempt to give some wiggle room for API queries, I want to setup a redirection policy. This includes redirecting common names, partial common names, model number (so long there are no ambiguities). I want to prioritize the redirection of cpuid because that's something we're particularly interested in for API purposes.

The following redirects should be done for all pages:

  1. Full common name
  2. Full common name, all lowercase
  3. Common name, just family/model, if applicable
  4. Common name, just family/model all alowercase, if applicable
  5. Model number
  6. Model number all lowercase
  7. /proc/cpuid name

E.g. Intel Core i7-4770R:

--David (talk) 15:44, 8 January 2016 (EST)

I went ahead and created WikiChip:model numbers based on folding@home dump table. Should give us a nice starting coverage. --ChipIt (talk) 18:02, 8 January 2016 (EST)

What about sSPEC numbers? Shouldn't they be a redirect as well? - 15:01, 7 January 2017 (EST)

Yea, sSpec should redirect as well. at the moment you can actually search for by sspec parts direct here s-spec. In fact, sSpec, qSpec (we have qualification sample info too), and part numbers redirect too. We have a bot that should be doing that automatically as we add that info. Right now I think User:David is getting ready to switch over the default Skin to our new skin as well. So he's a bit busy with all that stuff. --ChipIt (talk) 16:22, 7 January 2017 (EST)

articles for years/decades[edit]

I've been thinking and I think we should start creating articles for individual years with all the notable things that happened. It would make collecting that stuff easier if we start early with it. Any thoughts? --ChipIt (talk) 04:45, 28 April 2016 (EDT)

Sounds good I'll start filling stuff in as I go along. --At32Hz (talk) 06:26, 30 April 2016 (EDT)

mass DB of CPU chip info[edit]

I collected a mass amount of CPU info to create a similar site to yours. The website never worked out, but i still have the data. the data is public domain, so feel free to use it. It is stored in comma-seperated-values files, so its is easy to import to what ever. Any you can probably set up a script to import it to you mediawiki website.

I also tried to make a mediawiki version, and may be able to run that again for show you. I hope this is useful. contact me if you want any help importing it, or anything else. ZyMOS (talk) 16:00, 21 May 2016 (EDT)

THis is apparently the script i used to import the CSV files to MediaWiki. Also i dont recall the details of it. Contact me if yoiu have questions and i can try to remember what i did ZyMOS (talk) 16:05, 21 May 2016 (EDT)
Hey ZyMOS, these CSV files are pretty nifty. I'll see if I can import them into our {{mpu}}/{{mcu}} templates when I get a bit of free time. --At32Hz (talk) 16:37, 22 May 2016 (EDT)

CPU images / Chip manufacture logos / chip package outlines[edit]

I probably have 400 cpu/mpu/SoC photos, of mostly good quality. A ton of chip package outlines of medium quality, and IC manufacture logos of low quality. If you want i can upload them, but id want to script it, and need to have permission to use a bot. Check them out below.

ZyMOS (talk) 14:58, 27 May 2016 (EDT)

Hey ZyMOS and welcome! If you want, you can go for it. I've added you to the 'Bot' group so you should be able to automate it (we have the generic {{Information}} template). We might want to make a template that has some related info: Model, Family, Datecode, etc.. Preferably with semantic properties embedded similar to how we have in the MPU template as that will allow the images to be queried/searched/dynamically shown on a pages (if you have that info associated with the images, otherwise we could add that later no biggie). --David (talk) 19:05, 27 May 2016 (EDT)
I will probably have to script it with simple info, Manufacturer and part number. It will take me a while to get the script working, its very old. ZyMOS (talk) 21:10, 27 May 2016 (EDT)

Datasheets upload[edit]

One more thing i can contribute. a bunch or CPU/MPU datasheets. I can script upload them too, but it wont be a very intelligent script, so details will have to be inputed manually. BTW im impressed at some of the databooks you found, i know how difficult old ones are hard to find. ZyMOS (talk) 10:08, 28 May 2016 (EDT)

Datasheets are a bitch to find! I actually have a whole treasure trove worth of data books from the 60s-80s. I scanned a bunch of databooks (some I sent to bitsavers) and a ton of datasheet years ago. Interestingly enough, a lot of the datasheets I scanned and uploaded online somehow found their way to those online datasheet websites (they even slapped their own watermark on it as if they actually own it or something!). I have a lot more manuals and stuff for some of the more rarer 4 bit to 16 bit chips out there. Lots of stuff from ebay and craigslist! My main issue is scanning them. Atm I don't have the means to scan and I can't drop $1K on one of those fancy machines so I've been waiting for something like the Czur scanner (an Indiegogo project) to come out. --ChipIt (talk) 17:29, 3 June 2016 (EDT)
You can send them to They will scan them but they have to cut the bindings and i doubt they will give them back ZyMOS (talk) 01:58, 4 June 2016 (EDT)
another resource i found:
Interesting. Out of curiosity, how are they not reaching hosting limit with GitHub? Even our modest amount of docs have reached GBs. --David (talk) 02:11, 29 July 2016 (EDT)

Server upgrades & MediaWiki 1.27[edit]

Hey everyone, just want post here letting you know that next week I'll be taking the time to update my server to Fedora 24. Additionally I'll be updating MediaWiki 1.27 seeing as our current version (MediaWiki 1.25) has reached EOL. So..... if things stop working, there is a good chance I've caused it. Just let me know! -David (talk) 02:58, 29 July 2016 (EDT)

So, it's been a month since I actually posted it and it since been delayed because I decided to upgrade everything. Yesterday I went ahead and actually upgraded the entire server. Everything was outdated by years and had to be upgraded to latest version. This was also necessary due to the increase in web traffic we've been receiving. This is WikiChip's current setup:
  • Intel Xeon E5-2680 v3
  • Fedora 24
  • Nginx 1.10.1
  • PHP 5.6.25
  • MariaDB 10.1.16
  • MediaWiki 1.27.1
  • Semantic MediaWiki 2.4.1
As far as I'm aware all extensions are working. There was a small hiccups with Semantic MediaWiki, but it too seems to work fine (as far as I can tell). The Extension:CustomSidebar that were were using (which was already on life support by 1.25) has completely stopped working. Looks like many of the functions that were deprecated for a very long time were finally removed. I've commented out the affected templates but this does have to be dealt with somehow. Lastly, some languages (such as our mirc section have lost their syntax highlighting). We have to manually fix this up as well somehow. --David (talk)


Effective immediately WikiChip now uses SSL for everything. All "http" links will automatically redirect to their "https" versions. SSL Certificate is provided by Let's Encrypt project. --David (talk) 18:03, 11 September 2016 (EDT)

That's awesome thanks David! --Inject (talk) 15:34, 12 September 2016 (EDT)

possibly bug with sort?[edit]

Has anyone else noticed that when we setup a semantic subquery with a sort option, if the property specified in the sort isn't available for a specific result, it gets discarded completely? This is actually causing some serious issues for processors that do not have a launch date yet. --Inject (talk) 03:33, 6 December 2016 (EST)

I did some searching and I found saying
Sorting a query also influences the result of a query, because it is only possible to sort by property values that a page actually has. Therefore, if a query is ordered by a property (say Population) then SMW will usually restrict the query results to those pages that have at least one value for this property (i.e. only pages with specified population appear). Therefore, if the query does not require yet that the property is present in each query result, then SMW will silently add this condition.
This really bad news for us. Because we certainly have processors with Property:first launched blank (for obvious reason as they're not out yet). Sorting by launched date will filter those processors out. I'm not sure how to actually address this problem. --ChipIt (talk) 12:52, 6 December 2016 (EST)
I asked on the Semantic MediaWiki mailing list. Apparently if the field we're sorting by is not specified in the ask selection list, sort won't filter out NULL properties. If that's indeed the case, we can create a secondary "ldate" property that mirrors the first one - perhaps even have it set to like '3000' by default if 'future=yes'. --David (talk) 03:13, 8 December 2016 (EST)

max memory is finally in MiB[edit]

we should've done it a long time ago, but I've finally changed Property:max memory to MiB for consistency. That does mean a hell lot of stuff (max memory related, mainly in tables/queries) will be somewhat broken. So if you find something, do change it appropriately. Thanks! --David (talk) 16:58, 4 January 2017 (EST)

Yea we should have done it ages ago. I think there are a bunch of other properties we need to convert as well. --ChipIt (talk) 19:40, 4 January 2017 (EST)

Switching over to the new skin[edit]

Hey everyone. I think I'll be pushing the new skin today. If anyone notices something that's broken because of this change, please point them out for me so I can fix them.

Thank you! --David (talk) 17:14, 7 January 2017 (EST)

Everything looks good on my side David. I have noticed the menu icons (I think all font awesome icons?) are not loading on Edge too. But otherwise they work fine on Chrome/FireFox/Opera as far as I can tell. --ChipIt (talk) 18:38, 7 January 2017 (EST)

Kaby Lake articles[edit]

Now that Kaby Lake is fully released (except for W/X I guess) and we have most of the related articles somewhat built up. Can anyone go through the specs of the chips and double check that we have the right info everywhere? I've spent a ton of time making sure everything looks alright but a second pair of eyes wouldn't hurt. --David (talk) 11:00, 13 January 2017 (EST)

Everything looks fine for the most part. Intel has not yet released an update to their optimization manual so there could be a number of tiny arch related changes we need to document once that's out. We are also missing a bunch of articles relating to the sockets used in Kaby. Then we really need to shift our focus on Zen, before it's launched! --ChipIt (talk) 15:09, 13 January 2017 (EST)

MathML is failing[edit]

I've noticed all our math tags have stopped working probably because formulasearchengine is down for whatever reason. Anything we can do about this? --At32Hz (talk) 01:19, 6 February 2017 (EST)

You can see the errors on this page Tebibyte for example. --At32Hz (talk) 01:19, 6 February 2017 (EST)

Semantic MediaWiki 2.5.0[edit]

WikiChip has been upgraded to Semantic MediaWiki 2.5.0 (Release Notes) --David (talk) 12:05, 9 April 2017 (EDT)

WikiChip has been upgraded to MediaWiki 1.28.1 (Release Notes) --David (talk) 12:05, 10 April 2017 (EDT)
In an attempt to cut down on both bandwidth and load time we've done away with the full Font Awesome and instead switched to a handful of used SVG variants. --David (talk) 12:42, 10 April 2017 (EDT)
I think Jon mentioned it before but we need to reinstall the EastTimetine extension. Not really sure why we had a problem with it in the first place but I think we need to re-introduce it. Any thoughts? --ChipIt (talk) 01:46, 12 April 2017 (EDT)
I will see what I can do. --David (talk) 03:22, 12 April 2017 (EDT)
It's installed! --David (talk) 19:20, 15 April 2017 (EDT)

Microprocessor comparison page[edit]

So this has been talked about for a bit now so I figured I'll detail it here so everyone can see and possibly take part of the discussion if they want. As we continue to detail every individual model we've gained the ability to make use of the data in a number of unique ways. One such way is leveraging the embedded semantic properties to create a comparison table feature (similar to Intel's ark) - but we can do it on a much grander scale! Compare any model to any other model! E.g., VIA next to AMD next to an Intel model.

In our current flimsy prototype you can compare virtually any model to any model (e.g. an Intel 8086 to an i7-7700K to a Qualcomm 630 but such comparison diminish in their usefulness as their differences (especially ISA, but also date, node, market segment, etc..) grow. We will likely keep that functionality moving forward but add some kind of indicator informing the user they are comparing models that differ greatly.

Anyway. This is an initial post, I'll post updates as we continue to make progress. --ChipIt (talk) 02:18, 12 April 2017 (EDT)

Mobile site style fixes[edit]

So I've been spending some time attempting to fix some of the issues people have been having. Almost all the issues at the moment involve the mobile style. It getting clear how difficult it is to try to make our site responsively size to the smallest devices that visit our website - particularly iPhones. There's been a number of requests to try to address some of those issues so that's where my focus will be. If anyone is seeing some more problems, please drop them here. --ChipIt (talk) 00:50, 23 May 2017 (EDT)

Feel free to rework the entire front page pretty much. As it stand it looks like ass on mobile. Nothing really shifts and scales there properly. This is even a problem on low rest tables. --David (talk) 06:44, 24 May 2017 (EDT)
uarch template is now mobile-friendly - I updateed that template. Other templates will have to wait as they are way too complex for a simple switch. --David (talk) 08:22, 26 May 2017 (EDT)
The main page was switched to a responsive grid layout. It's in pretty good shape but some rough spots needs to possibly be fixed. --ChipIt (talk) 01:21, 27 May 2017 (EDT)
The main microprocessor template is now being switched over to the new template which is much more mobile friendly. --David (talk) 21:36, 7 June 2017 (EDT)