From owner-freebsd-current@FreeBSD.ORG Tue Sep 21 20:36:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8326716A4CE for ; Tue, 21 Sep 2004 20:36:41 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB75543D3F for ; Tue, 21 Sep 2004 20:36:40 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id i8LKYjXf084551; Tue, 21 Sep 2004 14:34:46 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 21 Sep 2004 14:35:46 -0600 (MDT) Message-Id: <20040921.143546.63053469.imp@bsdimp.com> To: rosti_bsd@yahoo.com From: "M. Warner Losh" In-Reply-To: <20040921122354.73480.qmail@web14827.mail.yahoo.com> References: <20040921122354.73480.qmail@web14827.mail.yahoo.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: new fdc(4) and new fdcontrol(8) behavior (5.3-BETA5) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 20:36:41 -0000 In message: <20040921122354.73480.qmail@web14827.mail.yahoo.com> Rostislav Krasny writes: : Why the 3F7h port isn't used by new fdc(4) on my system? Is it a : hardware detection bug? It is a minor, hardware detection bug. Your bios doesn't list it as a resource, but should. We do use it, but we don't allocate it with the bus system, which is why it doesn't appear in dmesg. A mostly-harmless cosmetic issue. Warner