From owner-freebsd-current Wed Oct 20 23:54:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from not.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with ESMTP id 64BD814E93 for ; Wed, 20 Oct 1999 23:54:49 -0700 (PDT) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id JAA13238; Thu, 21 Oct 1999 09:53:06 +0300 (EEST) (envelope-from will) To: Stephen Roome Cc: current@freebsd.org Subject: Re: Anyone adding "support" for Athlons. References: From: Ville-Pertti Keinonen Date: 21 Oct 1999 09:53:06 +0300 In-Reply-To: Stephen Roome's message of "20 Oct 1999 18:18:17 +0300" Message-ID: <86zoxd19yl.fsf@not.demophon.com> Lines: 18 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Roome writes: > As the title says, is anyone working on support for Athlons, and when can we > expect it to arrive back in -stable ? Athlons don't need any special support, they are fully compatible with Intel's latest processors. > (I can't find anything in the latest versions of sys/i386/i386/identcpu.c) The identification for AMD processors models that can report their name using cpuid is redundant, even for cpus that are currently listed there. I don't know whether this is intentional. It seems that currently, the policy of identcpu.c is to prefer the cpuid string, so the patch in pr i386/14440 should be a no-op. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message