From owner-freebsd-current@FreeBSD.ORG Wed Jul 9 10:07:50 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 BF95C37B401 for ; Wed, 9 Jul 2003 10:07:50 -0700 (PDT) Received: from kundenserver16.yws-admin.de (kundenserver16.yws-admin.de [217.115.154.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BF1443FAF for ; Wed, 9 Jul 2003 10:07:49 -0700 (PDT) (envelope-from flo@kasimir.com) Received: from kasimir.com (pD9E1DF32.dip.t-dialin.net [217.225.223.50]) by kundenserver16.yws-admin.de (Postfix) with ESMTP id B911735261E; Wed, 9 Jul 2003 19:08:06 +0200 (CEST) Message-ID: <3F0C4BE1.1050400@kasimir.com> Date: Wed, 09 Jul 2003 19:07:45 +0200 From: Florian Smeets User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030701 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <20030708220146.V3143@root.org> In-Reply-To: <20030708220146.V3143@root.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: acpi-jp@jp.freebsd.org cc: current@freebsd.org Subject: Re: PATCH - updated EC driver 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: Wed, 09 Jul 2003 17:07:51 -0000 Nate Lawson wrote: > If you tested my previous acpi_ec.c patch (or even if you didn't), please > test the following one: > > http://root.org/~nate/freebsd/ec-new.diff > > I will be committing this is in a few days if any problems that arise are > successfully addressed. It fixes numerous races and the broken tsleep > approach in the current version. Note that it does NOT have the > experimental burst mode support I had included in the last patch. It > appears that burst mode is more difficult to handle than I have time for > and the actual time spent in DELAY is low (~1-5 us per transaction). There > is no special dmesg output to report with this, just make sure it doesn't > break things (or fixes things for you). > [...] Hey Nate, works fine for me this time. No errors nothing just fine :) Regards, flo