From owner-freebsd-current@FreeBSD.ORG  Mon Jan 26 02:23:44 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7FA3C106566C;
	Mon, 26 Jan 2009 02:23:44 +0000 (UTC)
	(envelope-from pisymbol@gmail.com)
Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28])
	by mx1.freebsd.org (Postfix) with ESMTP id 185B68FC1F;
	Mon, 26 Jan 2009 02:23:43 +0000 (UTC)
	(envelope-from pisymbol@gmail.com)
Received: by yx-out-2324.google.com with SMTP id 8so2277813yxb.13
	for <multiple recipients>; Sun, 25 Jan 2009 18:23:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=ZfB7sxoiifnC8AtNK80vgBC8D0XbI5a+K2OFnAwg3NE=;
	b=NAu65q+lNqDwRCcSN9JKOF2HqE1EVNM82O1dFsm7d+2MBtj6sqDLiXLDiEqhpfPElF
	VGAWPeF+Fyh5gcVoaLdy2wb3casB4cfl2ySi0gsmozitc0OMDbwNA/gzMyOaqkfNpo5l
	DCgwVWZxuk7iRrJ4L9Cy3LbIPfKLIrBWNJh3M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=YYjPslbZ407fGZeGwRaZ7p3vvEnsY0vkF5ptJ5QQ2a2/ajCvnJ0mAQrVCJEepOsGgO
	tvGUyRFWckkzJwtZwLZmUbxoqjdZL7pZFA+jtKyCoDY236jmbiG4+9o5ht1WVTQyUr3d
	FU3R+ZZ/zOvFgUxL4mjAzASyiBuKh4NSU7ZpM=
MIME-Version: 1.0
Received: by 10.90.56.17 with SMTP id e17mr334139aga.46.1232936623416; Sun, 25 
	Jan 2009 18:23:43 -0800 (PST)
In-Reply-To: <3c0b01820901251735m4c6a1abfu37a1634818e1724a@mail.gmail.com>
References: <3c0b01820901251735m4c6a1abfu37a1634818e1724a@mail.gmail.com>
Date: Sun, 25 Jan 2009 21:23:43 -0500
Message-ID: <3c0b01820901251823p5c4536fcy3924d7a1209bfe71@mail.gmail.com>
From: Alexander Sack <pisymbol@gmail.com>
To: freebsd-acpi@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
Subject: Re: Reset register flag versus the actual register
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Mon, 26 Jan 2009 02:23:45 -0000

Whoops!!!  I had a brain fart...

On Sun, Jan 25, 2009 at 8:35 PM, Alexander Sack <pisymbol@gmail.com> wrote:
> Hi Everybody:
>
> I've ran into the quintessential "it works on Linux but does not work
> on FreeBSD" vendor comment regarding the boxes ability to reboot
> successfully.  I'm running FreeBSD-6.1 but this also applies the
> FreeBSD-CURRENT as well.  The problem boils down to the fact that the
> BIOS does set the ResetRegister bit in the FADT feature flags.
> However, I've noticed that latest stable Linux kernel has the
> following logic with respect to the reset register:
>
> acpi_reboot():
>
>  18        /* Is the reset register supported? */
>  19        if (!(acpi_gbl_FADT.flags & ACPI_FADT_RESET_REGISTER) ||
>  20            rr->bit_width != 8 || rr->bit_offset != 0)
>  21                return;

This checks the flag.  I didn't see the NOT for some odd reason.
Uggh, weird, I got to go back and now find out why on Linux uses the
hook and FreeBSD does not.

-aps