netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net
Subject: Re: Setting alternate MAC addresses on e1000
Date: Wed, 02 Apr 2008 10:07:18 +0200	[thread overview]
Message-ID: <47F33EB6.1050402@aei.mpg.de> (raw)
In-Reply-To: <36D9DB17C6DE9E40B059440DB8D95F5204D09A67@orsmsx418.amr.corp.intel.com>

Hi Jesse,

thanks for the hint, I was stupid to think these two NIC are just using 
the very same EEPROM.

Brandeburg, Jesse wrote:
> Carsten Aulbert wrote:
>> where magic is MAGIC=0x108c8086
>>
>> However this does not work on eth1 :(
> 
> I think you need a different MAGIC for eth1 since they are separate
> parts (different device ID) with separate eeproms, then the first 6 byte
> change should work for eth1 too.
> 

Yes, with MAGIC=0x109a8086 I can set the MAC address of eth1.

> in the future e1000-devel@lists.sf.net might be more appropriate to
> Intel specific hardware questions.  but copying netdev is still okay.

Will do, starting with a closely related question:

The Intel specs state that word 37H is a pointer to an "alternate MAC 
address". My boss things it would be wise to let the original MAC 
address in place and just add another MAC address, so that we can easily 
revert to the old "official" one by writing 0xffff into that word.

Has anyone experience with that approach? In principle that should be 
easy, however, I don't know where/how to find 6 free bytes from the 
table given in Intel's docs.

Thanks again and hopefully someone has some light for my brain ;)

Cheers

Carsten

  reply	other threads:[~2008-04-02  8:07 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 [this message]
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

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=47F33EB6.1050402@aei.mpg.de \
    --to=carsten.aulbert@aei.mpg.de \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jesse.brandeburg@intel.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).