From owner-freebsd-current@FreeBSD.ORG Tue Apr 13 22:23:24 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 5D5D816A4CE for ; Tue, 13 Apr 2004 22:23:24 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECE0843D31 for ; Tue, 13 Apr 2004 22:23:23 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.10/8.12.9) with ESMTP id i3E5NHkj017131; Tue, 13 Apr 2004 23:23:18 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 13 Apr 2004 23:24:10 -0600 (MDT) Message-Id: <20040413.232410.119139280.imp@bsdimp.com> To: ler@lerctr.org From: "M. Warner Losh" In-Reply-To: <18990000.1081795882@lerlaptop.lerctr.org> References: <7220000.1081793116@lerlaptop.lerctr.org> <20040412.123733.101437212.imp@bsdimp.com> <18990000.1081795882@lerlaptop.lerctr.org> 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: current@freebsd.org Subject: Re: HEADS UP: PCI Chnages 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: Wed, 14 Apr 2004 05:23:24 -0000 OK. I've recreated 'a' fdc problem here. My fdc doesn't normally attach anyway, so I'm not sure what the problem really is. I'd not expect a failure mode like this, but I'll look into it. Hmmm, I wonder if it is due to the fact that we really are allocating 0x3f4 to 0x3ff non-sharable and the floppy wants to be at 0x3f0-0x3f5,0x3f7. I'll bet that it is the problem... The 1 port (is likely 0x3f7) is in the ata range now allocated as is the 6 port range. Yes. now that I think about it more, the more I'm sure that's what's going on. The old ata code tried to allocate just one byte. If you are feeling brave (my brain is not engaged and I'm getting ready for bed), you could make the allocation of the ALTADDR rid in ata RF_SHAREABLE, as well as the resource allocation in the fdc driver... Hmmm, I'm not sure that would even work because the pci bus is the one doing the allocation with the rman, but it is worth a shot. Warner