public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Gregor Jasny <gjasny@web.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: What happened to Cyrix 6x86 support in 2.6?
Date: Sat, 21 May 2005 17:24:18 +0200	[thread overview]
Message-ID: <428F52A2.4060905@rainbow-software.org> (raw)
In-Reply-To: <200505211625.56664.gjasny@web.de>

Gregor Jasny wrote:
> Hi,
> 
> I have an old machine with a Cyrix 6x86 processor. When running Linux 2.4 it is recognized as a Cyrix and MTRR is enabled:
> 
> kernel: Linux version 2.4.22 (root@Rincewind) (gcc version 2.95.4 20011002 (Debian prerelease)) #2 Fri Nov 28 15:43:13 CET 2003
> ...
> kernel: Enabling CPUID on Cyrix processor.
> kernel: CPU:     After generic, caps: 00000105 00000000 00000000 00000004
> kernel: CPU:             Common caps: 00000105 00000000 00000000 00000004
> kernel: CPU: Cyrix 6x86L 2x Core/Bus Clock stepping 02
> 
> But when I boot a Linux 2.6 kernel with CONFIG_M586=y it recognizes only a 486.

Something like that also happened with my UMC 486. It's now detected as:

Linux version 2.6.8.1-router (root@pentium) (gcc version 3.3.4) #1 Thu 
Sep 9 12:42:25 CEST 2004
...
CPU: After generic identify, caps: 00000000 00000000 00000000 00000000
CPU: After all inits, caps:        00000000 00000000 00000000 00000000
CPU: UMC UMC UMC  ff/02 stepping 03

It used to be detected more nicely in 2.4.x (I don't remember exact string).

-- 
Ondrej Zary

  reply	other threads:[~2005-05-21 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-21 14:25 What happened to Cyrix 6x86 support in 2.6? Gregor Jasny
2005-05-21 15:24 ` Ondrej Zary [this message]
2005-05-21 16:07 ` Diego Calleja
2005-05-21 17:32   ` Ondrej Zary
2005-05-21 20:23 ` Matthias-Christian Ott

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=428F52A2.4060905@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=gjasny@web.de \
    --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