From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K12Tr-0000iy-2U for qemu-devel@nongnu.org; Tue, 27 May 2008 12:56:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K12Tp-0000gQ-Do for qemu-devel@nongnu.org; Tue, 27 May 2008 12:56:58 -0400 Received: from [199.232.76.173] (port=51225 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K12Tp-0000gE-5C for qemu-devel@nongnu.org; Tue, 27 May 2008 12:56:57 -0400 Received: from lizzard.sbs.de ([194.138.37.39]:19630) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K12Tp-0008Ly-1T for qemu-devel@nongnu.org; Tue, 27 May 2008 12:56:57 -0400 Received: from mail1.sbs.de (localhost [127.0.0.1]) by lizzard.sbs.de (8.12.11.20060308/8.12.11) with ESMTP id m4RGuslI016823 for ; Tue, 27 May 2008 18:56:54 +0200 Received: from [139.25.109.167] (mchn012c.mchp.siemens.de [139.25.109.167] (may be forged)) by mail1.sbs.de (8.12.11.20060308/8.12.11) with ESMTP id m4RGurck013945 for ; Tue, 27 May 2008 18:56:54 +0200 Message-ID: <483C3D55.2000508@siemens.com> Date: Tue, 27 May 2008 18:56:53 +0200 From: Jan Kiszka MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] KQEMU code organization 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 Hi, is there a technical reason why the kqemu kernel module is built out of a binary blob (monitor-image.bin->monitor-image.h)? Does this simply date back to the time when wrapper and core were distributed under different licenses? I'm currently trying to hunt down a (probable) bug in kqemu, and the monitor is now unfortunately a white spot for the source-level debugger. So far I only managed to make the rest visible. BTW, am I missing an official code repository of kqemu? Why is there no subfolder, e.g., in the qemu svn repos? So patches should be provided against 1.3.0pre11, right? Thanks, Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux