From owner-freebsd-current@FreeBSD.ORG  Thu Jul  3 10:38:24 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 642AF37B401
	for <current@freebsd.org>; Thu,  3 Jul 2003 10:38:24 -0700 (PDT)
Received: from rootlabs.com (root.org [67.118.192.226])
	by mx1.FreeBSD.org (Postfix) with SMTP id 169B943FDF
	for <current@freebsd.org>; Thu,  3 Jul 2003 10:38:23 -0700 (PDT)
	(envelope-from nate@rootlabs.com)
Received: (qmail 92043 invoked by uid 1000); 3 Jul 2003 17:38:23 -0000
Date: Thu, 3 Jul 2003 10:38:23 -0700 (PDT)
From: Nate Lawson <nate@root.org>
To: Koop Mast <einekoai@chello.nl>
In-Reply-To: <1057230554.27367.90.camel@headcrash.prisma.quccc.org>
Message-ID: <20030703103628.O92002@root.org>
References: <20030701010230.U86209@root.org>
	<1057230554.27367.90.camel@headcrash.prisma.quccc.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: "acpi-jp@jp.FreeBSD.org" <acpi-jp@jp.FreeBSD.org>
cc: FreeBSD current <current@freebsd.org>
Subject: Re: [acpi-jp 2378] Re: Updated ec-burst.diff patch
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jul 2003 17:38:24 -0000

On Thu, 3 Jul 2003, Koop Mast wrote:
> My machine an ASUS L3800S laptop.
> Before the burst_ec patch I am using the hw.acpi.ec.event_driven sysctl.
> This "fixed" the panic that occurred when switching to battery power.
> When using the patch I get same behavior as in the pre-event_driven="1"
> days :)

Heh, ok.

> Setting / unsetting hw.acpi.ec.burst_mode in /boot/loader.conf doesn't
> make a different.

There was a problem with the patch such that setting
hw.acpi.ec.burst_mode=0 did not correctly disable the ENABLE_BURST
command.  So that is why it had no effect.  I'll be posting an updated
diff sometime this weekend.  Thanks to all who have been testing this.

-Nate