From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Konstantin Kalin <konstantin.kalin@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NVIDIA Ethernet & invalid MAC
Date: Tue, 16 Oct 2007 15:43:13 +0100 [thread overview]
Message-ID: <20071016154313.53d19c43@the-village.bc.nu> (raw)
In-Reply-To: <4714C66D.4010607@gmail.com>
On Tue, 16 Oct 2007 18:10:53 +0400
Konstantin Kalin <konstantin.kalin@gmail.com> wrote:
> Hello,
>
> Recently we've got some computers with new motherboard having NVidia
> chipset. The motherboard has nforce12 & nforce13 Ethernet cards. I've
> noticed that MAC address is setup random each boot. I debugged the
> driver and found that these cards have right-byte order of MAC address
> but the driver is expecting incorrect byte-order for these models.
The only obvious thing I can think of to try would be to read the MAC
address both ways around.
The first 3 bytes of the resulting MAC should always be the Nvidia
allocation as I understand it and if so you can then decide which way
around is correct.
ie if it starts 00:04:0B then you know which way around it goes. (there
is one address that is the same either way around but clearly that one
doesn't matter).
So perhaps do that and for the afflicted parts add an EITHER_WAY_AROUND
flag ?
Alan
next prev parent reply other threads:[~2007-10-16 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 14:10 Konstantin Kalin
2007-10-16 14:43 ` Alan Cox [this message]
2007-10-16 15:16 ` Chuck Ebbert
2007-10-16 15:43 ` Alan Cox
2007-10-16 16:00 ` Jeff Garzik
2007-10-16 16:20 ` YOSHIFUJI Hideaki / 吉藤英明
2007-10-16 16:35 ` Konstantin Kalin
2007-10-16 16:41 ` Jeff Garzik
2007-10-16 16:52 ` Konstantin Kalin
2007-10-17 13:08 ` Konstantin Kalin
2007-10-16 16:00 ` Chris Snook
2007-10-16 16:07 ` Jeff Garzik
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=20071016154313.53d19c43@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=konstantin.kalin@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®