All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gery Kahn <geryk@ti.com>
To: Arik Nemtsov <arik@wizery.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Luciano Coelho <luciano.coelho@nokia.com>
Subject: Re: [PATCH 17/18] wl1271: Read MAC address from NVS file on HW startup
Date: Tue, 30 Nov 2010 21:01:23 +0200	[thread overview]
Message-ID: <4CF54A03.2090104@ti.com> (raw)
In-Reply-To: <AANLkTimtk2qXYOVPo+WRyV1Jhe-Fk-7hvoctuAF35ik7@mail.gmail.com>

On 30.Nov.10 18:04, Arik Nemtsov wrote:
>> The code flow of the add if (wl1271_op_add_interface) overwrites it from
>> vif.
> Thats the point of the patch. The MAC can be overwritten at any point
> between HW initialization and add_interface(). Either by a TESTMODE
> cmd or even by "ifconfig wlan0 hw ether xx:xx:xx:xx:xx:xx". The patch
> makes sure the MAC address is set (the default value is in the NVS)
> when the hardware is initialized.
>
> This allows the creation of monitor interfaces for instance. These are
> created without calling the driver's add_interface() and require a
> valid MAC address to be set. Such a monitor interface is added by
> hostapd when creating an AP (which explains why this patch is included
> in the AP-support patch-set).
>
> When this patch is applied one should be careful to not set the mac
> twice with different MAC addresses, as this might cause problems for
> the upper layers.
>
> Regards,
> Arik
The idea is to eliminate the situation where anyone "should be careful 
to not set the
MAC twice".
If there is MAC from NVS, make it system wide, w/o need to care about 
it. On the other hand,
if MAC set by `ifconfig' same story, make it system wide.

Best regards,
Gery

  reply	other threads:[~2010-11-30 19:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 11:32 [PATCH 00/18] AP mode support for wl12xx Arik Nemtsov
2010-11-18 11:32 ` [PATCH 01/18] wl1271: Add AP related configuration to conf_drv_settings Arik Nemtsov
2010-11-18 11:32 ` [PATCH 02/18] wl1271: AP mode - AP specific CMD_CONFIGURE sub-commands Arik Nemtsov
2010-11-18 11:32 ` [PATCH 03/18] wl1271: AP mode - add AP specific event Arik Nemtsov
2010-11-18 11:32 ` [PATCH 04/18] wl1271: AP-mode high level commands Arik Nemtsov
2010-11-18 11:32 ` [PATCH 05/18] wl1271: AP mode - workaround for FW bug on station remove Arik Nemtsov
2010-11-18 11:32 ` [PATCH 06/18] wl1271: AP mode - init sequence Arik Nemtsov
2010-11-18 11:32 ` [PATCH 07/18] wl1271: AP specific RX filter configuration Arik Nemtsov
2010-11-18 11:32 ` [PATCH 08/18] wl1271: Add AP related definitions to HOST-FW interface Arik Nemtsov
2010-11-18 11:32 ` [PATCH 09/18] wl1271: Configure AP on BSS info change Arik Nemtsov
2010-11-18 11:32 ` [PATCH 10/18] wl1271: AP mode config in ieee80211_ops.config Arik Nemtsov
2010-11-18 11:32 ` [PATCH 11/18] wl1271: AP mode - change filter config Arik Nemtsov
2010-11-18 11:32 ` [PATCH 12/18] wl1271: AP mode - add STA add/remove ops Arik Nemtsov
2010-11-18 11:32 ` [PATCH 13/18] wl1271: AP mode - changes in TX path Arik Nemtsov
2010-11-18 11:32 ` [PATCH 14/18] wl1271: AP mode - record TX configuration settings Arik Nemtsov
2010-11-18 11:32 ` [PATCH 15/18] wl1271: AP mode - encryption support Arik Nemtsov
2010-11-18 11:32 ` [PATCH 16/18] wl1271: AP mode - fetch appropriate firmware for AP Arik Nemtsov
2010-11-18 11:32 ` [PATCH 17/18] wl1271: Read MAC address from NVS file on HW startup Arik Nemtsov
2010-11-30 15:48   ` Gery Kahn
2010-11-30 16:04     ` Arik Nemtsov
2010-11-30 19:01       ` Gery Kahn [this message]
2010-11-30 19:20         ` Arik Nemtsov
2010-11-30 19:36           ` Gery Kahn
2010-11-30 21:23             ` Arik Nemtsov
2010-11-18 11:32 ` [PATCH 18/18] wl1271: Enable AP-mode Arik Nemtsov
2010-11-18 11:37 ` [PATCH 00/18] AP mode support for wl12xx Luciano Coelho
2010-11-18 11:42   ` Arik Nemtsov
2010-11-26  8:15 ` Luciano Coelho
2010-11-29  6:50   ` Arik Nemtsov

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=4CF54A03.2090104@ti.com \
    --to=geryk@ti.com \
    --cc=arik@wizery.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@nokia.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 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.