From owner-freebsd-amd64@FreeBSD.ORG Fri Jul 1 17:21:49 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8625B16A41C; Fri, 1 Jul 2005 17:21:49 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F3DA43D1F; Fri, 1 Jul 2005 17:21:49 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j61HLdtQ029263; Fri, 1 Jul 2005 10:21:39 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j61HLdHS029262; Fri, 1 Jul 2005 10:21:39 -0700 Date: Fri, 1 Jul 2005 10:21:39 -0700 From: Brooks Davis To: Jia-Shiun Li Message-ID: <20050701172139.GA25916@odin.ac.hmc.edu> References: <200506290818.j5T8IELL002348@peedub.jennejohn.org> <42C3F72E.9070902@speakeasy.net> <8f55402905063018441217c95a@mail.gmail.com> <20050701015457.GC4460@dragon.NUXI.org> <42C5220B.1000203@crossflight.co.uk> <1d6d20bc050701065367a01e8b@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gBBFr7Ir9EOA20Yy" Content-Disposition: inline In-Reply-To: <1d6d20bc050701065367a01e8b@mail.gmail.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: Guy Dawson , freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: AMD64 X2 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jul 2005 17:21:49 -0000 --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 01, 2005 at 09:53:27PM +0800, Jia-Shiun Li wrote: > On 7/1/05, Guy Dawson wrote: > > David O'Brien wrote: > > > It really should be that simple. All the external interfaces and pins > > > are the same for Athlon64-939 and Athlon64 X2. They have the same > > > thermal specifications, etc... > >=20 > > It's the only way AMD could reasonably do it. To require a different > > motherboard for X1 (?) and X2 chips would have the mobo makers rioting! >=20 > That's what Intel did. Requiring a new i945/i955-based board for their > rushed dual-core CPUs. Only use the same socket but varied pin > definition. If you put the new CPU on an i915 board, it will shutdown > automatically to 'protect'. In contrast Athlon64 claimed to be > designed with dual-core capability in mind from the beginning. It is worth noting that some motherboard manufactures did produce boards that don't work with dual core opterons. In particular the Tyan K8SR prior to rev-D doesn't work because they proview a couple too few watts to the CPU sockets. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --gBBFr7Ir9EOA20Yy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFCxXuiXY6L6fI4GtQRAt/XAKCfJobiSWfzOi9M1Yoe1zjeipn5vACgxUzU eyyZn6nArzjgBh2C6UvHF98= =HTE6 -----END PGP SIGNATURE----- --gBBFr7Ir9EOA20Yy--