From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=42888 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OKK1k-00030G-1y for qemu-devel@nongnu.org; Thu, 03 Jun 2010 19:40:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OKK1f-0000xy-4N for qemu-devel@nongnu.org; Thu, 03 Jun 2010 19:40:43 -0400 Received: from mail-yw0-f197.google.com ([209.85.211.197]:58454) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OKK1f-0000xk-1I for qemu-devel@nongnu.org; Thu, 03 Jun 2010 19:40:39 -0400 Received: by ywh35 with SMTP id 35so587198ywh.29 for ; Thu, 03 Jun 2010 16:40:37 -0700 (PDT) From: Rob Landley Subject: Re: [Qemu-devel] Arm big endian? Date: Thu, 3 Jun 2010 18:25:03 -0500 References: <201005292125.26794.rob@landley.net> <201006030852.03792.paul@codesourcery.com> In-Reply-To: <201006030852.03792.paul@codesourcery.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201006031825.04344.rob@landley.net> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org On Thursday 03 June 2010 02:52:03 Paul Brook wrote: > > 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. Understood. I there a better emulation to try? When you say "this hardware" do you mean the board, or do you mean big endian arm as a CPU? Because there _is_ a qemu-armeb. There isn't a qemu-system- armeb that I'm aware of, but I thought it autodetected endianness at least for the CPU...) If it's the board, I did that because versatilepb has essentially been the generic board emulation I've plugged all the other arm variants into. There isn't a -M ip4xx that I'm aware of. (I can try configuring a kernel with just serial console and see if I can get that to boot, and then add back net and disk and such one at a time, if that might be a reasonable approach...) > > Does this look more like a kernel error, or a qemu error? > > Probably both. If I could just get them to agree, I'd be happy. I just want a setup that can run a big endian arm userspace under system emulation (with network, serial console, clock, and disk). Emulating a feasible board would be a nice bonus, but not actually a goal. > Paul Rob -- Latency is more important than throughput. It's that simple. - Linus Torvalds