netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Jiri Benc <jbenc@suse.cz>,
	netdev@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>,
	John Linville <linville@tuxdriver.com>,
	Michael Buesch <mb@bu3sch.de>, Hong Liu <hong.liu@intel.com>
Subject: Re: [PATCH 3/6] d80211: add a perm_addr hardware property
Date: Sat, 04 Nov 2006 00:19:33 +0100	[thread overview]
Message-ID: <1162595973.24673.13.camel@johannes.berg> (raw)
In-Reply-To: <200611031649.32739.flamingice@sourmilk.net>

[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]

On Fri, 2006-11-03 at 16:49 -0500, Michael Wu wrote:

> Shouldn't you add something to ieee80211_set_mac_address so the driver/d80211 
> can find out what MAC address the user actually wants?

Hmm? d80211 already handles the case of the user changing a net_dev's
mac address fine. And it'll tell your driver about it whenever it
matters, at the time the user tries to UP that interface. And other than
that, the driver doesn't care.

> Might be easier to just point perm_addr to dev_addr, but that would make it 
> obvious that perm_addr is a bit messy. A wrapper for drivers that returns a 
> pointer to dev_addr might be a better idea.

I don't understand this. perm_addr is a field in the ieee80211_hw struct
reflecting the permanent mac address of the card. What's wrong with
that?

> Also, do we need to update interfaces associated with the master interface 
> when the master MAC address changes?

No. The interfaces are allowed to have differing mac addresses. But I
think they should all start out with the permanent mac address which is
why I put that field there. I guess you could argue for always using the
master's mac address. I would prefer new devices to start out with the
permanent mac address, but we can change that.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2006-11-03 23:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061102223854.692274000@sipsolutions.net>
2006-11-02 23:28 ` [PATCH 0/6] rework d80211 cookie pointer Michael Wu
     [not found] ` <20061102230013.960383000@sipsolutions.net>
2006-11-03  0:22   ` [PATCH 1/6] d80211: change the cookie to be opaque Johannes Berg
2006-11-03  0:46     ` Johannes Berg
2006-11-03  4:15       ` John W. Linville
2006-11-03  8:41         ` Johannes Berg
2006-11-05 15:20         ` Ivo van Doorn
2006-11-05 15:24           ` Johannes Berg
2006-11-03  9:21       ` Johannes Berg
2006-11-03  2:28     ` Michael Wu
2006-11-03  8:42       ` Johannes Berg
2006-11-03 19:04 ` [PATCH 0/6] rework d80211 cookie pointer Michael Wu
2006-11-03 19:08   ` Johannes Berg
2006-11-03 22:14     ` Michael Wu
2006-11-03 23:10       ` Johannes Berg
     [not found] ` <20061102230015.186648000@sipsolutions.net>
2006-11-03 21:49   ` [PATCH 3/6] d80211: add a perm_addr hardware property Michael Wu
2006-11-03 23:19     ` Johannes Berg [this message]
     [not found] ` <20061102230015.555750000@sipsolutions.net>
2006-11-03 22:27   ` [PATCH 4/6] d80211: add a struct device* " Michael Wu
2006-11-03 23:21     ` Johannes Berg
2006-11-03 23:46       ` Johannes Berg
     [not found] ` <20061102230016.080591000@sipsolutions.net>
2006-11-03 22:43   ` [PATCH 5/6] d80211: add a ethtool_ops " Michael Wu
2006-11-03 23:22     ` Johannes Berg

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=1162595973.24673.13.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=flamingice@sourmilk.net \
    --cc=hong.liu@intel.com \
    --cc=ivdoorn@gmail.com \
    --cc=jbenc@suse.cz \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=netdev@vger.kernel.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).