public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Alex Owen <r.alex.owen@gmail.com>,
	linux-kernel@vger.kernel.org, aabdulla@nvidia.com,
	"H. Peter Anvin" <hpa@zytor.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: forcedeth net driver: reverse mac address after pxe boot
Date: Thu, 05 Oct 2006 20:35:05 +0200	[thread overview]
Message-ID: <45255059.3040908@gmx.net> (raw)
In-Reply-To: <20061005144442.GB18408@tuxdriver.com>

John W. Linville wrote:
> On Wed, Oct 04, 2006 at 05:19:20PM +0100, Alex Owen wrote:
> 
>> The obvious fix for this is to try and read the MAC address from the
>> canonical location... ie where is the source of the address writen
>> into the controlers registers at power on? But do we know where that
>> may be?
> 
> This seems like The Right Thing (TM) to me, but we need someone from
> NVidia(?) to provide that information.  Ayaz?

The canonical location of the "original" MAC address is where we write
back the reversed MAC address. So that won't work.

>> The other solution would be unconditionally reset the controler to
>> it's power on state then use the current logic? can we reset the
>> controller via software?
> 
> This seems like a plausible alternative.

AFAIK there is no way to do that (except powering off the machine).

> The MAC address validation schemes suggested by others would probably
> "work", but they would be a bit fragile.  For example, every new vendor
> of forcedeth hardware would have a new OUI to be added to the list.

Nooooo! That would be a nightmare. Especially because some BIOSes
allow users to set the MAC address. All those setups would be broken
instantly by that solution. (Yes, you can probably be clever, but
then you don't have a chance to fix this generically.)


Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/

  reply	other threads:[~2006-10-05 18:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-04 16:19 forcedeth net driver: reverse mac address after pxe boot Alex Owen
2006-10-04 16:50 ` H. Peter Anvin
2006-10-04 17:30 ` Alan Cox
2006-10-04 18:06   ` Ayaz Abdulla
2006-10-20 17:33   ` Alex Owen
2006-10-05 14:28 ` Denis Vlasenko
2006-10-05 14:44 ` John W. Linville
2006-10-05 18:35   ` Carl-Daniel Hailfinger [this message]
2006-10-05 19:31     ` John W. Linville
2006-10-05 19:45       ` Ayaz Abdulla
2006-10-06 14:37         ` Alex Owen
2006-10-06 17:29           ` Ayaz Abdulla
2006-10-06 19:11             ` John W. Linville
2006-10-06 21:02               ` Ayaz Abdulla
2006-10-05 19:45       ` Andrew de Quincey

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=45255059.3040908@gmx.net \
    --to=c-d.hailfinger.devel.2006@gmx.net \
    --cc=aabdulla@nvidia.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=r.alex.owen@gmail.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