From: Finn Thain <fthain@telegraphics.com.au>
To: "Hervé Poussineau" <hpoussin@reactos.org>,
"Laurent Vivier" <laurent@vivier.eu>
Cc: Aleksandar Rikalo <aleksandar.rikalo@rt-rk.com>,
qemu-stable@nongnu.org, Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 02/13] dp8393x: Clean up endianness hacks
Date: Tue, 7 Jan 2020 09:19:13 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.21.1.2001061953150.65@nippy.intranet> (raw)
In-Reply-To: <e44d136b8b71414e17200bb1b7edfd94fe866705.1576815466.git.fthain@telegraphics.com.au>
On Fri, 20 Dec 2019, Finn Thain wrote:
> The in_use field is no different to the other words handled using
> dp8393x_put() and dp8393x_get(). Use the same technique for in_use
> that is used everywhere else.
>
> Signed-off-by: Finn Thain <fthain@telegraphics.com.au>
> ---
> Changed since v1:
> - Use existing 'address' variable rather than declare a new one.
>
> Laurent tells me that this clean-up has been tried before. He referred
> me to commit c744cf7879 ("dp8393x: fix dp8393x_receive()") and
> commit 409b52bfe1 ("net/dp8393x: correctly reset in_use field").
>
> Both of those patches look wrong to me because they both pass the wrong
> byte count to address_space_rw(). It's possible that those patches were
> needed to work around some kind of bug elsewhere, for example, an
> off-by-one result from dp8393x_crda(). The preceding patch in this series
> might help there.
Unfortunately this patch really does break NetBSD/arc 5.1, just as
Laurent said it would, just as commit c744cf7879 did.
Yet these patches are correct. What gives?
I found that one more change can make guests work (for both m68k q800 and
mips64el magnum machines) --
--- a/hw/net/dp8393x.c
+++ b/hw/net/dp8393x.c
@@ -246,8 +246,10 @@ static void dp8393x_put(dp8393xState *s, int width,
int offset,
uint16_t val)
{
if (s->big_endian) {
+ s->data[offset * width] = 0;
s->data[offset * width + width - 1] = cpu_to_be16(val);
} else {
+ s->data[offset * width + width - 1] = 0;
s->data[offset * width] = cpu_to_le16(val);
}
}
For a wide bus interface, this forces the Most Significant Word (MSW) to
zero. Yet another endianness hack, but it makes NetBSD 5.1 'sn' driver
happy.
There is a similar issue with the Linux jazzsonic driver. This driver uses
long-word-sized loads with word-sized MMIO registers --
#define SONIC_READ(reg) (*((volatile unsigned int *)dev->base_addr+reg))
This driver also expects the MSW to be zero. But the MSW actually equals
the LSW, and the driver fails to probe:
SONIC ethernet controller not found (0x40004)
This seems to indicate that qemu-system-mips64el -M magnum is doing word
smearing on the processor bus. Does anyone know how to prevent that?
> ---
> hw/net/dp8393x.c | 17 ++++++-----------
> 1 file changed, 6 insertions(+), 11 deletions(-)
>
> diff --git a/hw/net/dp8393x.c b/hw/net/dp8393x.c
> index 1957bd391e..b2cc768d9b 100644
> --- a/hw/net/dp8393x.c
> +++ b/hw/net/dp8393x.c
> @@ -765,8 +765,6 @@ static ssize_t dp8393x_receive(NetClientState *nc, const uint8_t * buf,
> return -1;
> }
>
> - /* XXX: Check byte ordering */
> -
> /* Check for EOL */
> if (s->regs[SONIC_LLFA] & SONIC_DESC_EOL) {
> /* Are we still in resource exhaustion? */
> @@ -836,15 +834,12 @@ static ssize_t dp8393x_receive(NetClientState *nc, const uint8_t * buf,
> /* EOL detected */
> s->regs[SONIC_ISR] |= SONIC_ISR_RDE;
> } else {
> - /* Clear in_use, but it is always 16bit wide */
> - int offset = dp8393x_crda(s) + sizeof(uint16_t) * 6 * width;
> - if (s->big_endian && width == 2) {
> - /* we need to adjust the offset of the 16bit field */
> - offset += sizeof(uint16_t);
> - }
> - s->data[0] = 0;
> - address_space_rw(&s->as, offset, MEMTXATTRS_UNSPECIFIED,
> - (uint8_t *)s->data, sizeof(uint16_t), 1);
> + /* Clear in_use */
> + address = dp8393x_crda(s) + sizeof(uint16_t) * 6 * width;
> + size = sizeof(uint16_t) * width;
> + dp8393x_put(s, width, 0, 0);
> + address_space_rw(&s->as, address, MEMTXATTRS_UNSPECIFIED,
> + (uint8_t *)s->data, size, 1);
> s->regs[SONIC_CRDA] = s->regs[SONIC_LLFA];
> s->regs[SONIC_ISR] |= SONIC_ISR_PKTRX;
> s->regs[SONIC_RSC] = (s->regs[SONIC_RSC] & 0xff00) | (((s->regs[SONIC_RSC] & 0x00ff) + 1) & 0x00ff);
>
next prev parent reply other threads:[~2020-01-06 22:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 4:17 [PATCH v2 00/13] Fixes for DP8393X SONIC device emulation Finn Thain
2019-12-20 4:17 ` [PATCH v2 04/13] dp8393x: Update LLFA and CRDA registers from rx descriptor Finn Thain
2019-12-20 4:17 ` [PATCH v2 09/13] dp8393x: Use long-word-aligned RRA pointers in 32-bit mode Finn Thain
2019-12-20 4:17 ` [PATCH v2 06/13] dp8393x: Implement packet size limit and RBAE interrupt Finn Thain
2019-12-20 4:17 ` [PATCH v2 02/13] dp8393x: Clean up endianness hacks Finn Thain
2020-01-06 22:19 ` Finn Thain [this message]
2020-01-07 7:20 ` Philippe Mathieu-Daudé
2020-01-08 0:21 ` Finn Thain
2019-12-20 4:17 ` [PATCH v2 12/13] dp8393x: Always update RRA pointers and sequence numbers Finn Thain
2019-12-20 4:17 ` [PATCH v2 01/13] dp8393x: Mask EOL bit from descriptor addresses Finn Thain
2019-12-20 4:17 ` [PATCH v2 13/13] dp8393x: Correctly advance RRP Finn Thain
2019-12-20 22:15 ` Finn Thain
2019-12-20 4:17 ` [PATCH v2 11/13] dp8393x: Clear descriptor in_use field when necessary Finn Thain
2019-12-20 4:17 ` [PATCH v2 07/13] dp8393x: Don't stop reception upon RBE interrupt assertion Finn Thain
2019-12-20 4:17 ` [PATCH v2 03/13] dp8393x: Have dp8393x_receive() return the packet size Finn Thain
2019-12-20 4:17 ` [PATCH v2 08/13] dp8393x: Don't clobber packet checksum Finn Thain
2019-12-20 4:17 ` [PATCH v2 10/13] dp8393x: Pad frames to word or long word boundary Finn Thain
2019-12-20 4:17 ` [PATCH v2 05/13] dp8393x: Clear RRRA command register bit only when appropriate Finn Thain
2019-12-20 10:16 ` [PATCH v2 00/13] Fixes for DP8393X SONIC device emulation Laurent Vivier
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=alpine.LNX.2.21.1.2001061953150.65@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=aleksandar.rikalo@rt-rk.com \
--cc=hpoussin@reactos.org \
--cc=jasowang@redhat.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).