From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39870) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RkkVX-00081o-DE for qemu-devel@nongnu.org; Tue, 10 Jan 2012 17:49:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RkkVW-00014Y-Ep for qemu-devel@nongnu.org; Tue, 10 Jan 2012 17:49:31 -0500 Received: from gate.crashing.org ([63.228.1.57]:44025) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RkkVW-0000yz-6L for qemu-devel@nongnu.org; Tue, 10 Jan 2012 17:49:30 -0500 Message-ID: <1326235758.23910.75.camel@pasglop> From: Benjamin Herrenschmidt Date: Wed, 11 Jan 2012 09:49:18 +1100 In-Reply-To: <485923AD-E235-4412-9B60-2E0736FB74D1@suse.de> References: <1326195311.23910.59.camel@pasglop> <4F0CB585.2000206@codemonkey.ws> <485923AD-E235-4412-9B60-2E0736FB74D1@suse.de> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] virtio-pci: Fix endianness of virtio config List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: kvm-ppc@vger.kernel.org, David Gibson , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" On Tue, 2012-01-10 at 23:41 +0100, Alexander Graf wrote: > > No. Libhw shouldn't be able to know anything about target endianness. > If a device is as brokenly spec'ed as virtio and is coupled to the > "main CPU endianness", it clearly belongs with the CPU, not into > libhw. Ok, can you guys solve this and tell me what I should do ? :-) Cheers, Ben.