All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86 boot time check for cpu features
Date: Fri, 03 Nov 2000 08:51:57 -0500	[thread overview]
Message-ID: <3A02C2FD.5A3C9899@didntduck.org> (raw)
In-Reply-To: <E13rgMG-0003Uc-00@the-village.bc.nu>

Alan Cox wrote:
> 
> > +     lea     cpuid_fail_msg, %si
> > +     call    prtstr
> > +1:   jmp     1b
> > +cpuid_fail_msg:
> > +     .string "Required CPU features are not present - compile kernel for the proper CPU type."
> > +cpuid_pass:
> 
> Only one very minor suggestion
> 
> 1:      hlt
>         j 1b
> 
> Q:      are any of the things you test present in processors only after we
>         do magic 'cpuid' enable invocations ?

AFAIK, none of the braindead chips have cmov instructions or PAE support
(only PentiumPro+ and Athlon do).  If someone can prove me wrong I'd
like to know.

-- 

						Brian Gerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-03 13:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-03  2:21 [PATCH] x86 boot time check for cpu features Brian Gerst
2000-11-03 12:54 ` Alan Cox
2000-11-03 13:51   ` Brian Gerst [this message]
2000-11-03 23:08   ` Brian Gerst
2000-11-04  0:23     ` Alan Cox
2000-11-04  1:28       ` Brian Gerst
  -- strict thread matches above, loose matches on Subject: below --
2000-11-04  1:01 davej
2000-11-04  1:02 davej
2000-11-04  2:53 ` Brian Gerst
2000-11-04  2:07   ` davej

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=3A02C2FD.5A3C9899@didntduck.org \
    --to=bgerst@didntduck.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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.