From owner-freebsd-i386@FreeBSD.ORG Thu Aug 3 22:20:16 2006 Return-Path: X-Original-To: freebsd-i386@hub.freebsd.org Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB87F16A4DD for ; Thu, 3 Aug 2006 22:20:16 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50DE143D58 for ; Thu, 3 Aug 2006 22:20:16 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k73MKGYE033946 for ; Thu, 3 Aug 2006 22:20:16 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k73MKGGG033945; Thu, 3 Aug 2006 22:20:16 GMT (envelope-from gnats) Date: Thu, 3 Aug 2006 22:20:16 GMT Message-Id: <200608032220.k73MKGGG033945@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: Marcel Moolenaar Cc: Subject: Re: i386/100831: sio ignores BIOS information about serial ports - bounty offered X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marcel Moolenaar List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Aug 2006 22:20:16 -0000 The following reply was made to PR i386/100831; it has been noted by GNATS. From: Marcel Moolenaar To: Warner Losh Cc: nate@root.org, jrhett@svcolo.com, freebsd-gnats-submit@freebsd.org, freebsd-i386@freebsd.org Subject: Re: i386/100831: sio ignores BIOS information about serial ports - bounty offered Date: Thu, 3 Aug 2006 15:16:22 -0700 On Aug 3, 2006, at 2:28 PM, Warner Losh wrote: > Agreed. However, the sio flags to designate a unit as console is the > only thing that doesn't fit well with hints, as presently implemented. > It should really be something like: console.type={serial,video} > console.location= > > so that would could use a video card not mapped to the default address > as the console, etc. It would be up to the driver at attach time to > look at the available console meta-information to see if this driver > matches that information. Then it wouldn't matter for a serial > console point of view what driver unit is assigned. It might matter > for other reasons... This is exactly what I implemented for uart(4). As long as the I/O location used by the low-level console is actually being "found" during bus-enumeration and the right driver is being attached, then you always have a working console for going to single-user mode. Not to mention that the firmware typically exports console information in terms of I/O location (see DIG64 HCDP or Microsoft SPCR), so you can trivially use that too (see for a real example src/sys/dev/uart/uart_cpu_ia64.c). -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net