From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: export multiple MAC addresses in sysfs
Date: Wed, 20 Jan 2010 19:10:10 +0100 [thread overview]
Message-ID: <1264011010.11396.22.camel@johannes.local> (raw)
In-Reply-To: <43e72e891001201005p5207345es6eb1a4b196b22a47@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
On Wed, 2010-01-20 at 10:05 -0800, Luis R. Rodriguez wrote:
> On Wed, Jan 20, 2010 at 3:02 AM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > If a device has multiple MAC addresses, userspace will
> > need to know about that. Similarly, if it allows the
> > MAC addresses to vary by a bitmask.
> >
> > If a driver exports multiple addresses, it is assumed
> > that it will be able to deal with that many different
> > addresses, which need not necessarily match the ones
> > programmed into the device; if a mask is set then the
> > device should deal addresses within that mask based
> > on an arbitrary "base address".
> >
> > To test it all and show how it is used, add support
> > to hwsim even though it can't actually deal with
> > addresses different from the default.
> >
> > Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
>
> Any reason to not export this via nl80211?
Laziness, and the fact that we only exported it in sysfs before.
> Can we say, use this on Atheros devices for storage of the bssid mask?
That was the intention of the mask, yes.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2010-01-20 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 11:02 [PATCH] cfg80211: export multiple MAC addresses in sysfs Johannes Berg
2010-01-20 18:05 ` Luis R. Rodriguez
2010-01-20 18:10 ` Johannes Berg [this message]
2010-01-20 18:14 ` Luis R. Rodriguez
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=1264011010.11396.22.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@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