From owner-freebsd-arch@FreeBSD.ORG Mon Jan 26 17:35:41 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF06216A4CE for ; Mon, 26 Jan 2004 17:35:41 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8575F43D9D for ; Mon, 26 Jan 2004 17:34:08 -0800 (PST) (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 i0R1WMET084762; Mon, 26 Jan 2004 18:32:22 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 26 Jan 2004 18:32:15 -0700 (MST) Message-Id: <20040126.183215.26531948.imp@bsdimp.com> To: nate@root.org From: "M. Warner Losh" In-Reply-To: <20040126172211.J30603@root.org> References: <20040126165523.W30461@root.org> <20040126.181720.15264443.imp@bsdimp.com> <20040126172211.J30603@root.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: arch@freebsd.org Subject: Re: newbus ioport usage X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2004 01:35:41 -0000 In message: <20040126172211.J30603@root.org> Nate Lawson writes: : On Mon, 26 Jan 2004, M. Warner Losh wrote: : > In message: <20040126165523.W30461@root.org> : > Nate Lawson writes: : > : Ok, I'm doing the set/alloc and it works. However, one weird thing. If I : > : allocate all ports at boot time, it succeeds. My driver goes through : > : multiple release/allocate cycles and it all works as expected. However if : > : I boot and attach to only one of the registers, subsequent attempts to : > : attach the second one fail. The resources are 2 IO ports, 0x101c and : > : 0x101d. Both are 1 byte. : > : > Deos devinfo -r show any cause for the problem? Maybe you aren't : > releasing them properly? Also, why not allocate them as a block of 2? : : I'll look into that. I can't allocate them in one block as they come and : go, based on system state. In one state, one is available and in another, : both are available. If I boot while only one is available and then you : plug in the AC adapter, new ones appear. This is acpi, btw. Ummm, wouldn't they both always be allocated to the driver, even if you could only talk to one of them at any given time? Warner