From: Dave Jones <davej@codemonkey.org.uk>
To: Adam Voigt <adam@cryptocomm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.39 XConfig Processor Detection
Date: Mon, 30 Sep 2002 14:30:57 +0100 [thread overview]
Message-ID: <20020930133057.GA8868@suse.de> (raw)
In-Reply-To: <1033392021.1491.6.camel@beowulf.internetstore.com>
On Mon, Sep 30, 2002 at 09:20:21AM -0400, Adam Voigt wrote:
> Apologies if this has already been noted or if I'm posting
> this to the wrong place/annoying you very busy people needlessly,
> but when I run XConfig, in the "Processor Type and Features" tab
> it autodetects my processor as a Pentium-4 when in fact it is a
> P3 700MHZ. The last time I installed a kernel (2.4.x) by hand, it did
> autodetect the processor on that machine (Athlon), so I assume that
> feature is still active. Anyways, here's the output from my cpuinfo:
There's no 'autodetect' feature.
Only defconfig, which sets the default option.
These defaults match whatever Linus is currently using, so
it seems he upgraded his Athlon box to a P4 8-)
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-09-30 13:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 7:46 2.3.39 compile errors on Alpha Jochen Friedrich
2002-09-30 7:59 ` Jochen Friedrich
2002-09-30 11:08 ` Adrian Bunk
2002-09-30 12:35 ` Alan Cox
2002-09-30 12:25 ` David S. Miller
2002-09-30 13:15 ` Alan Cox
2002-09-30 13:20 ` 2.5.39 XConfig Processor Detection Adam Voigt
2002-09-30 13:30 ` Dave Jones [this message]
2002-09-30 13:48 ` Adam Voigt
2002-09-30 20:39 ` 2.3.39 compile errors on Alpha David S. Miller
2002-09-30 17:58 ` 2.3.39 LLC on Alpha broken? Jochen Friedrich
2002-09-30 18:07 ` Arnaldo Carvalho de Melo
2002-09-30 8:04 ` Jochen Friedrich
2002-09-30 21:04 ` Jochen Friedrich
2002-10-01 14:46 ` Ivan Kokshaysky
2002-10-01 16:05 ` Falk Hueffner
2002-09-30 20:59 ` David S. Miller
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=20020930133057.GA8868@suse.de \
--to=davej@codemonkey.org.uk \
--cc=adam@cryptocomm.com \
--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;
as well as URLs for NNTP newsgroup(s).