From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id ACBD2DDEC7 for ; Sun, 13 May 2007 11:46:15 +1000 (EST) Subject: Re: [PATCH] powerpc: make ioport_map() handle already mapped ranges From: Benjamin Herrenschmidt To: Arnd Bergmann In-Reply-To: <200705130155.42414.arnd@arndb.de> References: <20070512143221.GB12890@lixom.net> <200705130018.42612.arnd@arndb.de> <20070512223623.GA16045@lixom.net> <200705130155.42414.arnd@arndb.de> Content-Type: text/plain Date: Sun, 13 May 2007 11:46:04 +1000 Message-Id: <1179020764.32247.45.camel@localhost.localdomain> Mime-Version: 1.0 Cc: Olof Johansson , linuxppc-dev@ozlabs.org, paulus@samba.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > There is a global io space range for all buses, which is maintained > by the reserve_phb_iospace() call. You should get your I/O ports in there > if you want them to just work. Note that while the reserve_phb_iospace() > logic works in practice, it does have a few shortcomings that should > eventually be resolved: The solution is to use proper allocators for these. As you pointed out on irc, it seems like the current __get_vm_area() could match our needs. It might allow us to also get rid of imalloc. I'll give that a go tomorrow. Ben.