netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
To: "Kok, Auke" <auke-jan.h.kok@intel.com>
Cc: Andy Gospodarek <andy@greyhouse.net>,
	netdev@vger.kernel.org, bill.hayes@hp.com
Subject: Re: Setting alternate MAC addresses on e1000
Date: Tue, 08 Apr 2008 19:45:25 +0200	[thread overview]
Message-ID: <47FBAF35.5030004@aei.mpg.de> (raw)
In-Reply-To: <47FBAAAF.9060206@intel.com>

Hi all,

Kok, Auke schrieb:
>> Bill posted a patch for this a while back (but it was not accepted since
>> support for that hardware is offically moving to e1000e).  This may be
>> what you want....
> 
> yeah I thought of that as well and after digging through the documentation I don't
> think this will work for 82573's - it seems that only 82571 hardware supports this
> feature, which is not what Carsten needs.
> 
> as stated above, the alternate eeprom layout of the 82573 seems to also indicate that.

Thanks for not forgetting me :)

I wasn't able to reply yet because I'm buried in work, but the initial 
tip, to just use a different ID for the second device worked already. 
Though I don't use the alternate MAC possibility, I can change the MAC 
address easily - and already did that on ~280 nodes on Sunday.

So, I would say, please consider my problem solved.

Thanks to all of you who replied and the rest for the thoughts and the 
software!

Cheers

Carsten

      reply	other threads:[~2008-04-08 17:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 13:15 Setting alternate MAC addresses on e1000 Carsten Aulbert
2008-04-01 17:17 ` Brandeburg, Jesse
2008-04-02  8:07   ` Carsten Aulbert
2008-04-02 17:41     ` Brandeburg, Jesse
2008-04-08 17:02 ` Andy Gospodarek
2008-04-08 17:26   ` Kok, Auke
2008-04-08 17:45     ` Carsten Aulbert [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=47FBAF35.5030004@aei.mpg.de \
    --to=carsten.aulbert@aei.mpg.de \
    --cc=andy@greyhouse.net \
    --cc=auke-jan.h.kok@intel.com \
    --cc=bill.hayes@hp.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;
as well as URLs for NNTP newsgroup(s).