All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.0test11-ac1
Date: 21 Nov 2000 16:07:52 -0800	[thread overview]
Message-ID: <8vf2oo$338$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1001121195742.28403E-100000@delta.ds2.pg.gda.pl> <E13yMsl-0005Lb-00@the-village.bc.nu>

Followup to:  <E13yMsl-0005Lb-00@the-village.bc.nu>
By author:    Alan Cox <alan@lxorguk.ukuu.org.uk>
In newsgroup: linux.dev.kernel
> 
> > > making any assumptions about APIC availability on a processor.
> > 
> >  OK, but how does it handle the 82489DX?  There are valid configurations
> > using this kind of APIC, including Pentium P54C ones...
> 
> These processors don't report the APIC on the cpuid ? If so then I guess
> the fix is something like this
> 
> 	if( cpuid says there is no local apic && vendor != intel)
> 
> Intel stuff appears to always be happy poking in APIC space. I don't know
> if this is related to the chip internals on the non APIC capable chips.
> 

Nononono... the 82489DX is an *external* APIC, which should be usable
on any Socket 5/7 CPU...

	-hpa
-- 
<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:[~2000-11-22  0:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-21 13:51 Linux 2.4.0test11-ac1 Alan Cox
2000-11-21 18:14 ` Johannes Erdfelt
2000-11-21 18:18   ` Alan Cox
2000-11-21 18:25     ` Maciej W. Rozycki
2000-11-21 18:31       ` Alan Cox
2000-11-21 18:40         ` Maciej W. Rozycki
2000-11-21 18:49           ` Alan Cox
2000-11-21 19:08             ` Maciej W. Rozycki
2000-11-21 19:34               ` Brian Gerst
2000-11-21 23:31               ` Alan Cox
2000-11-22  0:07                 ` H. Peter Anvin [this message]
2000-11-22  0:29                   ` Alan Cox
2000-11-22  0:19                     ` H. Peter Anvin
2000-11-22 15:48                     ` Maciej W. Rozycki
2000-11-22 16:47                       ` Alan Cox
2000-11-22 17:49                         ` Maciej W. Rozycki
2000-11-22 17:58                           ` Alan Cox
2000-11-22 18:02                             ` H. Peter Anvin
2000-11-22 18:06                               ` Alan Cox
2000-11-23  8:23                                 ` Maciej W. Rozycki
2000-11-23  8:52                             ` Vojtech Pavlik
2000-11-22 16:02                 ` Maciej W. Rozycki
2000-11-21 18:54 ` Jeff Garzik
2000-11-21 23:25   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2000-11-21 19:07 Steven Cole
2000-11-21 23:27 ` Alan Cox
2000-11-22  1:20 Steven Cole
2000-11-22 18:18 Bruce_Holzrichter

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='8vf2oo$338$1@cesium.transmeta.com' \
    --to=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 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.