From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:33996)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1R4UqZ-0002MV-TD
	for qemu-devel@nongnu.org; Fri, 16 Sep 2011 05:36:36 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1R4UqZ-00058T-49
	for qemu-devel@nongnu.org; Fri, 16 Sep 2011 05:36:35 -0400
Received: from mx1.redhat.com ([209.132.183.28]:17345)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1R4UqY-00058D-7W
	for qemu-devel@nongnu.org; Fri, 16 Sep 2011 05:36:34 -0400
Message-ID: <4E73189B.6050205@redhat.com>
Date: Fri, 16 Sep 2011 11:36:27 +0200
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
References: <4E70EC90.8000904@us.ibm.com> <4E719F7C.10700@redhat.com>
	<4E71FD19.6050606@codemonkey.ws> <4E725EC9.6060506@redhat.com>
In-Reply-To: <4E725EC9.6060506@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC] Plan for moving forward with QOM
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Avi Kivity <avi@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, Jan Kiszka <jan.kiszka@siemens.com>, Markus Armbruster <armbru@redhat.com>, qemu-devel <qemu-devel@nongnu.org>, "Edgar E. Iglesias" <edgar.iglesias@gmail.com>, Paolo Bonzini <pbonzini@redhat.com>

   Hi,

> Also, NE2000 methods have to call ISA_NE2000 and PCI_NE2000 methods,
> yes? That's going to be more difficult. Not impossible, just hard. It's
> probably going to involve device specific code that models what type of
> glue was used for that particular device/bus combo.

I'd expect our new, shiny memory api should help here.  I think the 
difference between pci and isa ne2k is just how the registers are mapped 
and how the IRQ is linked up.  At least the registers are easy to 
handle: ne2k core just creates a mmio memory region, then isa-ne2k and 
pci-ne2k just map the memory region in different ways and any register 
access goes directly to the ne2k core code.

cheers,
   Gerd