linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Dan Williams <dcbw@redhat.com>,
	Luis Carlos Cobo <luisca@cozybit.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:44:33 +0200	[thread overview]
Message-ID: <200807281544.33509.mb@bu3sch.de> (raw)
In-Reply-To: <1217251433.12662.5.camel@johannes.berg>

On Monday 28 July 2008 15:23:53 Johannes Berg wrote:
> On Sun, 2008-07-27 at 11:22 -0400, Dan Williams wrote:
> > On Thu, 2008-07-10 at 16:57 +0200, Luis Carlos Cobo wrote:
> > > Originally by Johannes Berg. This patch adds support for devices that do not
> > > report their MAC address until the firmware is loaded. While the address is not
> > > known, a multicast on is used.
> > 
> > Johannes, thoughts on this?  Is there a better way to do it for devices
> > that don't know their MAC address until firmware load?
> 
> I actually wrote this patch, but largely I don't care. It seemed that
> having unique MAC addresses would screw up less with udev, but maybe we
> can just leave it zeroed until we know?

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
tools should just be fixed, if they have problems with that.
(What are the udev problems, btw?)

-- 
Greetings Michael.

  reply	other threads:[~2008-07-28 13:45 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 [this message]
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
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=200807281544.33509.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luisca@cozybit.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).