From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Gabriel L. Somlo" <gsomlo@gmail.com>
Cc: "pbonzini@redhat.com" <pbonzini@redhat.com>,
Alexander Graf <agraf@suse.de>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC PATCH v1 2/2] e1000: adjust initial autoneg timing (for piix/osx)
Date: Wed, 2 Jul 2014 18:17:05 +0300 [thread overview]
Message-ID: <20140702151705.GB6649@redhat.com> (raw)
In-Reply-To: <20140702142133.GW1688@ERROL.INI.CMU.EDU>
On Wed, Jul 02, 2014 at 10:21:34AM -0400, Gabriel L. Somlo wrote:
> On Wed, Jul 02, 2014 at 12:33:16PM +0300, Michael S. Tsirkin wrote:
> > Just poking around the spec I find more things
> > we don't implement correctly wrt to auto-negotiation.
> > For example, MII_SR_AUTONEG_CAPS isn't set, is it?
> > Maybe that's why your guest doesn't work:
> > it doesn't expect to get autonegotation at all?
> >
> > So I have a question: does your patch actually help any guests?
> > If not, maybe we should defer it to after release,
> > and try to clean up autonegotiation more thouroughly for 2.2?
>
> I'll re-submit after 2.1 is officially out. But, since we're talking
> about MII_SR_AUTONEG_CAPS: PHY_STATUS is initialized to 0x794d, which
> includes setting the MII_SR_AUTONEG_CAPS bit (|= 0x8).
> Did you mean: we should check for MII_SR_AUTONEG_CAPS in have_autoneg() ?
> (i.e., on the chance it gets turned off by a guest-side write to
> PHY_STATUS) ?
PHY_STATUS isn't writeable is it?
No I just got confused with the binary math.
We really should use symbolic constants there,
we already have them defined.
>
> Thx,
> --G
>
> PS. Maybe also spell out the individual bits in phy_reg_init[] ? Like,
> instead of:
>
> [PHY_STATUS] = 0x794d,
>
> do this:
>
> [PHY_STATUS] = MII_SR_EXTENDED_CAPS |
> MII_SR_LINK_STATUS |
> MII_SR_AUTONEG_CAPS |
> MII_SR_PREAMBLE_SUPPRESS |
> MII_SR_EXTENDED_STATUS |
> MII_SR_10T_HD_CAPS |
> MII_SR_10T_FD_CAPS |
> MII_SR_100X_HD_CAPS |
> MII_SR_100X_FD_CAPS,
>
> ... for all registers ? Much more verbose, but IMHO that'd be a good
> thing :)
>
>
prev parent reply other threads:[~2014-07-02 15:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 16:55 [Qemu-devel] [RFC PATCH v1 0/2] e1000: More link negotiation vs. OS X Gabriel L. Somlo
2014-06-30 16:55 ` [Qemu-devel] [RFC PATCH v1 1/2] e1000: clean up set_phy_ctrl function Gabriel L. Somlo
2014-06-30 18:04 ` Michael S. Tsirkin
2014-06-30 18:12 ` Gabriel L. Somlo
2014-06-30 19:29 ` Gabriel L. Somlo
2014-06-30 19:35 ` Gabriel L. Somlo
2014-06-30 16:55 ` [Qemu-devel] [RFC PATCH v1 2/2] e1000: adjust initial autoneg timing (for piix/osx) Gabriel L. Somlo
2014-06-30 17:55 ` Michael S. Tsirkin
2014-06-30 18:00 ` Paolo Bonzini
2014-06-30 18:21 ` Alexander Graf
2014-07-02 9:02 ` Gabriel L. Somlo
2014-07-02 9:16 ` Alexander Graf
2014-07-02 20:49 ` [Qemu-devel] e1000 autoneg timing, piix/osx Gabriel L. Somlo
2014-07-02 21:02 ` Alexander Graf
2014-07-02 21:14 ` Gabriel L. Somlo
2014-07-02 21:54 ` Alexander Graf
2014-07-02 22:02 ` Gabriel L. Somlo
2014-07-03 8:04 ` Alexander Graf
2014-07-03 13:17 ` Gabriel L. Somlo
2014-07-03 13:20 ` Alexander Graf
2014-07-03 13:58 ` Gabriel L. Somlo
2014-07-03 14:02 ` Alexander Graf
2014-07-03 14:14 ` Gabriel L. Somlo
2014-07-03 14:51 ` Alexander Graf
2014-07-03 15:25 ` Alexander Graf
2014-07-03 16:09 ` Paolo Bonzini
2014-07-03 16:43 ` Gabriel L. Somlo
2014-07-03 17:33 ` Alexander Graf
2014-07-02 9:33 ` [Qemu-devel] [RFC PATCH v1 2/2] e1000: adjust initial autoneg timing (for piix/osx) Michael S. Tsirkin
2014-07-02 12:05 ` Gabriel L. Somlo
2014-07-02 12:09 ` Michael S. Tsirkin
2014-07-02 14:21 ` Gabriel L. Somlo
2014-07-02 15:17 ` Michael S. Tsirkin [this message]
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=20140702151705.GB6649@redhat.com \
--to=mst@redhat.com \
--cc=agraf@suse.de \
--cc=gsomlo@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).