public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Cyrix III boot fix and bug report
Date: Sun, 07 Jan 2001 14:22:08 -0800	[thread overview]
Message-ID: <3A58EC10.4C99F976@transmeta.com> (raw)
In-Reply-To: <E14FNek-0003Nt-00@the-village.bc.nu>

Alan Cox wrote:
> 
> > (Could this code have been written by someone who was confused between
> > MSR 0x80000001 and CPUID 0x80000001?)
> 
> It looks like thats what happened. The docs say it has 3dnow and mmx but
> I think your diagnosis is correct

Especially since it's bit 31 in EDX.  I don't think Cyrixi uses MSRs in
the 0x8000xxxx range.  I bet this should have been CPUID.

I suspect that that whole code should look more like this.  The MSR
access shouldn't have any effect on the extended CPUID flags, so that
shouldn't need to be there at all, unless there are Cyrix III's out there
which fail to report it in CPUID.

	-hpa

	case 6: /* Cyrix III */
		rdmsr (0x1107, lo, hi);
		lo |= (1<<1 | 1<<7);    /* Report CX8 & enable PGE */
                wrmsr (0x1107, lo, hi);

		/* Update the feature flags to include just revealed ones */
		c->x86_capability[0] = cpuid_edx(1);

		get_model_name(c);
		display_cacheinfo(c);
                break;


-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
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:[~2001-01-07 22:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-07 19:19 [PATCH] Cyrix III boot fix and bug report Ingo Oeser
2001-01-07 18:29 ` Alan Cox
2001-01-07 21:42   ` H. Peter Anvin
2001-01-07 21:47     ` Alan Cox
2001-01-07 22:22       ` H. Peter Anvin [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=3A58EC10.4C99F976@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hpa@zytor.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