From: "Ayaz Abdulla" <AAbdulla@nvidia.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Alex Owen" <r.alex.owen@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <c-d.hailfinger.kernel.2004@gmx.net>
Subject: RE: forcedeth net driver: reverse mac address after pxe boot
Date: Wed, 4 Oct 2006 11:06:30 -0700 [thread overview]
Message-ID: <DBFABB80F7FD3143A911F9E6CFD477B0189CAAEC@hqemmail02.nvidia.com> (raw)
In-Reply-To: <1159983049.25772.84.camel@localhost.localdomain>
This is a known issue and has been fixed in the latest PXE code. I will
have to find that information for you guys. Can one of you open a bug to
formally keep track of it.
Thanks,
Ayaz
-----Original Message-----
From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
Sent: Wednesday, October 04, 2006 10:31 AM
To: Alex Owen
Cc: linux-kernel@vger.kernel.org; c-d.hailfinger.kernel.2004@gmx.net;
Ayaz Abdulla
Subject: Re: forcedeth net driver: reverse mac address after pxe boot
Ar Mer, 2006-10-04 am 17:19 +0100, ysgrifennodd Alex Owen:
> 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?
Why not check if the first or last 3 bytes are the Nvidia owner bits.
The only card that will misdetect is
00:16:17:17:16:00
which doesn't matter anyway
Alan
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
next prev parent reply other threads:[~2006-10-04 18:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 16:19 Alex Owen
2006-10-04 16:50 ` H. Peter Anvin
2006-10-04 17:30 ` Alan Cox
2006-10-04 18:06 ` Ayaz Abdulla [this message]
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
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=DBFABB80F7FD3143A911F9E6CFD477B0189CAAEC@hqemmail02.nvidia.com \
--to=aabdulla@nvidia.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®