From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=56223 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OK5EQ-00035b-3W for qemu-devel@nongnu.org; Thu, 03 Jun 2010 03:52:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OK5EO-0000dI-UK for qemu-devel@nongnu.org; Thu, 03 Jun 2010 03:52:49 -0400 Received: from mail.codesourcery.com ([38.113.113.100]:37386) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OK5EO-0000dC-Kx for qemu-devel@nongnu.org; Thu, 03 Jun 2010 03:52:48 -0400 From: Paul Brook Subject: Re: [Qemu-devel] Arm big endian? Date: Thu, 3 Jun 2010 08:52:03 +0100 References: <201005292125.26794.rob@landley.net> In-Reply-To: <201005292125.26794.rob@landley.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201006030852.03792.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org > I'm trying to get arm big endian support to work. I patched the 2.6.33 > kernel to pretend that good old versatilepb can have a big endian CPU > plugged into it (attached), and then I built a kernel with the attached > .config, and qemu went "boing": That's about the result I'd expect. The fact that neither qemu nor linux claim to support big-endian mode for this hardware should be your first clue. > Does this look more like a kernel error, or a qemu error? Probably both. Paul