Date: Mon, 26 Jan 2004 17:23:46 -0800 (PST) From: Nate Lawson <nate@root.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: arch@freebsd.org Subject: Re: newbus ioport usage Message-ID: <20040126172211.J30603@root.org> In-Reply-To: <20040126.181720.15264443.imp@bsdimp.com> References: <20040126140100.T29680@root.org> <20040126.151728.133912536.imp@bsdimp.com> <20040126.181720.15264443.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 26 Jan 2004, M. Warner Losh wrote: > In message: <20040126165523.W30461@root.org> > Nate Lawson <nate@root.org> 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. -Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040126172211.J30603>