From owner-freebsd-acpi@FreeBSD.ORG Thu Oct 27 21:44:35 2005 Return-Path: X-Original-To: freebsd-acpi@FreeBSD.org Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4452B16A41F for ; Thu, 27 Oct 2005 21:44:35 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCBC043D45 for ; Thu, 27 Oct 2005 21:44:32 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id j9RLqwmk062414; Thu, 27 Oct 2005 17:52:59 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-acpi@FreeBSD.org Date: Thu, 27 Oct 2005 17:44:14 -0400 User-Agent: KMail/1.6.2 References: <971FCB6690CD0E4898387DBF7552B90E0323D7B6@orsmsx403.amr.corp.intel.com> <435928CA.1010305@root.org> <55E0CA58-AC1E-48E4-A4D0-DDC5829D3690@yahoo.fr> In-Reply-To: <55E0CA58-AC1E-48E4-A4D0-DDC5829D3690@yahoo.fr> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200510271744.17558.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1149/Thu Oct 27 16:20:09 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Mathieu Prevot Subject: Re: ACPI errors on amd64 (sempron) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2005 21:44:35 -0000 On Thursday 27 October 2005 05:39 pm, Mathieu Prevot wrote: > I simply added > > #define ACPI_MISALIGNED_TRANSFERS > > in /usr/src/sys/amd64/include/acpica_machdep.h so the intel > actypes.h is preserved. > Maybe it is simpler than touching the Robert's / Intel's code. Is > it right ? > If so, someone have to commit it on the CVS sources. Can you do it > before the release ? It's already fixed in (soon to be imported) ACPICA-20051021 code. Jung-uk Kim