From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] dummy -- support hardware address
Date: Thu, 8 Apr 2004 14:54:03 -0700 [thread overview]
Message-ID: <20040408145403.34382c96.davem@redhat.com> (raw)
In-Reply-To: <20040408110834.2fd1bd25@dell_ss3.pdx.osdl.net>
Stephen, why don't you do what usbnet does? Look at usbnet_init()
where it goes:
get_random_bytes (node_id, sizeof node_id);
node_id [0] &= 0xfe; // clear multicast bit
node_id [0] |= 0x02; // set local assignment bit (IEEE802)
I distinctly remember Alan Cox saying this was the right way
do this and avoid conflicts with Vendor assigned IDs.
next prev parent reply other threads:[~2004-04-08 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 18:08 [PATCH] dummy -- support hardware address Stephen Hemminger
2004-04-08 21:54 ` David S. Miller [this message]
2004-04-08 22:09 ` Stephen Hemminger
2004-04-09 18:45 ` [PATCH] (1/4) add random_ether_addr to ether_device.h Stephen Hemminger
2004-04-09 18:45 ` [PATCH] (3/4) usb gadget -- use random_ether_addr Stephen Hemminger
2004-04-09 18:45 ` [PATCH] (2/4) set random address in dummy Stephen Hemminger
2004-04-09 18:47 ` [PATCH] (4/4) usbnet -- use random_ether_addr Stephen Hemminger
2004-04-10 4:16 ` David S. Miller
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=20040408145403.34382c96.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).