From: David Relson <relson@osagesoftware.com>
To: "Giacomo A. Catenazzi" <cate@student.ethz.ch>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@torque.net
Subject: Re: [PATCH] Processor autodetection (when configuring kernel)
Date: Fri, 29 Dec 2000 09:09:01 -0500 [thread overview]
Message-ID: <4.3.2.7.2.20001229090753.00bc69a0@mail.osagesoftware.com> (raw)
In-Reply-To: <3A4C941E.EA824F87@student.ethz.ch>
Giacomo,
I don't think cpu_info.sh is quite right. It identified my 500 Mhz Pentium
III as CONFIG_M386. I think CONFIG_M686 is closer, but as I don't know the
significance of all the flags (MMX, TSC, etc), I'm not certain. Since the
flags do include fxsr, the correct answer may be CONFIG_M686FXSR.
Anyhow, here are my results:
[relson@osage relson]$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping : 3
cpu MHz : 501.147
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36
mmx fxsr xmm
bogomips : 999.42
[relson@osage relson]$ ARCH=i386 ; . cpu_detect.sh
GenuineIntel:6:7
CONFIG_M386
Also, here's a patch to make the script echo CONFIG_M686:
diff -urN cpu_detect.sh.orig cpu_detect.sh
--- cpu_detect.sh.orig Fri Dec 29 09:02:27 2000
+++ cpu_detect.sh Fri Dec 29 09:01:14 2000
@@ -18,7 +18,7 @@
case $cpu_id in
GenuineIntel:5:[0123] ) echo CONFIG_M586TSC ;;
GenuineIntel:5:[48] ) echo CONFIG_M586MMX ;;
- GenuineIntel:6:[01356] ) echo CONFIG_M686 ;;
+ GenuineIntel:6:[013567] ) echo CONFIG_M686 ;;
GenuineIntel:6:{8,9,11} ) echo CONFIG_M686FXSR ;;
AuthenticAMD:5:[0123] ) echo CONFIG_M586 ;;
AuthenticAMD:5:{8,9,10,11} ) echo CONFIG_MK6 ;;
David
P.S. I'm running 2.2.18, if it matters.
--------------------------------------------------------
David Relson Osage Software Systems, Inc.
relson@osagesoftware.com Ann Arbor, MI 48103
www.osagesoftware.com tel: 734.821.8800
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-29 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 13:39 Giacomo A. Catenazzi
2000-12-29 14:09 ` David Relson [this message]
2000-12-29 14:09 ` Jan-Benedict Glaw
2000-12-29 14:41 ` David Relson
2000-12-29 15:41 ` Ingo Oeser
2000-12-29 16:46 ` Re:[PATCH, v2] " Giacomo A. Catenazzi
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=4.3.2.7.2.20001229090753.00bc69a0@mail.osagesoftware.com \
--to=relson@osagesoftware.com \
--cc=cate@student.ethz.ch \
--cc=linux-kbuild@torque.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®