From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 5 20:07:43 2005 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BE5116A420; Mon, 5 Dec 2005 20:07:43 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 222D043D62; Mon, 5 Dec 2005 20:07:43 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id jB5K7SfW080249; Mon, 5 Dec 2005 12:07:42 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id jB5K79WK016372; Mon, 5 Dec 2005 12:07:09 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id jB5K79a3016370; Mon, 5 Dec 2005 12:07:09 -0800 (PST) (envelope-from jrhett) Date: Mon, 5 Dec 2005 12:07:09 -0800 From: Joe Rhett To: John Baldwin Message-ID: <20051205200709.GC13194@svcolo.com> References: <20051117050336.GB67653@svcolo.com> <20051117220358.GA65127@svcolo.com> <20051130181757.GA29686@svcolo.com> <200512011153.50287.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512011153.50287.jhb@freebsd.org> Organization: svcolo.com User-Agent: Mutt/1.5.9i Cc: freebsd-hardware@freebsd.org Subject: Re: com1 incorrectly associated with ttyd1, com2 with ttyd0 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 20:07:43 -0000 On Thu, Dec 01, 2005 at 11:53:49AM -0500, John Baldwin wrote: > No, it is reading it right. When you disable a device in ACPI it merely > doesn't assign resources to it. The OS can assign resources to it on its own > though and re-enable the device. FreeBSD currently doesn't implement enough > to get that right though. So what's involved in simply having it say Found : disabled in BIOS instead of half a dozen complaints for each disabled device? -- Joe Rhett senior geek SVcolo : Silicon Valley Colocation