From owner-freebsd-current@FreeBSD.ORG Sat Sep 1 00:20:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A65116A418; Sat, 1 Sep 2007 00:20:28 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 0C37F13C45E; Sat, 1 Sep 2007 00:20:27 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id l810KKME093867; Fri, 31 Aug 2007 21:20:20 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-current@freebsd.org, obrien@freebsd.org Date: Fri, 31 Aug 2007 21:20:30 -0300 User-Agent: KMail/1.9.7 References: <-3502020561049594852@unknownmsgid> <200708312032.21574.joao@matik.com.br> <20070901000710.GA12223@dragon.NUXI.org> In-Reply-To: <20070901000710.GA12223@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200708312120.31912.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.90.3, clamav-milter version 0.90.3 on msrv.matik.com.br X-Virus-Status: Clean Cc: Roman Divacky , pluknet , =?iso-8859-1?q?Bj=F6rn_K=F6nig?= Subject: Re: Adding k9 and k10 to bsd.cpu.mk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Sep 2007 00:20:28 -0000 On Friday 31 August 2007 21:07:10 David O'Brien wrote: > > > > well, the x2 thing I wasn't thinking it through and you are right, > > what I meant to say that so far as I know all S939-X2 are SSE3 capable > > and rev-E at least as all am2 are > > > > so eventually, athlon64-E would be more appropriate (with proper man > > Why? athlon64-E should apply to athlon64 rev's F & G? k8-sse3 seems > best - with aliases for athlon64-sse3 and opteron-sse3. > ok right but it is harder for an average kernel compiler to find the SSE3=20 feature instead of the cpu's revision but certainly it would be easy to suggest to consult sort of grep -i feat /var/run/dmesg.boot to see if or not in `man make.conf` or somewhere, what then makes it ok as = far=20 as it is well explained=20 > > opterons are not easy but it is already kind of advanced cpu so could be > > Why are Opteron's any harder? because all of them are 64bit but some older ones are not SSE3 capable, < 2= 50=20 I guess now but 252 is but not 100% sure =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br