qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: gerg@uclinux.org
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/4] hw/net: fix m68/ColdFire ethernet fec support
Date: Fri, 26 Jun 2015 15:27:12 +1000	[thread overview]
Message-ID: <1435296436-12152-1-git-send-email-gerg@uclinux.org> (raw)


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(-)

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  5:27 gerg [this message]
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
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=1435296436-12152-1-git-send-email-gerg@uclinux.org \
    --to=gerg@uclinux.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).