From: Christian Volkmann <haveaniceday@cv-sv.de>
To: linux-kernel@vger.kernel.org
Cc: Dave Jones <davej@redhat.com>, Adrian Bunk <bunk@stusta.de>,
Christian Volkmann <haveaniceday@cv-sv.de>,
ak@suse.de, Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC: 2.6 patch] i386: remove support for the Rise CPU
Date: Thu, 31 May 2007 19:37:52 +0200 [thread overview]
Message-ID: <465F07F0.3000406@cv-sv.de> (raw)
In-Reply-To: <20070531133106.GA26030@redhat.com>
The SIS550 chip uses the mP6 core according to http://en.wikipedia.org/wiki/MP6
May be this code can improve the capability of these SIS550 system on a chip ?
But this should be a different story.
Dave Jones wrote:
> On Thu, May 31, 2007 at 07:22:38AM +0200, Adrian Bunk wrote:
> > On Thu, May 17, 2007 at 05:47:54PM -0400, Dave Jones wrote:
> > > On Thu, May 17, 2007 at 11:28:01PM +0200, Christian Volkmann wrote:
> > >
> > > > - Important: somebody to check other CPU types if the same behavior happens.
> > >
> > > arch/i386/kernel/cpu/rise.c
> > >
> > > Though, I've *never* seen or even heard of someone with one of those CPUs,
> > > so whether we need to care is questionable. The mp6 did actually make it
> > > to manufacture aparently, but I don't think anyone actually bought one.
> > > http://en.wikipedia.org/wiki/Rise_Technology for a pic of this mythical beast.
> >
> > Considering that arch/i386/kernel/cpu/rise.o takes a few bytes in every
> > i386 kernel image, what about removing it?
>
> I'll be amazed if someone complains.
> We'll still boot fine on those CPUs without that support code too,
> we just won't advertise cx8 to userspace, and /proc/cpuinfo
> won't prettyprint the name. whoopdy-do.
>
> Should we actually find someone who a) has one and b) is crazy enough
> to still run it today, we could always add this stuff back.
>
> Signed-off-by: Dave Jones <davej@redhat.com>
>
> Dave
>
next prev parent reply other threads:[~2007-05-31 17:39 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 0:09 2.6.22-rc1 does not boot on VIA C3_2 cause of X86_CMPXCHG64 Christian
2007-05-17 0:42 ` Dave Jones
2007-05-17 1:15 ` H. Peter Anvin
2007-05-17 1:55 ` H. Peter Anvin
2007-05-17 1:39 ` Christian
2007-05-17 21:28 ` Christian Volkmann
2007-05-17 21:47 ` Dave Jones
2007-05-17 21:59 ` Christian Volkmann
2007-05-31 5:22 ` [RFC: 2.6 patch] i386: remove support for the Rise CPU Adrian Bunk
2007-05-31 13:31 ` Dave Jones
2007-05-31 17:37 ` Christian Volkmann [this message]
2007-05-31 17:48 ` Dave Jones
2007-05-19 10:22 ` 2.6.22-rc1 does not boot on VIA C3_2 cause of X86_CMPXCHG64 Hans de Bruin
2007-05-17 8:56 ` Alan Cox
2007-05-17 11:51 ` Andi Kleen
2007-05-17 15:02 ` Dave Jones
2007-05-17 22:14 ` H. Peter Anvin
2007-05-19 5:53 ` 2.6.22-rc1 does not boot on VIA C3_2 cause of X86_CMPXCHG64 II Andi Kleen
2007-05-19 6:02 ` Dave Jones
2007-05-19 11:47 ` Andi Kleen
2007-05-19 17:23 ` Dave Jones
2007-05-19 8:22 ` Claas Langbehn
2007-05-19 18:10 ` H. Peter Anvin
2007-05-19 11:42 ` Christian Volkmann
2007-05-19 11:54 ` Andi Kleen
2007-05-23 21:50 ` H. Peter Anvin
2007-05-19 17:26 ` Claas Langbehn
2007-05-19 20:22 ` Via C3: other flags possible ? Christian Volkmann
2007-05-19 22:36 ` Christian Volkmann
2007-05-19 22:52 ` Via C3/C7: " Simon Arlott
2007-05-20 8:19 ` Claas Langbehn
2007-05-20 13:14 ` Christian Volkmann
2007-05-20 12:59 ` Via C3: " Andi Kleen
2007-05-19 17:54 ` 2.6.22-rc1 does not boot on VIA C3_2 cause of X86_CMPXCHG64 II Claas Langbehn
2007-05-17 1:10 ` 2.6.22-rc1 does not boot on VIA C3_2 cause of X86_CMPXCHG64 Linus Torvalds
2007-05-17 1:25 ` Christian
2007-05-17 2:21 ` Linus Torvalds
2007-05-17 3:05 ` H. Peter Anvin
2007-05-17 3:16 ` Linus Torvalds
2007-05-17 4:51 ` H. Peter Anvin
2007-05-17 6:18 ` Dave Jones
2007-05-17 6:31 ` H. Peter Anvin
2007-05-17 6:17 ` Dave Jones
2007-05-17 9:22 ` Hans de Bruin
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=465F07F0.3000406@cv-sv.de \
--to=haveaniceday@cv-sv.de \
--cc=ak@suse.de \
--cc=bunk@stusta.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.