From owner-freebsd-hackers Fri Dec 22 15:22:32 2000 From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 22 15:22:30 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 812E937B400; Fri, 22 Dec 2000 15:22:26 -0800 (PST) Received: from bellatlantic.net (client-151-198-135-46.nnj.dialup.bellatlantic.net [151.198.135.46]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id SAA15414; Fri, 22 Dec 2000 18:22:19 -0500 (EST) Sender: root@smtp02.teb1.iconnet.net Message-ID: <3A43E22B.61A7A49C@bellatlantic.net> Date: Fri, 22 Dec 2000 18:22:19 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Mike Smith Cc: heckfordj@psi-domain.co.uk, freebsd-hackers@FreeBSD.ORG Subject: Re: Pentium 4 References: <200012212115.eBLLFDj01783@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > Is there now support for the Pentium 4 in FreeBSD?? > > We've always run on the P4. > > > If so, is there an option such as CPUCLASS 786 in the Kernel?? > > No, it's still a 686. Basically, there are 3 possible issues for Pentium4: - higher clock frequency (also for newer P3) may cause overflow in counters of delay loops - hopefully this does not happen in FreeBSD - microcode download: it got new model ID, so minor tweaking may be needed to make sure that Pentium4 is recognised as upgradable (this depends on how model comparison is done for example, Linux needed this tweaking, UnixWare did not) - microcode download: CPUs must be handled one by one sequentially to accomodate the two-CPUs-on-one-chip technology (to exclude the case when two logical CPUs on the same chip are being told to do microcode upgrade at the same time) I think that's all. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message