From: Luis Carlos Cobo <luisca@cozybit.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Dan Williams <dcbw@redhat.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/6] mac80211: allow no mac address until firmware load
Date: Mon, 28 Jul 2008 15:56:37 +0200 [thread overview]
Message-ID: <1217253397.6364.2.camel@localhost> (raw)
In-Reply-To: <200807281544.33509.mb@bu3sch.de>
On Mon, 2008-07-28 at 15:44 +0200, Michael Buesch wrote:
> Well, I think that really is pretty weird and it is confusing to the
> user to see that pseudo random MAC that changes suddenly when the device is
> initialized. For the human user (so everybody but me), it would be better
> to have the MAC all-zeros until the firmware loaded. So it would be obvious
> that the MAC is not set, yet. I think userspace
The problem is that all-zeroes is actually a valid mac address, owned by
Xerox (http://standards.ieee.org/regauth/oui/oui.txt) Not that it will
probably cause us any problem, but a multicast address is afaik an
invalid mac for a device. Should we go for 01:allzeros?
--
Luis Carlos Cobo Rus GnuPG ID: 44019B60
cozybit Inc.
next prev parent reply other threads:[~2008-07-28 13:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 14:57 [PATCH 1/6] mac80211: allow no mac address until firmware load Luis Carlos Cobo
2008-07-27 15:22 ` Dan Williams
2008-07-28 13:23 ` Johannes Berg
2008-07-28 13:44 ` Michael Buesch
2008-07-28 13:56 ` Luis Carlos Cobo [this message]
2008-07-28 14:00 ` Michael Buesch
2008-07-28 14:59 ` Dan Williams
2008-07-28 15:07 ` Johannes Berg
2008-07-28 15:14 ` Dan Williams
2008-07-28 15:58 ` Tomas Winkler
2008-07-28 16:22 ` Dan Williams
2008-07-30 11:17 ` Luis Carlos Cobo
2008-07-30 11:35 ` Dan Williams
2008-07-30 14:30 ` John W. Linville
2008-07-30 14:52 ` Luis Carlos Cobo
2008-07-28 13:57 ` Dan Williams
2008-07-28 14:25 ` Michael Buesch
2008-07-28 14:44 ` Tomas Winkler
2008-07-28 14:49 ` Johannes Berg
2008-07-28 14:57 ` Dan Williams
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=1217253397.6364.2.camel@localhost \
--to=luisca@cozybit.com \
--cc=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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.