qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@uclinux.org>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] hw/net: fix m68/ColdFire ethernet fec support
Date: Fri, 26 Jun 2015 22:07:18 +1000	[thread overview]
Message-ID: <558D4076.1010104@uclinux.org> (raw)
In-Reply-To: <20150626101251.GK15457@stefanha-thinkpad.redhat.com>

Hi Stefan,

On 26/06/15 20:12, Stefan Hajnoczi wrote:
> On Fri, Jun 26, 2015 at 03:27:12PM +1000, gerg@uclinux.org wrote:
>> The following set of patches fixes the emulated ColdFire ethernet fec
>> driver. There is primarily two problems that need to be fixed.
>>
>> 1. The emulated driver needs to support probing of an attached phy.
>>     It is strait forward to emulate an attached phy, but to avoid using
>>     magic numbers I have factored out the common MII register and value
>>     definitions into their own mii.h file first.
>>
>> 2. Fix the fec driver receiver to return the correct value.
>>
>> With these changes in place the qemu m5208evb board emulation can probe,
>> identify and use the fec ethernet running a Linux guest.
>>
>>
>>   hw/net/mcf_fec.c                |   54 ++++++++++++++++++++++++++--
>>   include/hw/net/allwinner_emac.h |   40 ---------------------
>>   include/hw/net/mii.h            |   76 ++++++++++++++++++++++++++++++++++++++++
>>   3 files changed, 128 insertions(+), 42 deletions(-)
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
>
> If this series has no maintainer to go through I'll merge it via my net
> tree.  Please let me know if you'd like that.

That would be great. Please do merge via your tree.
Thanks for the review.

> mcf_fec is not fully correct yet, it needs to call
> qemu_flush_queued_packets() when rx_enabled transitions from 0 to 1.
> This will restart rx by sending any queued packets from the net
> subsystem.
>
> In order to get flow control between NetClientState peers working the
> following is missing:
>
> 1. mcf_fec_receive()'s !s->rx_enabled case should return -1 to drop
>     unexpected packets.
>
> 2. mcf_fec_receive() should return 0 in the (bd.flags & FEC_BD_E) == 0
>     case where we've run out of rx buffers.  That way the net subsystem
>     queues the packet and waits until the next RDAR write transitions
>     rx_enabled from 0 to 1.

Ok, thanks for the pointers. I'll work up some additional changes
that handle these cases.

Regards
Greg

  reply	other threads:[~2015-06-26 12:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  5:27 [Qemu-devel] [PATCH 0/4] hw/net: fix m68/ColdFire ethernet fec support gerg
2015-06-26  5:27 ` [Qemu-devel] [PATCH 1/4] hw/net: create common collection of MII definitions gerg
2015-06-26  5:27 ` [Qemu-devel] [PATCH 2/4] hw/net: add ANLPAR bit definitions to generic mii gerg
2015-06-26  5:27 ` [Qemu-devel] [PATCH 3/4] hw/net: add simple phy support to mcf_fec driver gerg
2015-06-26  5:27 ` [Qemu-devel] [PATCH 4/4] hw/net: fix mcf_fec driver receiver gerg
2015-06-26 10:12 ` [Qemu-devel] [PATCH 0/4] hw/net: fix m68/ColdFire ethernet fec support Stefan Hajnoczi
2015-06-26 12:07   ` Greg Ungerer [this message]
2015-06-30  5:38   ` Greg Ungerer
2015-07-27 13:11     ` Stefan Hajnoczi
2015-07-28  0:03       ` Greg Ungerer
2015-07-27 13:13 ` Stefan Hajnoczi

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=558D4076.1010104@uclinux.org \
    --to=gerg@uclinux.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).