From owner-freebsd-current@FreeBSD.ORG Sat Apr 26 15:17:02 2003 Return-Path: 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 0BA1437B401 for ; Sat, 26 Apr 2003 15:17:02 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D9D643FBD for ; Sat, 26 Apr 2003 15:17:01 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0335.cvx21-bradley.dialup.earthlink.net ([209.179.193.80] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 199XyZ-0002qB-00; Sat, 26 Apr 2003 15:16:56 -0700 Message-ID: <3EAB0505.B3D7D98D@mindspring.com> Date: Sat, 26 Apr 2003 15:15:33 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Nate Lawson References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a49824c257e7815ebcb0dd0ce8b99a935da7ce0e8f8d31aa3f350badd9bab72f9c350badd9bab72f9c cc: acpi-jp@jp.freebsd.org cc: current@freebsd.org Subject: Re: New ACPI diffs ready for testing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Apr 2003 22:17:02 -0000 Nate Lawson wrote: > On Sat, 26 Apr 2003, Terry Lambert wrote: > > An Intel employee posted that this is fixed in the newest > > code drop, which is to be available soon. > > It's 0424 and is available now. I'll be rolling a dist with some fixes. Cool! I thought it was going to be weeks, based on the posting! You work fast! 8-). > > You can actually work around this by relaxing the ordering > > restrictions (turning the process two-pass). This is what > > Microsoft does for their implementation, I believe. > > Or you can enter the symbol into the namespace whenever you hit the call > or declaration instead of strictly just the declaration. I thought there was an order of declaration problem on IBM ThinkPads, and some VAIO's (the 505?) that prevented this from happening in a single pass... -- Terry