Netdev List
 help / color / mirror / Atom feed
From: "Michael Chan" <mchan@broadcom.com>
To: "Teodor MICU" <mteodor@gmail.com>
Cc: 690845@bugs.debian.org, netdev <netdev@vger.kernel.org>
Subject: Re: Bug#690845: ethtool: incorrect WoL detection on Broadcom NX II rev < 12
Date: Mon, 22 Oct 2012 15:54:19 -0700	[thread overview]
Message-ID: <1350946459.8764.145.camel@LTIRV-MCHAN1.corp.ad.broadcom.com> (raw)
In-Reply-To: <CAG2Wgfdn52R2FYh77-2ZHCFVwe8d0MOv_4but6aOsU50jF-+Lg@mail.gmail.com>

On Mon, 2012-10-22 at 10:52 +0300, Teodor MICU wrote:
> 08:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708
> Gigabit Ethernet (rev 11)

It is 5708 B1, and due to some hardware limitations, ethtool initiated
WoL is not supported.  Here's the code fragment in bnx2.c:

	if ((CHIP_ID(bp) == CHIP_ID_5708_A0) ||
	    (CHIP_ID(bp) == CHIP_ID_5708_B0) ||
	    (CHIP_ID(bp) == CHIP_ID_5708_B1) ||
	    !(REG_RD(bp, BNX2_PCI_CONFIG_3) & BNX2_PCI_CONFIG_3_VAUX_PRESET)) {
		bp->flags |= BNX2_FLAG_NO_WOL;
		bp->wol = 0;
	}

  reply	other threads:[~2012-10-22 22:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121018134717.9579.22997.reportbug@palomino.museglobal.com>
     [not found] ` <1350570748.26833.102.camel@deadeye.wl.decadent.org.uk>
     [not found]   ` <CAG2Wgfee=qsiUhAk5reYTypcOZL0kM5A58J+LjB1wuQ_k9FrfA@mail.gmail.com>
2012-10-19  1:30     ` Bug#690845: ethtool: incorrect WoL detection on Broadcom NX II rev < 12 Ben Hutchings
2012-10-19 19:38       ` Michael Chan
2012-10-22  7:52         ` Teodor MICU
2012-10-22 22:54           ` Michael Chan [this message]
2012-10-23  1:45             ` Ben Hutchings
2012-10-23  2:18               ` Michael Chan
2012-10-24 14:23                 ` Ben Hutchings

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=1350946459.8764.145.camel@LTIRV-MCHAN1.corp.ad.broadcom.com \
    --to=mchan@broadcom.com \
    --cc=690845@bugs.debian.org \
    --cc=mteodor@gmail.com \
    --cc=netdev@vger.kernel.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