From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GbRS0-0007Ya-Fi for qemu-devel@nongnu.org; Sat, 21 Oct 2006 20:44:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GbRRz-0007VQ-Dp for qemu-devel@nongnu.org; Sat, 21 Oct 2006 20:44:27 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GbRRz-0007V8-8n for qemu-devel@nongnu.org; Sat, 21 Oct 2006 20:44:27 -0400 Received: from [65.74.133.4] (helo=mail.codesourcery.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GbRRz-0007jZ-5a for qemu-devel@nongnu.org; Sat, 21 Oct 2006 20:44:27 -0400 From: Paul Brook Date: Sun, 22 Oct 2006 01:44:21 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610220144.22013.paul@codesourcery.com> Subject: [Qemu-devel] ColdFire/m68k target Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org I've just committed ColdFire/M68K target support to cvs. This implements usermode emulation for ColdFire CPUs, including the FPU. The CPU emulation has been reasonably well tested, but linux syscall emulation only lightly tested. For those that don't know, ColdFire is a subset of the old m68k architecture, with a few minor differences, and a slightly different FPU. I'll probably be implementing full system emulation sometime (Freescale M5xxxEVB dev board). M68k code will not run on the current emulation. Implementing the missing 68k bits (addressing modes and bitfield instructions) probably wouldn't be that hard. Implementing 68881 FPU emulation is a bit harder 'cos it uses "extended" precision registers. The code is a bit different to most other qemu targets because I originally wrote it for my code generation backend rather than dyngen. The main translation code is unmodified, with glue to make it work with dyngen. For this reason the generated code isn't as efficient as it could be. Paul P.S. Anyone wanting to play with ColdFire emulation can find toolchains at http://www.codesourcery.com/gnu_toolchains/coldfire/index_html