From: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: remove NexGen support (fwd)
Date: Thu, 01 May 2008 02:15:23 +0400 [thread overview]
Message-ID: <4818EF7B.4040202@gmail.com> (raw)
In-Reply-To: <20080430213457.GD18536@elf.ucw.cz>
Pavel Machek пишет:
> Hi!
>
>> It is claimed that NexGen CPUs were never shipped:
>>
>> http://lkml.org/lkml/2008/4/20/179
>>
>> Also, the kernel support for these chips has been broken for
>> a long time, the code intended to support NexGen thereby being
>> essentially dead.
>
> Are you sure it never shipped? Wikipedia seems to suggest it did ship.
>
> http://www.cpu-info.com/index2.php?mainid=Nx586&page=5
>
> ...FPU for nexgen was never shipped, that implies that CPU did ship.
The main reason for removing the NexGen support was that the latter
had effectively been broken for G-d knows how many years. As a person
somehow involved into embedded development, I simply could not resist
to trim a few dozen bytes of dead binary code off vmlinux. Besides,
the change is trivially revertable (just checked that), and in case
that somebody owns a NexGen box and complains, that can be addressed
in a matter of minutes.
Dmitri
>
> Pavel
>
prev parent reply other threads:[~2008-04-30 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080429081729.GA3921@ucw.cz>
2008-04-30 21:34 ` [PATCH] x86: remove NexGen support (fwd) Pavel Machek
2008-04-30 21:41 ` H. Peter Anvin
2008-04-30 21:51 ` Pavel Machek
2008-04-30 21:56 ` H. Peter Anvin
2008-04-30 21:45 ` Ondrej Zary
2008-04-30 22:15 ` Dmitri Vorobiev [this message]
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=4818EF7B.4040202@gmail.com \
--to=dmitri.vorobiev@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=tglx@linutronix.de \
/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