From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 19 19:46:30 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 9777F16A41F for ; Mon, 19 Dec 2005 19:46:30 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id F388843D49 for ; Mon, 19 Dec 2005 19:46:28 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 4153088 for multiple; Mon, 19 Dec 2005 14:44:27 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id jBJJkIug068559; Mon, 19 Dec 2005 14:46:18 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Joe Rhett Date: Mon, 19 Dec 2005 14:25:09 -0500 User-Agent: KMail/1.8.2 References: <20051117050336.GB67653@svcolo.com> <200512161125.19927.jhb@freebsd.org> <20051217215133.GA92180@svcolo.com> In-Reply-To: <20051217215133.GA92180@svcolo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512191425.10855.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1213/Mon Dec 19 09:48:34 2005 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 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, 19 Dec 2005 19:46:30 -0000 On Saturday 17 December 2005 04:51 pm, Joe Rhett wrote: > > On Friday 16 December 2005 01:36 am, Joe Rhett wrote: > > > Well, this is where what the BIOS "says" and what the user is led to > > > expect, are different that what you are arguing for. And on top of > > > that, every major OS except for FreeBSD does the right thing (acts like > > > it isn't there) > > > > > > Isn't it fairly obvious that no resources setup for a peripheral means > > > "disabled in BIOS" and it would be best to ignore that resource? > > On Fri, Dec 16, 2005 at 11:25:19AM -0500, John Baldwin wrote: > > No. You would understand that if you had actually read my earlier > > e-mails. > > I did, but out of order of this reply. Sorry. > > > If you set PnP OS to yes, then the BIOS is free to not enable any devices > > not needed for booting. Thus, even if you didn't have COM1 disabled if > > it didn't need COM1 to boot and you had PnP OS set to yes, it could not > > assign any resources to COM1 and require the OS to set the resources. > > There isn't any way for the OS to know if you disabled the device, or if > > you used PnP OS and the BIOS didn't configure that device _even_ _though_ > > _it_ _is_ _enabled_ _in_ _the_ _BIOS_ _setup_ because it didn't feel like > > it. > > Are you saying that changing PNP to "No" would make it easier for FreeBSD? > Are there any disadvantages to this? FreeBSD doesn't support having PnP OS set to Yes actually, it still requires No. We've been getting closer to working with it set to Yes, but I don't think we are all the way there. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org