Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 29 Aug 2002 05:36:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 29 Aug 2002 05:36:30 -0400 Received: from faui02.informatik.uni-erlangen.de ([131.188.30.102]:28578 "EHLO faui02.informatik.uni-erlangen.de") by vger.kernel.org with ESMTP id ; Thu, 29 Aug 2002 05:36:30 -0400 Date: Thu, 29 Aug 2002 11:17:44 +0200 From: Richard Zidlicky To: Benjamin Herrenschmidt Cc: davem@redhat.com, linux-kernel@vger.kernel.org Subject: Re: readsw/writesw readsl/writesl Message-ID: <20020829111744.A223@linux-m68k.org> References: <20020828142356.B4464@linux-m68k.org> <20020828161701.22623@192.168.4.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020828161701.22623@192.168.4.1>; from benh@kernel.crashing.org on Wed, Aug 28, 2002 at 06:17:01PM +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 984 Lines: 22 On Wed, Aug 28, 2002 at 06:17:01PM +0200, Benjamin Herrenschmidt wrote: > Another possibility (that looks saner to me) would be to define that > the IO macros take all a parameter which represents the bus (or rather > the device pointer in the new driver model). Most archs would just > ignore that macro parameter and so have exactly equivalent code as > we have today, but that let archs that feel they need it to actually > use that to go pick the proper access methods for that device. that would certainly solve all problems. > In all cases, though, I would keep the distinction between {read,write}* > and {in,out}* as there are PCI drivers that will need to mix them. sure, it makes a difference even on m68k ISA buses. Richard - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/