From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N2oWW-0006E6-5a for qemu-devel@nongnu.org; Tue, 27 Oct 2009 12:03:52 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N2oWR-0006AS-OP for qemu-devel@nongnu.org; Tue, 27 Oct 2009 12:03:51 -0400 Received: from [199.232.76.173] (port=32903 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N2oWR-0006AK-Hs for qemu-devel@nongnu.org; Tue, 27 Oct 2009 12:03:47 -0400 Received: from mail-ew0-f206.google.com ([209.85.219.206]:65395) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N2oWQ-0005Fp-P8 for qemu-devel@nongnu.org; Tue, 27 Oct 2009 12:03:47 -0400 Received: by ewy2 with SMTP id 2so291966ewy.34 for ; Tue, 27 Oct 2009 09:03:41 -0700 (PDT) Sender: Rabin Vincent Date: Tue, 27 Oct 2009 21:33:20 +0530 From: Rabin Vincent Subject: Re: [Qemu-devel] Support for new target emulator Message-ID: <20091027160320.GA5561@debian> References: <0F5F73E36031FD46AD3F2E6948F0C0A001DFDE56@frimb01.corp.atmel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0F5F73E36031FD46AD3F2E6948F0C0A001DFDE56@frimb01.corp.atmel.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Boyapati, Anitha" Cc: qemu-devel@nongnu.org On Fri, Oct 23, 2009 at 12:50:03PM +0200, Boyapati, Anitha wrote: > We have a proposal to add support for AVR32 target emulation in Qemu. I've been working on and off on AVR32 target support for a little while now. It's still far from being complete or mergeable, but enough of the architecture has been implemented to boot a minimal Linux kernel in system emulation and run busybox in linux-user emulation. I've put up the current source at http://repo.or.cz/w/qemu/avr32.git, and a small README and some prebuilt kernel and busybox binaries to play with at http://rab.in/qemu/avr32/. Current status and a TODO list are below. Have a look. I still hope to complete this and get it merged at some point, but you're welcome to beat me to it. If you (or anyone else) decide to work off this, I'd be happy to take patches or give you push access to the repo. Current status: - linux-user: Busybox (ash, ls, gzip, etc) works. - system: Linux kernel (built for ATSTK1000) boots and is able to get a userspace printf("Hello") init process to run. Busybox init doesn't work because fork/exec appears to be broken with the current MMU code. TODO, off the top of my head: - Get fork/exec working under Linux in system mode - Code cleanup (especially remove duplicated code in translate.c) - Make kernel args/atags work (removes need for kernel hack) - Disassembler code integration - Single stepping - GDB support - more devices (atleast framebuffer), sysbus conversion - Implement missing insns (mul variants, packed data insns, saturating arithmetic, various odds & ends) - processor variants support (UC3)? - ... Rabin