From: john stultz <johnstul@us.ibm.com>
To: Samium Gromoff <_deepfire@mail.ru>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 386 + TSC -> none good
Date: 22 Oct 2002 09:58:04 -0700 [thread overview]
Message-ID: <1035305887.508.1.camel@laptop.cornchips.homelinux.net> (raw)
In-Reply-To: <20021022165554.DNWW23718.sccrmhc01.attbi.com@laptop.cornchips.homelinux.net >
> The result being a menuconfig selection of 386 cpu in 2.4.20-pre9
> producing a .config with a CONFIG_X86_ENABLE_TSC (or was it _USE_TSC?).
> 2.4.19-rc1 which i`ve ran before has no problem with it.
This is quite curious. Could you please send me your .config?
thanks
-john
next parent reply other threads:[~2002-10-22 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021022165554.DNWW23718.sccrmhc01.attbi.com@laptop.cornchips.homelinux.net >
2002-10-22 16:58 ` john stultz [this message]
2002-10-22 10:59 Samium Gromoff
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=1035305887.508.1.camel@laptop.cornchips.homelinux.net \
--to=johnstul@us.ibm.com \
--cc=_deepfire@mail.ru \
--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
all inboxes | Powered by JetHome®