From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 25 13:03:25 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 111A316A4CE for ; Wed, 25 Feb 2004 13:03:25 -0800 (PST) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id E60D543D2F for ; Wed, 25 Feb 2004 13:03:24 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 20924 invoked from network); 25 Feb 2004 21:03:24 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 25 Feb 2004 21:03:24 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i1PL3J29045486; Wed, 25 Feb 2004 16:03:21 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: "Ralph S." Date: Wed, 25 Feb 2004 14:09:35 -0500 User-Agent: KMail/1.6 References: <20040223213832.GC36207@saboteur.dek.spc.org> <24224.1077716465@www54.gmx.net> In-Reply-To: <24224.1077716465@www54.gmx.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200402251409.35715.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-hackers@freebsd.org Subject: Re: Local APIC on FreeBSD/i386 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2004 21:03:25 -0000 On Wednesday 25 February 2004 08:41 am, Ralph S. wrote: > Hmm.. I'm running FreeBSD-current (as of Feb 12, 04) and it does implement > 'device apic' for UP systems... but onyl if the APIC has been enabled by > the BIOS. (Maybe I'm just doing something wrong there, though. However, > Intel's Katmai CPUs have an APIC built in, I'm sure of that.) I have tried > to software-enable it, set up the base address and update cpu_feature, but > until now all I get is > boot -v telling me there is no APIC (before, it didn't mention even that > though). You have to have an I/O APIC to talk to the local APIC. That is part of the motherboard chipset. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org