linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Kalle Valo <kalle.valo@iki.fi>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Oikarinen Juuso (Nokia-D/Tampere)" <juuso.oikarinen@nokia.com>
Subject: Re: [RFC 1/3] mac80211: WIP - add operating BSSID to device configuration struct
Date: Mon, 26 Oct 2009 11:11:46 +0200	[thread overview]
Message-ID: <4AE567D2.8040102@nokia.com> (raw)
In-Reply-To: <87tyxmh8i9.fsf@purkki.valot.fi>

ext Kalle Valo wrote:
> Luciano Coelho <luciano.coelho@nokia.com> writes:
> 
>> Some chips need to know the BSSID that we are interested in before we start
>> the association process.  This patch adds an operating BSSID to the device
>> configuration struct ieee80211_conf so that it can be passed to the driver
>> when op_config is called.
>>
>> With this solution we also solve the problem of some chips that require
>> an explicit disconnect command when disassociating.
> 
> You could explain here more how disconnection is possible. It's not
> obvious from the commit log.
> 
>> + * @oper_bssid: BSSID on which we are operating; some chips need to know
>> + *    which BSSID we are "tuned" to in order to improve power management,
>> + *    coexistence with other technologies (such as Bluetooth) and other
>> + *    filtering issues.
> 
> "Tuned" is confusing here. Also I think it's enough to specify the
> reasons in the commit log, and here just explain what the parameters
> is used for. Maybe something like this:
> 
> * @oper_bssid: BSSID on which we are operating; some chips need to
> *    know the BSSID before association. If zero, there is no
> *    association established nor any requests of it.
> 

Very good points.  I'll fix this as part of my rework on these patches.  Thanks 
for your comments!

-- 
Cheers,
Luca.

  reply	other threads:[~2009-10-26  9:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-16 12:27 [RFC 0/3] mac80211 operating bssid concept implementation Luciano Coelho
2009-10-16 12:27 ` [RFC 1/3] mac80211: WIP - add operating BSSID to device configuration struct Luciano Coelho
2009-10-22  8:55   ` Johannes Berg
2009-10-24  5:34     ` Luciano Coelho
2009-10-26  8:37       ` Kalle Valo
2009-10-26  9:10         ` Luciano Coelho
2009-10-26  9:28           ` Kalle Valo
2009-10-26  9:52             ` Luciano Coelho
2009-10-26  8:19   ` Kalle Valo
2009-10-26  9:11     ` Luciano Coelho [this message]
2009-10-16 12:27 ` [RFC 2/3] wl1271: WIP - use operating BSSID for joining and disconnecting Luciano Coelho
2009-10-16 12:27 ` [RFC 3/3] wl1271: WIP - remove workaround for disconnection Luciano Coelho

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=4AE567D2.8040102@nokia.com \
    --to=luciano.coelho@nokia.com \
    --cc=juuso.oikarinen@nokia.com \
    --cc=kalle.valo@iki.fi \
    --cc=linux-wireless@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).