From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1K12qr-0005dD-CG
	for qemu-devel@nongnu.org; Tue, 27 May 2008 13:20:45 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1K12qp-0005ak-Si
	for qemu-devel@nongnu.org; Tue, 27 May 2008 13:20:45 -0400
Received: from [199.232.76.173] (port=55502 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1K12qp-0005aa-Ox
	for qemu-devel@nongnu.org; Tue, 27 May 2008 13:20:43 -0400
Received: from wa-out-1112.google.com ([209.85.146.179]:43533)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <bentaylor.solx86@gmail.com>) id 1K12qp-0004gN-FY
	for qemu-devel@nongnu.org; Tue, 27 May 2008 13:20:43 -0400
Received: by wa-out-1112.google.com with SMTP id j5so3129637wah.18
	for <qemu-devel@nongnu.org>; Tue, 27 May 2008 10:20:37 -0700 (PDT)
Message-ID: <cef699d70805271020wd6633d5v7323ccb5fc7b6f4@mail.gmail.com>
Date: Tue, 27 May 2008 13:20:37 -0400
From: "Ben Taylor" <bentaylor.solx86@gmail.com>
Subject: Re: [Qemu-devel] KQEMU code organization
In-Reply-To: <483C3D55.2000508@siemens.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <483C3D55.2000508@siemens.com>
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

On Tue, May 27, 2008 at 12:56 PM, Jan Kiszka <jan.kiszka@siemens.com> 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?

I maintain a version of the repository at

http://svn9.cvsdude.com/kdesolaris/kqemu/trunk/1.0.3pre11/kqemu

that includes the Solaris changes and other patches posted to the
list that I've been able to test and integrate.

despite the kqemu being under kdesolaris (my friend owns this tree),
this is kqemu the kernel module, not kqemu the KDE qemu front end. :-)

ben