From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Finn Thain <fthain@telegraphics.com.au>,
Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org
Cc: "Aleksandar Rikalo" <aleksandar.rikalo@rt-rk.com>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"Laurent Vivier" <laurent@vivier.eu>,
qemu-stable@nongnu.org
Subject: Re: [PATCH v3 09/14] dp8393x: Use long-word-aligned RRA pointers in 32-bit mode
Date: Tue, 28 Jan 2020 12:13:34 +0100 [thread overview]
Message-ID: <ec30b6a0-a99e-9cae-fe25-a6e77d7be2f1@redhat.com> (raw)
In-Reply-To: <b971aa27c59c56f5c7c6bfaf26080fd97bb5cb9f.1579474761.git.fthain@telegraphics.com.au>
On 1/19/20 11:59 PM, Finn Thain wrote:
> Section 3.4.1 of the datasheet says,
>
> The alignment of the RRA is confined to either word or long word
> boundaries, depending upon the data width mode. In 16-bit mode,
> the RRA must be aligned to a word boundary (A0 is always zero)
> and in 32-bit mode, the RRA is aligned to a long word boundary
> (A0 and A1 are always zero).
>
> This constraint has been implemented for 16-bit mode; implement it
> for 32-bit mode too.
>
> Signed-off-by: Finn Thain <fthain@telegraphics.com.au>
> Tested-by: Laurent Vivier <laurent@vivier.eu>
> ---
> hw/net/dp8393x.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/hw/net/dp8393x.c b/hw/net/dp8393x.c
> index 947ceef37c..b052e2c854 100644
> --- a/hw/net/dp8393x.c
> +++ b/hw/net/dp8393x.c
> @@ -663,12 +663,16 @@ static void dp8393x_write(void *opaque, hwaddr addr, uint64_t data,
> qemu_flush_queued_packets(qemu_get_queue(s->nic));
> }
> break;
> - /* Ignore least significant bit */
> + /* The guest is required to store aligned pointers here */
> case SONIC_RSA:
> case SONIC_REA:
> case SONIC_RRP:
> case SONIC_RWP:
> - s->regs[reg] = val & 0xfffe;
> + if (s->regs[SONIC_DCR] & SONIC_DCR_DW) {
> + s->regs[reg] = val & 0xfffc;
> + } else {
> + s->regs[reg] = val & 0xfffe;
> + }
> break;
> /* Invert written value for some registers */
> case SONIC_CRCT:
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2020-01-28 11:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 22:59 [PATCH v3 00/14] Fixes for DP8393X SONIC device emulation Finn Thain
2020-01-19 22:59 ` [PATCH v3 01/14] dp8393x: Mask EOL bit from descriptor addresses Finn Thain
2020-01-28 11:21 ` Philippe Mathieu-Daudé
2020-01-28 22:57 ` Finn Thain
2020-01-19 22:59 ` [PATCH v3 13/14] dp8393x: Don't reset Silicon Revision register Finn Thain
2020-01-28 11:08 ` Philippe Mathieu-Daudé
2020-01-28 22:28 ` Finn Thain
2020-01-29 6:53 ` Philippe Mathieu-Daudé
2020-01-29 7:52 ` Finn Thain
2020-01-19 22:59 ` [PATCH v3 10/14] dp8393x: Pad frames to word or long word boundary Finn Thain
2020-01-28 11:02 ` Philippe Mathieu-Daudé
2020-01-19 22:59 ` [PATCH v3 02/14] dp8393x: Always use 32-bit accesses Finn Thain
2020-01-19 22:59 ` [PATCH v3 05/14] dp8393x: Update LLFA and CRDA registers from rx descriptor Finn Thain
2020-01-19 22:59 ` [PATCH v3 11/14] dp8393x: Clear descriptor in_use field to release packet Finn Thain
2020-01-19 22:59 ` [PATCH v3 14/14] dp8393x: Don't stop reception upon RBE interrupt assertion Finn Thain
2020-01-19 22:59 ` [PATCH v3 07/14] dp8393x: Implement packet size limit and RBAE interrupt Finn Thain
2020-01-19 22:59 ` [PATCH v3 12/14] dp8393x: Always update RRA pointers and sequence numbers Finn Thain
2020-01-19 22:59 ` [PATCH v3 09/14] dp8393x: Use long-word-aligned RRA pointers in 32-bit mode Finn Thain
2020-01-28 11:13 ` Philippe Mathieu-Daudé [this message]
2020-01-19 22:59 ` [PATCH v3 03/14] dp8393x: Clean up endianness hacks Finn Thain
2020-01-28 11:02 ` Philippe Mathieu-Daudé
2020-01-19 22:59 ` [PATCH v3 04/14] dp8393x: Have dp8393x_receive() return the packet size Finn Thain
2020-01-28 11:03 ` Philippe Mathieu-Daudé
2020-01-28 11:04 ` Philippe Mathieu-Daudé
2020-01-19 22:59 ` [PATCH v3 06/14] dp8393x: Clear RRRA command register bit only when appropriate Finn Thain
2020-01-19 22:59 ` [PATCH v3 08/14] dp8393x: Don't clobber packet checksum Finn Thain
2020-01-28 0:12 ` [PATCH v3 00/14] Fixes for DP8393X SONIC device emulation Laurent Vivier
2020-01-28 0:25 ` Finn Thain
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=ec30b6a0-a99e-9cae-fe25-a6e77d7be2f1@redhat.com \
--to=philmd@redhat.com \
--cc=aleksandar.rikalo@rt-rk.com \
--cc=fthain@telegraphics.com.au \
--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).