From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: tigran@veritas.com (Tigran Aivazian)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox), linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.2ac7
Date: Fri, 2 Mar 2001 16:59:12 +0000 (GMT) [thread overview]
Message-ID: <E14Ystf-0001vP-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.21.0103021638260.6279-100000@penguin.homenet> from "Tigran Aivazian" at Mar 02, 2001 04:46:40 PM
> the bad news to this "rule" is that I just found one "exception". Namely,
> I have Celeron-600/100 and PentiumII-333/66 and both evaluate to
> bus/mul=0/0 even in 4bit bus representation which is impossible. So, this
> is my big stumbling block.... if you tell me how to overcome
> this, I can very quickly build buscode[] table that works on all other
> machines I have.
>
> also, a pointer to anything written down about bus encoding in 2E MSR
> would be nice.
Cyrix III samuel data book
Mobile Intel(R) Pentium III Processor in BGA2 and ,,
[24940903.pdf]
Table 14 in paticular gives the config bits
This also implies a bus selection table of
00 66MHz
01 100Mhz
10 Reserved
11 133 Mhz
next parent reply other threads:[~2001-03-02 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0103021638260.6279-100000@penguin.homenet>
2001-03-02 16:59 ` Alan Cox [this message]
2001-03-02 17:56 ` Tigran Aivazian
[not found] <Pine.LNX.4.21.0103021356370.6279-100000@penguin.homenet>
2001-03-02 16:11 ` Tigran Aivazian
2001-03-02 16:38 ` Alan Cox
2001-03-02 16:22 ` Alan Cox
2001-03-01 1:31 Alan Cox
2001-03-01 13:04 ` Maciej W. Rozycki
2001-03-01 13:11 ` Ingo Molnar
2001-03-01 14:24 ` Maciej W. Rozycki
2001-03-01 21:16 ` José Luis Domingo López
2001-03-01 21:11 ` Tigran Aivazian
2001-03-01 22:39 ` Alan Cox
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=E14Ystf-0001vP-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.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 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®