From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 24 13:35:14 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 04CF816A41C for ; Fri, 24 Jun 2005 13:35:14 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C790C43D1D for ; Fri, 24 Jun 2005 13:35:13 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id j5ODYw7c065981; Fri, 24 Jun 2005 06:34:58 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id j5ODYvGk065980; Fri, 24 Jun 2005 06:34:57 -0700 (PDT) (envelope-from obrien) Date: Fri, 24 Jun 2005 06:34:57 -0700 From: "David O'Brien" To: Martin Cracauer Message-ID: <20050624133457.GC65546@dragon.NUXI.org> References: <200506131616.j5DGGDfr067534@lurza.secnetix.de> <200506132038.25975.josemi@redesjm.local> <200506131147.50300.peter@wemm.org> <200506132102.56346.josemi@redesjm.local> <20050623181856.A67269@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050623181856.A67269@cons.org> X-Operating-System: FreeBSD 6.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.9i Cc: freebsd-amd64@freebsd.org Subject: Re: Athlon64 board with ECC support? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jun 2005 13:35:14 -0000 On Thu, Jun 23, 2005 at 06:18:56PM -0400, Martin Cracauer wrote: > And I suppose the BIOS needs to support it, too, Correct. > although it is not > clear to me how ECC exceptions are supposed to be routed anyway. > Clearly some chip not being CPU or RAM needs to have a say in the > exception delivery? Anybody understands how this works? Why?? The memory controller is on the same die as the CPU. The exception is handled w/in the CPU and it never goes out to any support chip. -- -- David (obrien@FreeBSD.org)