From: okamoto@granite.cias.osakafu-u.ac.jp
To: plan9@granite.cias.osakafu-u.ac.jp
Subject: [9fans] Winchip
Date: Mon, 4 Sep 2000 16:23:35 +0900 [thread overview]
Message-ID: <200009040724.DAA11318@cse.psu.edu> (raw)
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
next reply other threads:[~2000-09-04 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-04 7:23 okamoto [this message]
2000-09-07 1:05 okamoto
2000-09-07 1:22 ` Boyd Roberts
2000-09-07 1:46 okamoto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200009040724.DAA11318@cse.psu.edu \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--cc=plan9@granite.cias.osakafu-u.ac.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).