From owner-freebsd-current Sun Oct 1 15: 3:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106]) by hub.freebsd.org (Postfix) with ESMTP id BC70937B66C for ; Sun, 1 Oct 2000 15:03:26 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e91M4wJ00361; Sun, 1 Oct 2000 15:04:58 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010012204.e91M4wJ00361@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mitsuru IWASAKI Cc: takawata@shidahara1.planet.sci.kobe-u.ac.jp, haro@tk.kubota.co.jp, current@freebsd.org, acpi-jp@jp.FreeBSD.org Subject: Interesting AML bug... recommended workaround? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Oct 2000 15:04:58 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's what seems to be an interesting AML or AML parser bug. OperationRegion(PSRG, SystemMemory, 0x0410, 0x1) Field(PSRG, DWordAcc, NoLock, Preserve) { , 2, PS2E, 1 } The field is marked for 32-bit access, but the region is only 1 byte wide. What's the correct thing to do here? Expand the region to accomodate the field's access requirements? Constrain the access size of the field to that of the region? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message