From owner-freebsd-current@FreeBSD.ORG Mon Jul 26 09:59:33 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 09E8516A4CE; Mon, 26 Jul 2004 09:59:33 +0000 (GMT) Received: from robbins.dropbear.id.au (085.c.009.mel.iprimus.net.au [210.50.114.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B20D43D2D; Mon, 26 Jul 2004 09:59:32 +0000 (GMT) (envelope-from tim@robbins.dropbear.id.au) Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id A71AD4207; Mon, 26 Jul 2004 19:59:29 +1000 (EST) Date: Mon, 26 Jul 2004 19:59:29 +1000 From: Tim Robbins To: njl@freebsd.org Message-ID: <20040726095929.GA30092@cat.robbins.dropbear.id.au> References: <20040726021326.GA23697@cat.robbins.dropbear.id.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040726021326.GA23697@cat.robbins.dropbear.id.au> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: Floppy disk drive no longer detected 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: Mon, 26 Jul 2004 09:59:33 -0000 On Mon, Jul 26, 2004 at 12:13:26PM +1000, Tim Robbins wrote: > My floppy disk drive is no longer probed correctly by -CURRENT. I get the > following message, but none about fd0 (and /dev/fd0 does not exist): > > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 > > Previously it probed as: > > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > > The ACPI DSDT for this system is available at: > http://people.freebsd.org/~tjr/k8v.txt.bz2 Ok, it looks like the FDC device should have a child device for each drive, but my system's DSDT has none. Could we work around this in the driver by not using _FDE/_FDI to probe unless the FDC device has at least 1 child with an _FDI object, or should we add an entry to the quirks table for this particular BIOS instead? Tim