From owner-freebsd-current Sat Nov 20 6:24:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1]) by hub.freebsd.org (Postfix) with ESMTP id 7C84514CED for ; Sat, 20 Nov 1999 06:24:02 -0800 (PST) (envelope-from lh@aus.org) Received: from PHOENIX.ZER0.NET (lh@ZER0.NET [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id JAA17913; Sat, 20 Nov 1999 09:22:40 -0500 (EST) Message-Id: <199911201422.JAA17913@ayukawa.aus.org> X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-9 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <867ljelopt.fsf@not.demophon.com> Content-Type: text/plain; charset=unix-ascii charset: UNIX-ACSII charset: UNIX-ACSII Date: Sat, 20 Nov 1999 09:22:39 -0500 (EST) From: Luke Hollins To: Ville-Pertti Keinonen Subject: Re: cpu name Cc: freebsd-current@FreeBSD.ORG, freebsd@nowcool.dhs.org, Jeroen Ruigrok/Asmodai Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> printf("CPU: "); > Look again, the AMD identification can fill cpu_model using cpuid. > > The code doesn't appear to have changed lately, so if there is a > problem it's probably a matter of some processor being incorrectly > identified as supporting the feature. Or the processor is broken. I never reported it because I usually use -O2 , but I have a box that ran -current up until very recently that was updated fairly often, and it showed the CPU name as that \^E alot. I checked for sure and it did get the right id, 0x580 , but still showed \^E instead of whats defined for 0x580 Luke To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message