From owner-freebsd-current Fri Jul 5 6: 2: 2 2002 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 A438A37B400 for ; Fri, 5 Jul 2002 06:01:59 -0700 (PDT) Received: from blackhole.x-echo.com (blackhole.x-echo.com [195.101.94.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25A4F43E4A for ; Fri, 5 Jul 2002 06:01:00 -0700 (PDT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 17QRXl-0005nZ-00; Fri, 05 Jul 2002 13:46:33 +0200 Date: Fri, 5 Jul 2002 13:46:33 +0200 To: Terry Lambert Cc: Takanori Watanabe , Alex Zepeda , current@freebsd.org Subject: Re: ACPI woes again.. Message-ID: <20020705114633.GA22257@poup.poupinou.org> References: <200207050945.SAA28267@axe-inc.co.jp> <3D258C38.9E26407@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D258C38.9E26407@mindspring.com> User-Agent: Mutt/1.3.28i From: Ducrot Bruno 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 Fri, Jul 05, 2002 at 05:08:24AM -0700, Terry Lambert wrote: > Takanori Watanabe wrote: > > +.Sh OVERRIDING YOUR BIOS BYTECODE > > +ACPI interprets bytecode named AML, ACPI Machine Language, provided by BIOS > > +vendor as memory image at boot time. Sometimes, the AML code contains > > +problem that is not appeared in Microsoft implement. So we provide a way > > +to override it with your own AML code. > > +.Pp > > How does Windows deal with hardware that has this problem? > Do they use a "rogues" list, and replace the AML, too (only > automatically)? Actually, their ACPI implementation suck, so that most of buggy AML work. For example, they don't check correctly if a they have the right to read/write to some Operational Region. If an AML declare incorrecly such regions, under FBSD (or other free OS with an ACPI-CA implementation), it can not work since the bound checking work as expected. But as a consequence, those regions can't be acceded. As an example, the status of the AC can not be reported correctly under a Satellite 3000-601 due to this kind of bug. -- Ducrot Bruno http://www.poupinou.org Page profaissionelle http://toto.tu-me-saoules.com Haume page To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message