From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nhg9p-0006Bo-Uu for qemu-devel@nongnu.org; Wed, 17 Feb 2010 04:25:21 -0500 Received: from [199.232.76.173] (port=51452 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nhg9o-0006BZ-TX for qemu-devel@nongnu.org; Wed, 17 Feb 2010 04:25:20 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Nhg9o-00068O-2j for qemu-devel@nongnu.org; Wed, 17 Feb 2010 04:25:20 -0500 Received: from mail-pz0-f187.google.com ([209.85.222.187]:64219) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Nhg9n-00068K-Nl for qemu-devel@nongnu.org; Wed, 17 Feb 2010 04:25:19 -0500 Received: by pzk17 with SMTP id 17so6087991pzk.4 for ; Wed, 17 Feb 2010 01:25:18 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <201002161214.31083.rob@landley.net> References: <201002110520.07620.rob@landley.net> <201002151852.59150.rob@landley.net> <201002161214.31083.rob@landley.net> From: Artyom Tarasenko Date: Wed, 17 Feb 2010 10:24:58 +0100 Message-ID: Subject: Re: [Qemu-devel] Re: qemu-ppc can't run static uClibc binaries. Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Rob Landley Cc: qemu-devel@nongnu.org 2010/2/16 Rob Landley : > On Tuesday 16 February 2010 03:31:16 Alexander Graf wrote: >> On 16.02.2010, at 01:52, Rob Landley wrote: >> If swapping the parameter was the right solution I would've submitted a >> patch long ago :-). Unfortunately it's not as easy. > > I agree that making a single controller handle four drives is a _better_ = fix. > (Somebody said that current Linux kernels notice the DMA failure and fall= back > to PIO-ing the drive, or some such. =A0I take it that MacOS doesn't?) > > I just want it fixed, and if that's the direction qemu would prefer to go= on > that issue, I'd like to encourage that in any way I can. =A0I just don' t= know > how... > >> But the inlining is >> really only about simple commenting. It's a lot nicer to have context wh= en >> you say "this doesn't make sense" or so :-). > > Understood. =A0I can do that here in future. > >> Either way - it's good to see someone interested in the topic actually >> sending patches. Reviewing and commenting doesn't mean I don't like what >> you're doing. In this case it just means I'm pretty sure it doesn't solv= e >> the problem, but only the symptoms. > > Thanks. =A0I'm interested, but overwhelmed. > > My FWL project is an attempt to make as many different targets as possibl= e work > the same way, generally under QEMU. =A0This lets me regression test Linux= and > uClibc and busybox and such across all of 'em. =A0(Eventually from a nigh= tly > cron job rebuilding everything from scratch on an 8-way server, with auto= matic > "git bisect" telling me what commit broke it.) > > So far I've got arm, mips, powerpc, and x86/x86-64 building little native > development environments, which can then natively build dropbear and stra= ce > inside qemu (optionally calling out to the cross compiler via distcc). = =A0Each > of those has a working CPU emulation (with mmu) on a board with a network > card, three disks, at least 256 megs of memory, serial console, and clock > chip. > > I've also got a bunch of "sort of working, but not well enough to run bui= lds > natively under" targets on top of that (arm big endian, sh4, sparc...) What's not well enough on sparc? --=20 Regards, Artyom Tarasenko solaris/sparc under qemu blog: http://tyom.blogspot.com/