From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Winchip
Date: Thu,  7 Sep 2000 10:05:27 +0900
From: okamoto@granite.cias.osakafu-u.ac.jp
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-nxyvymttozciebvohwoomypjto"
Message-Id: <20000907010522.60312199D8@mail>
Topicbox-Message-UUID: 0524e86c-eac9-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.
--upas-nxyvymttozciebvohwoomypjto
Content-Disposition: inline
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

Well, there is none who is using such a dumn and strange CPU
here.  I gave it a larger heat sunk, and now got good performance
from it.   The change of the previous post may not be neccessary
if you don't care how the CPU is recongnized. ☺

Kenji


--upas-nxyvymttozciebvohwoomypjto
Content-Type: message/rfc822
Content-Disposition: inline

Received: from granite.cias.osakafu-u.ac.jp ([192.168.1.3]) by diabase; Mon Sep  4 16:28:22 JST 2000
Received: from elmo.cias.osakafu-u.ac.jp (elmo.cias.osakafu-u.ac.jp [157.16.103.2])
	by granite.cias.osakafu-u.ac.jp (8.9.3/8.9.3) with ESMTP id QAA23541;
	Mon, 4 Sep 2000 16:28:25 +0900
Received: from cse.psu.edu (majordom@claven.cse.psu.edu [130.203.3.50])
	by elmo.cias.osakafu-u.ac.jp (8.9.3/3.7W-00080718) with ESMTP id QAA13351;
	Mon, 4 Sep 2000 16:28:32 +0900 (JST)
Received: from localhost (majordom@localhost)
	by cse.psu.edu (8.8.8/8.8.8) with SMTP id DAA11377;
	Mon, 4 Sep 2000 03:26:10 -0400 (EDT)
Received: by claven.cse.psu.edu (bulk_mailer v1.5); Mon, 4 Sep 2000 03:24:41 -0400
Received: (from majordom@localhost)
	by cse.psu.edu (8.8.8/8.8.8) id DAA11323
	for 9fans-outgoing; Mon, 4 Sep 2000 03:24:36 -0400 (EDT)
X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f
Received: from rhyolite.chigaku6.co.jp (granite.cias.osakafu-u.ac.jp [157.16.91.52])
	by cse.psu.edu (8.8.8/8.8.8) with SMTP id DAA11318
	for <9fans@cse.psu.edu>; Mon, 4 Sep 2000 03:24:30 -0400 (EDT)
From: okamoto@granite.cias.osakafu-u.ac.jp
Message-Id: <200009040724.DAA11318@cse.psu.edu>
To: plan9@granite.cias.osakafu-u.ac.jp
Subject: [9fans] Winchip
Date: Mon, 4 Sep 2000 16:23:35 0900
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-9fans@cse.psu.edu
Reply-To: 9fans@cse.psu.edu
Precedence: bulk

I have a Winchip 240MHz CPU, and added it to /sys/src/9/pc/devarch.c's X86type
structure as below:

/*
 * WinChip 240MHz
 */
static X86type x86winchip[] =
{
	{5,	4,	23,	"Winchip 240MHz",},		/* guesswork */
	{ -1,	-1,	23,	"unknown", },		/* total default */
};

I also added lines in cpuidentify() function in the same file as:

	if(strncmp(m->cpuidid, "AuthenticAMD", 12) == 0)
		t = x86amd;
	else if(strncmp(m->cpuidid, "CentaurHauls", 12) == 0)
		t = x86winchip;
	else
		t = x86intel;

Is that all the neccessary patch to use this CPU?  Do I forget anything?
The chip is now recongnized as 240MHz "Winchip 240MHz".
Woever, when I run it longer time, I get hangup of the machine. :-)
I'm wondering this is just the heat problem or something else...

Kenji

--upas-nxyvymttozciebvohwoomypjto--