From: "David S. Miller" <davem@redhat.com>
To: timothy.covell@ashavan.org
Cc: zhengpei@msu.edu, linux-kernel@vger.kernel.org
Subject: Re: strange kernel message when hacking the NIC driver
Date: Fri, 11 Jan 2002 04:28:44 -0800 (PST) [thread overview]
Message-ID: <20020111.042844.70219945.davem@redhat.com> (raw)
In-Reply-To: <200201111224.g0BCOYSr001179@svr3.applink.net>
In-Reply-To: <200201111159.g0BBxCSr001144@svr3.applink.net> <20020111.040715.48529485.davem@redhat.com> <200201111224.g0BCOYSr001179@svr3.applink.net>
From: Timothy Covell <timothy.covell@ashavan.org>
Date: Fri, 11 Jan 2002 06:20:42 -0600
True. I was assuming that the context of the post was
that the NICs were on the same network link.
I didn't catch that bit.
Solaris _defaults_ to using the MAC address from the
primary (hostname) NIC for the rest of them.
This has nothing to do with Solaris, it has to do with
open firmware variable settings. If there is a 'local-mac-address'
property in the device node for the ethernet card, that is what
the drivers use. Otherwise they use the "host MAC".
If you look, this is what we do under Linux on Sparc too.
next prev parent reply other threads:[~2002-01-11 12:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 4:19 strange kernel message when hacking the NIC driver Pei Zheng
2002-01-11 5:20 ` Timothy Covell
2002-01-11 11:55 ` Timothy Covell
2002-01-11 12:07 ` David S. Miller
2002-01-11 12:20 ` Timothy Covell
2002-01-11 12:28 ` David S. Miller [this message]
2002-01-12 21:37 ` Prof. Brand
2002-01-12 21:44 ` Timothy Covell
2002-01-11 13:11 ` Alan Cox
2002-01-11 19:02 ` Timothy Covell
2002-01-11 19:24 ` Paul Walmsley
2002-01-11 22:51 ` Timothy Covell
2002-01-12 21:37 ` Prof. Brand
2002-01-12 21:58 ` Timothy Covell
2002-01-11 19:33 ` Pei Zheng
-- strict thread matches above, loose matches on Subject: below --
2002-01-14 6:32 Zwane Mwaikambo
2002-01-14 7:41 ` Bernd Eckenfels
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=20020111.042844.70219945.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=timothy.covell@ashavan.org \
--cc=zhengpei@msu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.