From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.5] notsc option needs some attention/TLC
Date: Sun, 10 Nov 2002 19:03:57 +0000 (UTC) [thread overview]
Message-ID: <aqmait$tmb$1@forge.intermeta.de> (raw)
In-Reply-To: Pine.LNX.4.44.0211091044060.12487-100000@home.transmeta.com
Linus Torvalds <torvalds@transmeta.com> writes:
> - a kernel compiled for TSC-only. This one simply will not _work_ without
> a TSC, since it is statically compiled for the TSC case. Here, "notsc"
> simply cannot do anything, so it just prints a message saying that it
> doesn't work.
IMHO, if you boot a "TSC-only" kernel on a machine without TSC, the correct
answer should be
Panic: This kernel is compiled for TSC-only. No TSC found.
Machine halted.
Same goes IMHO for "i686 on lower", "i586 on lower" and so on.
Everything else leads to strange effects and hard to decipher bug
reports. If in doubt, boot i386 compiled kernel.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
next prev parent reply other threads:[~2002-11-10 18:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-09 12:00 [PATCH][2.5] notsc option needs some attention/TLC Mikael Pettersson
2002-11-09 13:05 ` Alan Cox
2002-11-09 16:34 ` Martin J. Bligh
2002-11-09 18:09 ` Zwane Mwaikambo
2002-11-09 18:51 ` Linus Torvalds
2002-11-10 19:03 ` Henning P. Schmiedehausen [this message]
2002-11-12 11:29 ` Maciej W. Rozycki
2002-11-11 1:21 ` William Lee Irwin III
2002-11-11 1:51 ` Linus Torvalds
2002-11-11 8:15 ` William Lee Irwin III
2002-11-11 13:24 ` Alan Cox
2002-11-09 19:10 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-11-09 17:52 J.E.J. Bottomley
2002-11-10 5:32 ` Zwane Mwaikambo
2002-11-10 14:25 ` J.E.J. Bottomley
2002-11-09 4:52 Zwane Mwaikambo
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='aqmait$tmb$1@forge.intermeta.de' \
--to=hps@intermeta.de \
--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