linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-kernel@vger.kernel.org
Subject: Re: APIC support on Slot-A Athlon, K6
Date: Mon, 8 Dec 2003 05:58:59 -0600	[thread overview]
Message-ID: <20031208115859.GA17909@dbz.icequake.net> (raw)
In-Reply-To: <20031208102800.5409.87787.Mailman@lists.us.dell.com>

[-- Attachment #1: Type: text/plain, Size: 2168 bytes --]


> >Unfortunately, this disables the APIC support (if it existed) on a
> >Slot-A Athlon 600 MS-6167 (family 6, model 1, AMD-751/756), and a K6/3 400
> >Tyan S1598 (family 5, model 9, MVP3/686A).
> >
> >What is the purpose of this check? Why is the APIC availability dependent
> >on the CPU, rather than just the southbridge?
> 
> This code checks for the ability to enable the local APIC,
> which is integrated into the processor. The local APIC is
> not implemented in K6 or K7 model 1, so the check is correct.

Thanks, that just cleared up a huge misconception (I had the APIC and I/O-APIC
confused, apparently).

This page cleared a lot up (must remember to STFW occasionally):
http://www.microsoft.com/whdc/hwdev/platform/proc/IO-APIC.mspx

> Furthermore, I/O-APIC usage requires (in hardware) that the
> processor has a local APIC.

What can the APIC support alone accomplish, without an I/O-APIC?
Just NMI watchdog and related things? (looking at CONFIG_APIC help)
Looks like I/O-APIC is the real desired feature, but a functioning local
APIC, though not very useful by itself, is a prerequisite for it.

> > Also, there are only
> >checks for Intel and AMD CPUs. Is it not possible to use an APIC in
> >conjunction with a Cyrix, et.al. ?
> 
> The other manufacturers haven't yet implemented local APIC
> functionality in their processors.

Ok, much more clear.

> >The APIC is also not enabled on this machine, but it is a 586B southbridge,=
> > which
> >I am not sure contains an APIC.
> 
> What processor? As I wrote above, I/O-APIC can't be used unless
> the processor has a local APIC.

Cyrix. :D  Obviously, it won't work simply because of that.  I
am curious if the VIA 586B has a IO-APIC though (the 686A/B do) so
that it would work if I put a different processor in it.
VIA no longer put their datasheets on the web anymore...

> Some BIOSen have an option for enabling/disabling I/O-APIC mode.
> Some BIOSen skip the "legacy" MP tables and only announce the
> I/O-APIC config data via ACPI, so working ACPI may be required.

Also useful info.  Thanks!

-- 
Ryan Underwood, <nemesis@icequake.net>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

       reply	other threads:[~2003-12-08 11:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031208102800.5409.87787.Mailman@lists.us.dell.com>
2003-12-08 11:58 ` Ryan Underwood [this message]
2003-12-08 12:06   ` APIC support on Slot-A Athlon, K6 William Lee Irwin III
2003-12-08 17:07 Mikael Pettersson
  -- strict thread matches above, loose matches on Subject: below --
2003-12-08 10:44 Mikael Pettersson
2003-12-08  8:48 Ryan Underwood

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=20031208115859.GA17909@dbz.icequake.net \
    --to=nemesis-lists@icequake.net \
    --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;
as well as URLs for NNTP newsgroup(s).