From: "Jan Beulich" <JBeulich@novell.com>
To: "Dave Jones" <davej@redhat.com>
Cc: <mingo@elte.hu>, <tglx@linutronix.de>,
<linux-kernel@vger.kernel.org>, <hpa@zytor.com>
Subject: Re: [PATCH, v2] i386: tighten dependencies of CPU_SUP_*_32
Date: Fri, 29 Apr 2011 07:54:36 +0100 [thread overview]
Message-ID: <4DBA7CCC020000780003ED3A@vpn.id2.novell.com> (raw)
In-Reply-To: <20110428164228.GA8336@redhat.com>
>>> On 28.04.11 at 18:42, Dave Jones <davej@redhat.com> wrote:
> On Thu, Apr 28, 2011 at 10:03:39AM +0100, Jan Beulich wrote:
>
> > --- 2.6.39-rc5/arch/x86/Kconfig.cpu
> > +++ 2.6.39-rc5-i386-cpu-sup-dependencies/arch/x86/Kconfig.cpu
> > @@ -440,7 +440,7 @@ config CPU_SUP_INTEL
> > config CPU_SUP_CYRIX_32
> > default y
> > bool "Support Cyrix processors" if PROCESSOR_SELECT
> > - depends on !64BIT
> > + depends on M386 || M486 || M586 || M586TSC || M586MMX || (EXPERT && !64BIT)
> > ---help---
> > This enables detection, tunings and quirks for Cyrix processors
> >
> > @@ -494,7 +494,7 @@ config CPU_SUP_TRANSMETA_32
> > config CPU_SUP_UMC_32
> > default y
> > bool "Support UMC processors" if PROCESSOR_SELECT
> > - depends on !64BIT
> > + depends on M386 || M486 || (EXPERT && !64BIT)
> > ---help---
> > This enables detection, tunings and quirks for UMC processors
>
> PROCESSOR_SELECT is already dependant on EXPERT being set.
If EXPERT was omitted from the depends condition, then the whole
option would be unavailable (and hence the prompt invisible) even
if PROCESSOR_SELECT=y (and e.g. M686=y).
The intention, however, is to allow the option to be selectable in
an EXPERT configuration (to have a temporary workaround in
case the condition set isn't precise, or to do testing on
hypothetical new CPUs).
Or to put it differently, the intended behavior change is precisely
for the PROCESSOR_SELECT=n case, so that no impossible CPUs
get auto-enabled.
Jan
prev parent reply other threads:[~2011-04-29 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 9:03 Jan Beulich
2011-04-28 16:42 ` Dave Jones
2011-04-29 6:54 ` Jan Beulich [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=4DBA7CCC020000780003ED3A@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®