On Tue, Jul 19, 2011 at 14:41, Juan Quintela quint...@redhat.com wrote:
Anthony PERARD anthony.per...@citrix.com wrote:
This patch introduces the two IOPorts on e1000, IOADDR and IODATA. The
IOADDR is used to specify which register we want to access when we read
or write on IODATA.
This
Anthony PERARD anthony.per...@citrix.com wrote:
This patch introduces the two IOPorts on e1000, IOADDR and IODATA. The
IOADDR is used to specify which register we want to access when we read
or write on IODATA.
This patch fixes some weird behavior that I see when I use e1000 with
QEMU/Xen,
On Sat, Jul 2, 2011 at 18:35, Andreas Färber andreas.faer...@web.de wrote:
Am 30.06.2011 um 23:35 schrieb Anthony PERARD:
This patch introduces the two IOPorts on e1000, IOADDR and IODATA. The
IOADDR is used to specify which register we want to access when we read
or write on IODATA.
This
Am 30.06.2011 um 23:35 schrieb Anthony PERARD:
This patch introduces the two IOPorts on e1000, IOADDR and IODATA. The
IOADDR is used to specify which register we want to access when we
read
or write on IODATA.
This patch fixes some weird behavior that I see when I use e1000 with
QEMU/Xen,
This patch introduces the two IOPorts on e1000, IOADDR and IODATA. The
IOADDR is used to specify which register we want to access when we read
or write on IODATA.
This patch fixes some weird behavior that I see when I use e1000 with
QEMU/Xen, the guest memory can be corrupted by this NIC because