public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Martin Wilck <martin.wilck@ts•fujitsu.com>
To: alexander.h.duyck@intel•com, jeffrey.t.kirsher@intel•com,
	netdev@vger•kernel.org, e1000-devel@lists•sourceforge.net
Cc: "Uhe, Rudolf" <rudolf.uhe@ts•fujitsu.com>
Subject: [PATCH] fix WOL on 2nd port on i350
Date: Mon, 04 Jul 2011 16:17:43 +0200	[thread overview]
Message-ID: <4E11CB87.5040806@ts.fujitsu.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 538 bytes --]

WOL fails on second port of a i350 network adapter with the latest
upstream kernel driver. It works with the sf.net driver 3.0.19. The
following patch seems to be missing upstream.

Regards,
Martin

-- 
Dr. Martin Wilck
PRIMERGY System Software Engineer
x86 Server Engineering

FUJITSU
Fujitsu Technology Solutions GmbH
Heinz-Nixdorf-Ring 1
33106 Paderborn, Germany
Phone:			++49 5251 525 2796
Fax:			++49 5251 525 2820
Email:			martin.wilck@ts•fujitsu.com
Internet:		http://ts.fujitsu.com
Company Details:	http://ts.fujitsu.com/imprint


[-- Attachment #2: igb_i350_wol.diff --]
[-- Type: text/plain, Size: 539 bytes --]

--- linus/drivers/net/igb/igb_main.c	2011-06-13 00:17:28.000000000 +0200
+++ linus/drivers/net/igb/igb_main.c.new	2011-07-04 14:24:00.000000000 +0200
@@ -1985,7 +1985,7 @@ static int __devinit igb_probe(struct pc
 
 	if (hw->bus.func == 0)
 		hw->nvm.ops.read(hw, NVM_INIT_CONTROL3_PORT_A, 1, &eeprom_data);
-	else if (hw->mac.type == e1000_82580)
+	else if (hw->mac.type >= e1000_82580)
 		hw->nvm.ops.read(hw, NVM_INIT_CONTROL3_PORT_A +
 		                 NVM_82580_LAN_FUNC_OFFSET(hw->bus.func), 1,
 		                 &eeprom_data);


[-- Attachment #3: Type: text/plain, Size: 377 bytes --]

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2

[-- Attachment #4: Type: text/plain, Size: 257 bytes --]

_______________________________________________
E1000-devel mailing list
E1000-devel@lists•sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit http://communities.intel.com/community/wired

             reply	other threads:[~2011-07-04 14:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-04 14:17 Martin Wilck [this message]
2011-07-06  8:53 ` [E1000-devel] [PATCH] fix WOL on 2nd port on i350 Jeff Kirsher

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=4E11CB87.5040806@ts.fujitsu.com \
    --to=martin.wilck@ts$(echo .)fujitsu.com \
    --cc=alexander.h.duyck@intel$(echo .)com \
    --cc=e1000-devel@lists$(echo .)sourceforge.net \
    --cc=jeffrey.t.kirsher@intel$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=rudolf.uhe@ts$(echo .)fujitsu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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