From owner-freebsd-current@FreeBSD.ORG Tue Aug 24 13:22:42 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 89E9B16A4CE for ; Tue, 24 Aug 2004 13:22:42 +0000 (GMT) Received: from encontacto.net (dsl-200-95-35-64.prod-infinitum.com.mx [200.95.35.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id E158543D48 for ; Tue, 24 Aug 2004 13:22:41 +0000 (GMT) (envelope-from eculp@encontacto.net) Received: from localhost (localhost [127.0.0.1]) (uid 80) by encontacto.net with local; Tue, 24 Aug 2004 08:22:41 -0500 Received: from dsl-200-95-35-64.prod-infinitum.com.mx (dsl-200-95-35-64.prod-infinitum.com.mx [200.95.35.64]) by mail.encontacto.net (Horde) with HTTP for ; Tue, 24 Aug 2004 08:22:41 -0500 Message-ID: <20040824082241.ogsskc4g4g0ockk8@mail.encontacto.net> Date: Tue, 24 Aug 2004 08:22:41 -0500 From: Edwin Culp To: current@freebsd.org References: <20040822062942.jdgc48ksoo8c8kk0@mail.encontacto.net> <20040822194550.L94593@carver.gumbysoft.com> <20040822.213112.116247523.imp@bsdimp.com> In-Reply-To: <20040822.213112.116247523.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Originating-IP: 200.95.35.64 Subject: Re: Problems with fdc0 w/Athlon and via chipset. Floppy isn't recognized. 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, 24 Aug 2004 13:22:42 -0000 Quoting "M. Warner Losh" : > In message: <20040822194550.L94593@carver.gumbysoft.com> > Doug White writes: > : On Sun, 22 Aug 2004, Edwin Culp wrote: > : Your BIOS writer is on crack. I think Nate was working on a hack to glue > : the ranges together to work around this. > > Actually, Nate's hack doesn't glue things together like this. I have > a preliminary patch ready for this problem before phk committed the > rewrite of fdc, which I need to merge into the current fdc. > > Warner Thanks, Warner. I can confirm that with today's cvsup and build and with my BIOS writer on crack:), I'm still seeing the same: fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 Thanks again, ed