From owner-freebsd-current@FreeBSD.ORG Sat Feb 9 01:20:10 2008 Return-Path: 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 6E60216A41B for ; Sat, 9 Feb 2008 01:20:10 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 50BFF13C4E9 for ; Sat, 9 Feb 2008 01:20:10 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id m191K2uS041107; Fri, 8 Feb 2008 17:20:02 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.1/8.14.1/Submit) id m191K2lW041106; Fri, 8 Feb 2008 17:20:02 -0800 (PST) (envelope-from obrien) Date: Fri, 8 Feb 2008 17:20:02 -0800 From: "David O'Brien" To: cpghost Message-ID: <20080209012002.GC30493@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, cpghost , freebsd-current@freebsd.org References: <20080208185405.GA1479@roadrunner.spoerlein.net> <47ACAE62.2060706@FreeBSD.org> <47ACB7BB.7090305@samsco.org> <20080209002918.GA85693@epia-2.farid-hajji.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080209002918.GA85693@epia-2.farid-hajji.net> X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: boot0sio working for anyone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2008 01:20:10 -0000 On Fri, Feb 08, 2008 at 05:29:18PM -0700, cpghost wrote: > Yes, but the other way around is possible with a little help from a > patched or more capable BIOS. Such a BIOS could intercept the "display > character" (int $0x10, ah=0xe), "check for keypress" (int 0x16, ah=0x1), > and "get keypress" (int 0x16, ah=0x0) BIOS calls and reroute them to > or from the serial interface. > > With such a BIOS, /boot/boot0 would run just fine, because the > bootloader would be oblivious to this rerouting. > > Isn't it the approach taken by Soekris devices? These boxes have no This is the approach taken by [most] server motherboards which offer a serial console setting. I don't use boot0sio on my MP Opteron systems. -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? Let's not play "Jeopardy-style quoting"