From owner-freebsd-amd64@FreeBSD.ORG Thu Oct 23 00:24:43 2008 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BA901065672; Thu, 23 Oct 2008 00:24:43 +0000 (UTC) (envelope-from neldredge@math.ucsd.edu) Received: from euclid.ucsd.edu (euclid.ucsd.edu [132.239.145.52]) by mx1.freebsd.org (Postfix) with ESMTP id E8A4F8FC14; Thu, 23 Oct 2008 00:24:42 +0000 (UTC) (envelope-from neldredge@math.ucsd.edu) Received: from zeno.ucsd.edu (zeno.ucsd.edu [132.239.145.22]) by euclid.ucsd.edu (8.11.7p3+Sun/8.11.7) with ESMTP id m9N0Oe601954; Wed, 22 Oct 2008 17:24:40 -0700 (PDT) Received: from localhost (neldredg@localhost) by zeno.ucsd.edu (8.11.7p3+Sun/8.11.7) with ESMTP id m9N0OeX06794; Wed, 22 Oct 2008 17:24:40 -0700 (PDT) X-Authentication-Warning: zeno.ucsd.edu: neldredg owned process doing -bs Date: Wed, 22 Oct 2008 17:24:39 -0700 (PDT) From: Nate Eldredge X-X-Sender: neldredg@zeno.ucsd.edu To: Jung-uk Kim In-Reply-To: <200810221944.13406.jkim@FreeBSD.org> Message-ID: References: <1224616985.00027652.1224606603@10.7.7.3> <48FF9925.4090007@FreeBSD.org> <48FF9AFA.3030201@root.org> <200810221944.13406.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-acpi@freebsd.org, Alexander Motin , freebsd-amd64@freebsd.org, Nate Lawson Subject: Re: Semi-working patch for amd64 suspend/resume X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Oct 2008 00:24:43 -0000 On Wed, 22 Oct 2008, Jung-uk Kim wrote: > The port 0x80 is usually used for BIOS debugging. > > http://www.coreboot.org/FAQ#POST_card > > Probably BIOS developer forgot to comment out the lines. :-) Or it's been left in as a diagnostic tool. My motherboard has a built-in LED display wired up to port 0x80, and it flashes various numbers as it passes different stages of booting. Useful for detecting various types of failure, nicer than the beep codes. It can also be handy for kernel debugging, when you can't use printf. A very thoughtful feature on the motherboard designer's part. Btw, I'm interested to test the patch, and I'll do so when I have a chance. This is a feature I've been awaiting for some time. -- Nate Eldredge neldredge@math.ucsd.edu