From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K6TVq-0006wQ-GB for qemu-devel@nongnu.org; Wed, 11 Jun 2008 12:49:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K6TVo-0006uS-Pe for qemu-devel@nongnu.org; Wed, 11 Jun 2008 12:49:29 -0400 Received: from [199.232.76.173] (port=59978 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6TVo-0006tz-9t for qemu-devel@nongnu.org; Wed, 11 Jun 2008 12:49:28 -0400 Received: from 131.221.64-86.rev.gaoland.net ([86.64.221.131]:59839 helo=athena.purplelabs.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K6TVn-0001uv-Jm for qemu-devel@nongnu.org; Wed, 11 Jun 2008 12:49:27 -0400 Received: from localhost (localhost [127.0.0.1]) by athena.purplelabs.com (Postfix) with ESMTP id AE15E653D0 for ; Wed, 11 Jun 2008 17:58:50 +0200 (CEST) Received: from athena.purplelabs.com ([127.0.0.1]) by localhost (athena.purplelabs.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wPm5kXpUm-JA for ; Wed, 11 Jun 2008 17:58:48 +0200 (CEST) Received: from [10.1.2.49] (drivers_tba_lin.purplelabs.com [10.1.2.49]) by athena.purplelabs.com (Postfix) with ESMTP id 4BF6163281 for ; Wed, 11 Jun 2008 17:58:48 +0200 (CEST) Message-ID: <484FF638.2080905@purplelabs.com> Date: Wed, 11 Jun 2008 17:58:48 +0200 From: Thomas Bandelier MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Adding new ARM9-based platform in Qemu Reply-To: thomas.bandelier@purplelabs.com, 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 Hi, I'm facing several difficulties to implement such a platform support in Qemu. Concretely, all is about adding a new mobile-phone baseband processor emulation in hw directory. Inspiration from "integratorcp" and other machines is not enough for a QEMU-beginner like me... So 2 questions: -> Does kind of "development guidelines" documentation exist ? -> Maybe someone on this list has already accomplished such a task ? - In this case, please answer in private. Thanks in advance, Thomas