From owner-freebsd-sparc64@FreeBSD.ORG Mon Aug 18 11:29:17 2003 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 666EB37B401 for ; Mon, 18 Aug 2003 11:29:13 -0700 (PDT) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A82443FB1 for ; Mon, 18 Aug 2003 11:29:12 -0700 (PDT) (envelope-from tillman@seekingfire.com) Received: from blues.seekingfire.prv (blues.seekingfire.prv [192.168.23.211]) by mail.seekingfire.com (Postfix) with ESMTP id DA8E8C3 for ; Mon, 18 Aug 2003 12:29:11 -0600 (CST) Received: (from tillman@localhost) by blues.seekingfire.prv (8.11.6/8.11.6) id h7IITB729183 for sparc64@freebsd.org; Mon, 18 Aug 2003 12:29:11 -0600 Date: Mon, 18 Aug 2003 12:29:11 -0600 From: Tillman To: FreeBSD-Sparc64 Message-ID: <20030818122911.A29079@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Urban-Legend: There is lots of hidden information in headers Subject: Serial boot console and kernel options (sio vs sab) X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 18:29:17 -0000 Howdy, I currently have a getty listening on COM1 to allow me to login to my Ultra 5 over a null modem cable. I'd like to expand this so that I can also access the boot process over the serial line (in addition to on the normal keyboard/monitor). Following the relevant chapter in the handbook (section 17.6), I find that they talk about the sio serial driver. I used the sab serial driver ... and it doesn't seem to have a man page. Are the same kernel options applicable to sab? For example, can I do something like this in my kernel config file: device sab0 at ebus0 port IO_COM2 flags 0x10 irq 43 ... ? Or is there some otehr process to enable the boot process on COM1 for sparc? My dmesg shows this, by the way: # dmesg | grep sab sab0: addr 0x1400400000-0x140040007f irq 43 on ebus0 sabtty0: on sab0 sabtty1: on sab0 Thanks for any help you can offer, -T -- Certainly the game is rigged. Don't let that stop you; if you don't bet, you can't win. - Robert Heinlein