From owner-freebsd-current@FreeBSD.ORG Sun Mar 13 01:48:55 2005 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 413D716A4CE; Sun, 13 Mar 2005 01:48:55 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 909EB43D1D; Sun, 13 Mar 2005 01:48:54 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.3/8.13.1) with ESMTP id j2D1mbjG030717; Sat, 12 Mar 2005 18:48:37 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 12 Mar 2005 18:48:52 -0700 (MST) Message-Id: <20050312.184852.104039702.imp@bsdimp.com> To: bzeeb-lists@lists.zabbadoz.net From: "M. Warner Losh" In-Reply-To: References: <20050312.183415.102615682.imp@bsdimp.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: rwatson@FreeBSD.org cc: current@FreeBSD.org Subject: Re: sio0 probing broken with fdc change? 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: Sun, 13 Mar 2005 01:48:55 -0000 In message: "Bjoern A. Zeeb" writes: : On Sat, 12 Mar 2005, M. Warner Losh wrote: : : Hi, : : > In message: : > Robert Watson writes: : > : ... : > : fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 : > : fdc0: [FAST] : > : fd0: <1440-KB 3.5" drive> on fdc0 drive 0 : > : ... : > : : > : After: : > : : > : ... : > : fdc1: Faking up FDCTL : > : > This means you are using hints to get your floppy recognized. This : > likely is an error that we've silently lived with for too long. I : > hadn't anticipated that my change would break anything here. : > : > : fdc1: at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 : > : on isa0 : > : fdc1: Faking up FDCTL : > : fdc1: [FAST] : > : > I don't see how a change in the floppy driver could break probing : > serial ports. Can you provide at least a theory of the crime for me : > to investigate? Otherwise, it makes absolutely no sense at all. It : > works for me, so you'll need to track down what it is doing : > differently. : : what makes me wonder is that it is fdc_1_. Yea. It may be that allocating only 1 port gives only 1 port in the simple ISA hints case, which is causing problems downstream. However, even if that were the case, since we've been able to allocate the ports for fdc1, fdc1 should just work. Warner