From: Jason Wang <jasowang@redhat.com>
To: qemu-devel@nongnu.org, peter.maydell@linaro.org
Cc: Mike Nawrocki <michael.nawrocki@gtri.gatech.edu>,
Jason Wang <jasowang@redhat.com>
Subject: [Qemu-devel] [PULL 6/8] Fix eepro100 simple transmission mode
Date: Tue, 14 Nov 2017 10:11:36 +0800 [thread overview]
Message-ID: <1510625498-4821-7-git-send-email-jasowang@redhat.com> (raw)
In-Reply-To: <1510625498-4821-1-git-send-email-jasowang@redhat.com>
From: Mike Nawrocki <michael.nawrocki@gtri.gatech.edu>
The simple transmission mode was treating the area immediately after the
transmit command block (TCB) as if it were a transmit buffer descriptor,
when in reality it is simply the packet data. This change simply copies
the data following the TCB into the packet buffer.
Signed-off-by: Mike Nawrocki <michael.nawrocki@gtri.gatech.edu>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
---
hw/net/eepro100.c | 18 +++---------------
1 file changed, 3 insertions(+), 15 deletions(-)
diff --git a/hw/net/eepro100.c b/hw/net/eepro100.c
index 80b8f47..91dd058 100644
--- a/hw/net/eepro100.c
+++ b/hw/net/eepro100.c
@@ -774,23 +774,11 @@ static void tx_command(EEPRO100State *s)
}
assert(tcb_bytes <= sizeof(buf));
while (size < tcb_bytes) {
- uint32_t tx_buffer_address = ldl_le_pci_dma(&s->dev, tbd_address);
- uint16_t tx_buffer_size = lduw_le_pci_dma(&s->dev, tbd_address + 4);
-#if 0
- uint16_t tx_buffer_el = lduw_le_pci_dma(&s->dev, tbd_address + 6);
-#endif
- if (tx_buffer_size == 0) {
- /* Prevent an endless loop. */
- logout("loop in %s:%u\n", __FILE__, __LINE__);
- break;
- }
- tbd_address += 8;
TRACE(RXTX, logout
("TBD (simplified mode): buffer address 0x%08x, size 0x%04x\n",
- tx_buffer_address, tx_buffer_size));
- tx_buffer_size = MIN(tx_buffer_size, sizeof(buf) - size);
- pci_dma_read(&s->dev, tx_buffer_address, &buf[size], tx_buffer_size);
- size += tx_buffer_size;
+ tbd_address, tcb_bytes));
+ pci_dma_read(&s->dev, tbd_address, &buf[size], tcb_bytes);
+ size += tcb_bytes;
}
if (tbd_array == 0xffffffff) {
/* Simplified mode. Was already handled by code above. */
--
2.7.4
next prev parent reply other threads:[~2017-11-14 2:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 2:11 [Qemu-devel] [PULL 0/8] Net patches Jason Wang
2017-11-14 2:11 ` [Qemu-devel] [PULL 1/8] net: fix check for number of parameters to -netdev socket Jason Wang
2017-11-14 2:11 ` [Qemu-devel] [PULL 2/8] colo-compare: Insert packet into the suitable position of packet queue directly Jason Wang
2017-11-14 2:11 ` [Qemu-devel] [PULL 3/8] colo-compare: compare the packet in a specified Connection Jason Wang
2017-11-15 18:57 ` Peter Maydell
2017-11-16 1:32 ` Mao Zhongyi
2017-11-14 2:11 ` [Qemu-devel] [PULL 4/8] colo-compare: Fix comments Jason Wang
2017-11-14 2:11 ` [Qemu-devel] [PULL 5/8] colo: Consolidate the duplicate code chunk into a routine Jason Wang
2017-11-14 2:11 ` Jason Wang [this message]
2017-11-14 2:11 ` [Qemu-devel] [PULL 7/8] Add new PCI ID for i82559a Jason Wang
2017-11-15 6:43 ` Stefan Weil
2017-11-15 11:22 ` Jason Wang
2017-11-14 2:11 ` [Qemu-devel] [PULL 8/8] net/socket: fix coverity issue Jason Wang
2017-11-14 15:23 ` [Qemu-devel] [PULL 0/8] Net patches Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1510625498-4821-7-git-send-email-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=michael.nawrocki@gtri.gatech.edu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).