From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NiuDf-0004Nd-QN for qemu-devel@nongnu.org; Sat, 20 Feb 2010 13:38:23 -0500 Received: from [199.232.76.173] (port=38146 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NiuDe-0004MA-V6 for qemu-devel@nongnu.org; Sat, 20 Feb 2010 13:38:23 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NiuDd-0002bj-3d for qemu-devel@nongnu.org; Sat, 20 Feb 2010 13:38:22 -0500 Received: from [71.162.243.5] (port=55130 helo=grelber.thyrsus.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NiuDc-0002bT-ID for qemu-devel@nongnu.org; Sat, 20 Feb 2010 13:38:20 -0500 From: Rob Landley Date: Sat, 20 Feb 2010 12:38:17 -0600 References: <201002110520.07620.rob@landley.net> <201002201117.41568.rob@landley.net> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201002201238.17811.rob@landley.net> Subject: [Qemu-devel] Re: Fun with sparc (was Re: qemu-ppc can't run static uClibc binaries.) List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: qemu-devel@nongnu.org, Paolo Bonzini , Artyom Tarasenko On Saturday 20 February 2010 11:34:44 Blue Swirl wrote: > On 2/20/10, Rob Landley wrote: > > I don't understand what's going wrong here. Did the kernel break on > > sparc sometime between 2.6.18 and 2.6.32 and nobody noticed? Is sparc > > using software emulated floating point at the kernel level and that's > > configured as a module? (Except I don't think busybox ls uses floating > > point...) > > Sparc32 is not maintained anymore so maybe it broke at some point. > There was some discussion a few years ago. Not maintained on the Linux kernel side, or not maintained under qemu? It seems to be working under debian, but the 2.6.18 kernel is from 2006. > > Do any sparc people understand what's going on here? My next step is to > > grab a 2.6.18 kernel and try to get _that_ to work with the tweaked > > debian config (and an ext2 root filesystem since squashfs wasn't merged > > back then and had a format change when it was merged). But I'm mostly > > flailing around blind here... > > I'm also trying different kernels using my .config. But already 2.6.12 > hangs in ESP probe. I've got 2.6.32 booting to a command prompt (albeit with serial console and intentionall restricted set of hardware). But then it misbehaves. I'll try getting 2.6.18 to build with a known .config, and then bisect forward if that seems to work... Thanks, Rob -- Latency is more important than throughput. It's that simple. - Linus Torvalds