From owner-freebsd-current@FreeBSD.ORG Sat Sep 1 00:07:26 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 B8C2F16A419; Sat, 1 Sep 2007 00:07:26 +0000 (UTC) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 5F5E213C4E1; Sat, 1 Sep 2007 00:07:26 +0000 (UTC) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id l8107B8s025362; Fri, 31 Aug 2007 17:07:11 -0700 (PDT) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.1/8.14.1/Submit) id l8107ATI025361; Fri, 31 Aug 2007 17:07:10 -0700 (PDT) (envelope-from obrien) Date: Fri, 31 Aug 2007 17:07:10 -0700 From: "David O'Brien" To: JoaoBR Message-ID: <20070901000710.GA12223@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, JoaoBR , freebsd-current@freebsd.org, Roman Divacky , pluknet , =?unknown-8bit?Q?Bj=F6rn_K=F6nig?= References: <-3502020561049594852@unknownmsgid> <200708300859.13098.joao@matik.com.br> <53349.192.168.1.2.1188538732.squirrel@webmail.alpha-tierchen.de> <200708312032.21574.joao@matik.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200708312032.21574.joao@matik.com.br> X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.11 Cc: Roman Divacky , freebsd-current@freebsd.org, pluknet , =?unknown-8bit?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 Reply-To: obrien@freebsd.org 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:07:26 -0000 On Fri, Aug 31, 2007 at 08:32:20PM -0300, JoaoBR wrote: > On Friday 31 August 2007 02:38:52 Björn König wrote: > > JoaoBR wrote: > > > but athlon64-x2 for S940 and athlon64-am2 for sse3 capable cpus would be > > > kind of understandable for all > > > [...] > > > venice as said in another mail is not clear for all people and certainly > > > it does not appear on the box or elsewhere > > > > I think the names "athlon64-x2" and "athlon64-am2" would be most confusing > > and ambiguous, because the socket has nothing to do with the feature set > > of the CPU. Athlon64 X2 CPUs are not only available for socket 940, but > > also for AM2 and 939. There are SSE3 CPUs that fit into 940, AM2 and 939. > > > > 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. > opterons are not easy but it is already kind of advanced cpu so could be Why are Opteron's any harder? -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? Let's not play "Jeopardy-style quoting"