From owner-freebsd-current Thu Jan 16 11: 6:43 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D02C37B401 for ; Thu, 16 Jan 2003 11:06:42 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 5FC7243F5B for ; Thu, 16 Jan 2003 11:06:41 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 47334 invoked by uid 1000); 16 Jan 2003 19:06:41 -0000 Date: Thu, 16 Jan 2003 11:06:41 -0800 (PST) From: Nate Lawson To: Terry Lambert Cc: freebsd-current@FreeBSD.ORG Subject: Re: bad ACPL asl's on motherboards In-Reply-To: <3E26FF8C.45EB637B@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 16 Jan 2003, Terry Lambert wrote: > "Cagle, John (ISS-Houston)" wrote: > > You might ask that question on the ACPI development list. I think there > > are several people who have contributed patched ASL's for machines that > > are broken. Here's a link: > > > > Acpi-devel mailing list > > Acpi-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/acpi-devel > > Repeat: These machines work fine under Windows; the problem > is not the BIOS, it's the OS's ASL interpreter. There's another wrinkle in that the interpreter is supplied by Intel. Some difficulties were _introduced_ by them, notably the strict var scope checking. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message