From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:493 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id S268326AbUIPXad (ORCPT ); Thu, 16 Sep 2004 19:30:33 -0400 Message-ID: <414A220B.5040600@pobox.com> Date: Thu, 16 Sep 2004 19:30:19 -0400 From: Jeff Garzik MIME-Version: 1.0 Subject: Re: RFC: being more anal about iospace accesses.. References: <1095287935.1688.4.camel@mulgrave> <20040916023325.GJ642@parcelfarce.linux.theplanet.co.uk> <20040916223042.GO642@parcelfarce.linux.theplanet.co.uk> <414A17C0.9000309@pobox.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit To: Linus Torvalds Cc: Matthew Wilcox , James Bottomley , Geert Uytterhoeven , Linux Arch list , Al Viro , Andrew Morton , Alan Cox , "David S. Miller" List-ID: Linus Torvalds wrote: It doesn't have good semantics, though. For example, would your code work > if the copy was byte-by-byte? Word-for-word? Long-for-long? It might work > on some hardware, but it's not an operation that makes sense "in general". That's actually a good point. Looking at the code, /* TODO: we are too slack to do reg dumping for pio, for now */ #ifdef CONFIG_8139TOO_PIO #define rtl8139_get_regs_len NULL #define rtl8139_get_regs NULL I seem to recall that I didn't implement it precisely because some registers wanted to read only at certain bit widths. Jeff