From: Cesar Eduardo Barros <cesarb@nitnet.com.br>
To: linux-kernel@vger.kernel.org
Subject: CPU name for "pure" i386 missing
Date: Mon, 26 Feb 2001 21:49:00 -0300 [thread overview]
Message-ID: <20010226214900.A11142@flower.cesarb> (raw)
Looks like every time the CPU detection code is rewritten, the printing of the
CPU name for "pure" (i.e. "original") 386s suffer. Last time, the "\n" after
the "CPU: 386" line was missing.
This time it's worse. It's tripping the "unknown CPU" code path:
CPU: Before vendor init, caps: 00000000 00000000 00000000, vendor = 255
[...]
CPU: ff/00
and looking at /proc/cpuinfo:
processor : 0
vendor_id : unknown
cpu family : 3
model : 0
model name : ff/00
stepping : unknown
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : no
fpu_exception : no
cpuid level : -1
wp : no
flags :
bogomips : 3.62
Shouldn't the code be supposed to figure that, since there is no cpuid, it
should be a 386 or an early 486?
I think that table_lookup_model in arch/i386/kernel/setup.c should code a
vendor of 255 as a special case and return "386" or something like that instead
of bailing out. If everybody agrees, I'll make a patch for Linus.
--
Cesar Eduardo Barros
cesarb@nitnet.com.br
cesarb@dcc.ufrj.br
next reply other threads:[~2001-02-27 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 0:49 Cesar Eduardo Barros [this message]
2001-02-27 14:08 ` [PATCH] Re: CPU name for "pure" i386 missing Cesar Eduardo Barros
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=20010226214900.A11142@flower.cesarb \
--to=cesarb@nitnet.com.br \
--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;
as well as URLs for NNTP newsgroup(s).