From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Gustav Lidberg <gustavl@home.se>,
Michael Elizabeth Chastain <mec@shout.net>
Cc: linux-kernel@vger.kernel.org, Mikael Pettersson <mikpe@csd.uu.se>
Subject: Re: make menuconfig creates erronous config for 386
Date: Wed, 9 Mar 2005 10:53:09 -0300 [thread overview]
Message-ID: <20050309135309.GA15110@logos.cnet> (raw)
In-Reply-To: <422F04F7.1020701@home.se>
Hi,
On Wed, Mar 09, 2005 at 03:15:19PM +0100, Gustav Lidberg wrote:
> Hi
>
> There is a bug in "make menuconfig". If one chooses 386 or 486 for cpu
> type, CONFIG_X86_TSC=y is set in .config. This creates a kernel that is
> unbootable on 386. Testing shows that it worked in 2.4.19, but is broken
> from 2.4.20 onwards. Someone should definetely look into this.
> (I'm not subscribed to lkml)
Quoting Mikael Pettersson, from
http://marc.theaimsgroup.com/?l=linux-kernel&m=109986177309630&w=2
"Do a 'make oldconfig' after switching CPU type from a
TSC-capable one to a TSC-less one in 2.4 kernels. There
is a known bug in the old configuration system where it
can leave derived options in an inconsistent state after
a single round of option changes. CONFIG_X86_TSC is the
prime example of this. Doing a second configuration round
allows the derived options to reach a fixpoint."
Note that arch/i386/defconfig contains CONFIG_X86_TSC=y.
Michael, Mikael, what are the possibilities for fixing this
Configure limitation?
In the meantime, I wonder if arch/i386/defconfig should be
changed to contain "CONFIG_X86_TSC=n" instead of "=y" to make
life easier for 386/486 users who use "make menuconfig" without
pre-existing .config files.
This should have been fixed ages ago. :(
prev parent reply other threads:[~2005-03-09 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 14:15 make menuconfig creates erronous config for 386 Gustav Lidberg
2005-03-09 13:53 ` Marcelo Tosatti [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=20050309135309.GA15110@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=gustavl@home.se \
--cc=linux-kernel@vger.kernel.org \
--cc=mec@shout.net \
--cc=mikpe@csd.uu.se \
/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.