From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKnY5-0007is-4I for qemu-devel@nongnu.org; Wed, 16 Dec 2009 01:39:49 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKnY2-0007gX-VH for qemu-devel@nongnu.org; Wed, 16 Dec 2009 01:39:48 -0500 Received: from [199.232.76.173] (port=38577 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKnY2-0007gL-Nb for qemu-devel@nongnu.org; Wed, 16 Dec 2009 01:39:46 -0500 Received: from 124x34x33x190.ap124.ftth.ucom.ne.jp ([124.34.33.190]:53945 helo=master.linux-sh.org) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NKnY2-0003LP-7o for qemu-devel@nongnu.org; Wed, 16 Dec 2009 01:39:46 -0500 Date: Wed, 16 Dec 2009 15:13:06 +0900 From: Paul Mundt Subject: Re: [Qemu-devel] [PATCH] experimental sh4 host support V2 Message-ID: <20091216061306.GA32449@linux-sh.org> References: <20091115115355.9126.25624.sendpatchset@rxone.opensource.se> <20091202083658.GV2310@hall.aurel32.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091202083658.GV2310@hall.aurel32.net> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Aurelien Jarno Cc: qemu-devel@nongnu.org On Wed, Dec 02, 2009 at 09:36:58AM +0100, Aurelien Jarno wrote: > On Sun, Nov 15, 2009 at 08:53:55PM +0900, Magnus Damm wrote: > > This is V2 of the QEMU sh4 host support patch. > > > > The code is of a somewhat experimental nature, which means that > > only the bare essentials are in place. The sh4 host support has > > been tested with the sh4 target inside the QEMU sh4 user space > > emulator. Only tiny assembly snippets has been tested so far, but > > at least syscalls and some branches seem ok at this point. Both > > big and little endian hosts are supported, but 64-bit targets and > > softmmu are still on the TODO list. The icache handling needs more > > work as well. > > I have started to review this patch, but I don't know when I'll have > time to finish the review. I'll try to do it before the end of the week. > Any updates on this?