qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC] Plan for moving forward with QOM


From: Gerd Hoffmann
Subject: Re: [Qemu-devel] [RFC] Plan for moving forward with QOM
Date: Fri, 16 Sep 2011 11:36:27 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.22) Gecko/20110904 Red Hat/3.1.14-1.el6_1 Thunderbird/3.1.14

  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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]