From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:35369) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SX0vA-0006cy-5C for qemu-devel@nongnu.org; Tue, 22 May 2012 22:03:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SX0v8-0004UI-3n for qemu-devel@nongnu.org; Tue, 22 May 2012 22:03:27 -0400 Received: from shell4.bayarea.net ([209.128.82.1]:38709) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SX0v7-0004Sn-QI for qemu-devel@nongnu.org; Tue, 22 May 2012 22:03:26 -0400 Message-ID: <4FBC4563.60909@eagerm.com> Date: Tue, 22 May 2012 19:03:15 -0700 From: Michael Eager MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] How to create new target port? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi All -- I'm investigating adding a new target architecture to QEMU. Are there documents, how-to's, or other guidance on how to approach this? Or any advice? I noticed that there are a number of directories for architectures like target-arm and target-mips. There are also definitions under tcg for arm and mips. I noticed that target-microblaze exists, but there is no microblaze directory under tcg. What does this mean? -- Michael Eager eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077