Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 4 Jan 2002 12:15:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 4 Jan 2002 12:15:33 -0500 Received: from opal.biophys.uni-duesseldorf.de ([134.99.176.7]:35044 "EHLO opal.biophys.uni-duesseldorf.de") by vger.kernel.org with ESMTP id ; Fri, 4 Jan 2002 12:15:25 -0500 Date: Fri, 4 Jan 2002 18:15:01 +0100 (CET) From: Michael Schmitz To: Geert Uytterhoeven cc: Alan Cox , Manfred Spraul , Linux Kernel Development , Linux/m68k Subject: Re: Who uses hdx=bswap or hdx=swapdata? 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 > > For 2.5 would it perhaps be cleaner if we had a bswapping loop device. Sort > > of very bad crypto mode ? > > Don't mention crypto, or Atari will come after us with the DMCA sword, claiming > they deliberately implemented access control? ;-) Caution - I recall that on some m68k boxes we had to further byteswap specific parts of the identify data or they wouldn't make sense. The IDE driver will still have to be aware of these exceptions. I can't recall the particulars anymore - Geert? Since hdx=swapdata only works on disks replacing this with a byteswapping loop device sounds fine (loopback being used for anything kernel-internally now :-) Michael - 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/