From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 1 12:13:55 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5015937B401 for ; Tue, 1 Apr 2003 12:13:55 -0800 (PST) Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F32D43FAF for ; Tue, 1 Apr 2003 12:13:54 -0800 (PST) (envelope-from nate@yogotech.com) Received: from emerger.yogotech.com (emerger.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3p2/8.9.3) with ESMTP id NAA10058; Tue, 1 Apr 2003 13:13:44 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by emerger.yogotech.com (8.12.8/8.12.8) id h31KDaEV027067; Tue, 1 Apr 2003 13:13:36 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16009.62192.552107.137267@emerger.yogotech.com> Date: Tue, 1 Apr 2003 13:13:36 -0700 To: des@ofug.org (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) In-Reply-To: References: <20030330.191944.62348635.imp@bsdimp.com> <20030331.091739.08149174.imp@bsdimp.com> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid cc: freebsd-hackers@freebsd.org cc: dgilbert@velocet.ca Subject: Re: [hackers] Re: Realtek X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nate Williams List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Apr 2003 20:13:55 -0000 > > An address that works. Without further knowledge of your laptop, it > > is impossible for me to say. You will have to find this out by trial > > and error. Some folks like 0xf8000000, others like 0x400000000 and > > one uses 0xd4000, but the last one I don't recommend. > > 0xf8000000 seems to work on my StinkPad (still can't get the serial > port to work though). You have to enable it using the PS2 'DOS' command (the Windows one won't work, for whatever reason). Once it's probably enabled/configured, it acts like any other normal serial port. (It's a pain to get it working right, since it involves dozens of reboots in order to understand what exactly the configuration *should* be. From memory, it wasn't as obvious as it could have been.) Nate