From: "John W. Linville" <linville@tuxdriver.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Luis Carlos Cobo <luisca@cozybit.com>,
Tomas Winkler <tomasw@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
Michael Buesch <mb@bu3sch.de>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/6] mac80211: allow no mac address until firmware load
Date: Wed, 30 Jul 2008 10:30:03 -0400 [thread overview]
Message-ID: <20080730143003.GB19408@tuxdriver.com> (raw)
In-Reply-To: <1217417721.11432.21.camel@localhost.localdomain>
On Wed, Jul 30, 2008 at 07:35:21AM -0400, Dan Williams wrote:
> On Wed, 2008-07-30 at 13:17 +0200, Luis Carlos Cobo wrote:
> > So I see three options:
> >
> > 1) Use 00:... and be happy. No problem with udev, we use an address that
> > is actually valid.
> >
> > 2) Use 01:00... and fix udev so it ignores it.
> >
> > 3) Use 44:44..., because it is what orinoco used and fix udev so it
> > ignores it.
> >
> > I would go for solution 2, 00:00:00:00:00:00 is a valid address for a
> > device and multicast addresses are not, and that should be reflected on
> > udev's policy.
>
> I guess, but having a zero MAC seems more logical to me, and it's also
> the failure case if something doesn't get properly initialized. WEXT
> uses it for "disassociated". We already check for the zero MAC in a
> number of places.
I'm with Dan -- use all zeroes.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-07-30 14:33 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
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 [this message]
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=20080730143003.GB19408@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luisca@cozybit.com \
--cc=mb@bu3sch.de \
--cc=tomasw@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;
as well as URLs for NNTP newsgroup(s).