diff options
| author | Finn Thain <fthain@telegraphics.com.au> | 2020-01-29 20:27:49 +1100 |
|---|---|---|
| committer | Michael Roth <mdroth@linux.vnet.ibm.com> | 2020-06-02 10:40:21 -0500 |
| commit | cbc8277051f76f8131f5d4c787862a16a5fa1707 (patch) | |
| tree | 9a0eade9cb3f09934b0378a558ffd5033ac924ae /hw/sparc64 | |
| parent | e7cad754fd0bf00c671a1509acc2981f11736ee8 (diff) | |
| download | qemu-cbc8277051f76f8131f5d4c787862a16a5fa1707.zip qemu-cbc8277051f76f8131f5d4c787862a16a5fa1707.tar.gz qemu-cbc8277051f76f8131f5d4c787862a16a5fa1707.tar.bz2 | |
dp8393x: Pad frames to word or long word boundary
The existing code has a bug where the Remaining Buffer Word Count (RBWC)
is calculated with a truncating division, which gives the wrong result
for odd-sized packets.
Section 1.4.1 of the datasheet says,
Once the end of the packet has been reached, the serializer will
fill out the last word (16-bit mode) or long word (32-bit mode)
if the last byte did not end on a word or long word boundary
respectively. The fill byte will be 0FFh.
Implement buffer padding so that buffer limits are correctly enforced.
Signed-off-by: Finn Thain <fthain@telegraphics.com.au>
Tested-by: Laurent Vivier <laurent@vivier.eu>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
(cherry picked from commit 350e7d9a77d3b9ac74d240e4b232db1ebe5c05bc)
*drop context dependencies from b7cbebf2b9d, 1ccda935d4f, and
19f70347731
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Diffstat (limited to 'hw/sparc64')
0 files changed, 0 insertions, 0 deletions