Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 16 Apr 2002 11:33:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 16 Apr 2002 11:33:27 -0400 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:20495 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Tue, 16 Apr 2002 11:33:23 -0400 Date: Tue, 16 Apr 2002 08:30:12 -0700 (PDT) From: Linus Torvalds To: David Lang cc: Martin Dalecki , Vojtech Pavlik , Kernel Mailing List Subject: Re: [PATCH] 2.5.8 IDE 36 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 16 Apr 2002, David Lang wrote: > > It sounds as if you are removing this capability, am I misunderstaning you > or is there some other way to do this? (and duplicating the drive to use > dd to byteswap is not practical for 100G+) Doing it with a loopback like interface at a higher level is the much saner operation - I understand why Martin removed the byteswap support, and agree with it 100%. It just didn't make any sense from a driver standpoint. In fact, the byteswapping was actively incorrect, in that it swapped data in-place - which means that it corrupts the data area while IO is in progress. It also only works for PIO. The only reason byteswapping exists is a rather historical one: Linux did the wrong thing for "insw/outsw" on big-endian architectures at one point (it byteswapped the data). (Oh, and coupled with the fact that the IDE ID string is in a "big-endian" word order, which may have been one more reason to add a "do byteswapped IO" thing). Linus - 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/