From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1K16GJ-0003Qq-Ai
	for qemu-devel@nongnu.org; Tue, 27 May 2008 16:59:15 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1K16GH-0003QW-Ny
	for qemu-devel@nongnu.org; Tue, 27 May 2008 16:59:15 -0400
Received: from [199.232.76.173] (port=43735 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1K16GH-0003QT-IU
	for qemu-devel@nongnu.org; Tue, 27 May 2008 16:59:13 -0400
Received: from relay3-v.mail.gandi.net ([217.70.178.77]:43990)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <fabrice@bellard.org>) id 1K16GH-0001J9-2f
	for qemu-devel@nongnu.org; Tue, 27 May 2008 16:59:13 -0400
Message-ID: <483C75DF.1050603@bellard.org>
Date: Tue, 27 May 2008 22:58:07 +0200
From: Fabrice Bellard <fabrice@bellard.org>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] KQEMU code organization
References: <483C3D55.2000508@siemens.com>
In-Reply-To: <483C3D55.2000508@siemens.com>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: jan.kiszka@siemens.com

Hi,

Regarding kqemu, I am still hesitating whether to commit it in the QEMU
subversion repository. Moreover, I may change its license to another
open source one so I would prefer that the patches are assigned to my
copyright, especially if they are just small bugfixes.

For your information, I will commit some incompatible API changes in
kqemu in the next few days, so a new version will be needed anyway.

Regards,

Fabrice.

Jan Kiszka wrote:
> 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
>