Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 27 Aug 2002 02:44:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 27 Aug 2002 02:44:44 -0400 Received: from pizda.ninka.net ([216.101.162.242]:31882 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id ; Tue, 27 Aug 2002 02:44:43 -0400 Date: Mon, 26 Aug 2002 23:43:23 -0700 (PDT) Message-Id: <20020826.234323.39328052.davem@redhat.com> To: andre@linux-ide.org Cc: linux-kernel@vger.kernel.org Subject: Re: readsw/writesw readsl/writesl From: "David S. Miller" In-Reply-To: References: <20020826.231157.10296323.davem@redhat.com> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1059 Lines: 28 From: Andre Hedrick Date: Mon, 26 Aug 2002 23:23:22 -0700 (PDT) Would you consider these for each arch as there are coresponding one for IOMIO, and life would be better if we had a standard set for MMIO. Please consider the request. I responded to the private email I got on this subject. I forget who asked me this, but they said they were working on this IDE stuff. My response was that io_barrier() shall be defined on all platforms in asm/io.h and that you can then define your ide_read{l,w,b} as: __raw_raw{l,w,b}(...); io_barrier(); So instead of having a million read* variations, we have one that is standard usage (little endian + I/O barrier) and then a raw variant where the cpu does nothing special and you have to byte-twiddle and barrier explicitly. - 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/