Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ron Rindjunsky <ron.rindjunsky@intel.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	tomas.winkler@intel.com, flamingice@sourmilk.net
Subject: Re: [PATCH 1/2] mac80211: [RFC] adding bss_config to low level driver ops
Date: Wed, 24 Oct 2007 14:00:18 +0200	[thread overview]
Message-ID: <1193227218.4510.31.camel@johannes.berg> (raw)
In-Reply-To: <11932213374183-git-send-email-ron.rindjunsky@intel.com>

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

On Wed, 2007-10-24 at 12:22 +0200, Ron Rindjunsky wrote:

> +#define BSS_VERIFY_STATE_ASSOC		(1<<0)

Why "verify"? Shouldn't it be "CHANGED" instead?

> +struct ieee80211_bss_data {
> +	u8 verify_map;

Seeing that you already used 5 of 8 bits and we're likely to increase
this in the future, I'd go with a u32 here. Also, have you attempted to
make all fields 'valid' all the time and if so, why is there no
'changed' bitmap passed to the callback?

> +	/* association related data */
> +	u8 assoc;
> +	u16 aid;

And then reorder these two for less padding.

> + * @bss_info_changed: Handler for configuration requests related to BSS
> + * 	parameters that may vary during BSS's lifespan, and may affect low
> + * 	level driver (e.g. assoc/disassoc status, erp parameters).
> + * 	This function should not be used if no BSS has been set, unless
> + * 	for association indication.

I don't understand the last sentence here. Can you elaborate? Is it
meant as a note for mac80211 hackers? If so, wouldn't it be more
appropriate to add it to the function that calls this? Also, you didn't
add the if_id which will even break Intel's driver once multi-MAC
support is added...

> @@ -276,6 +276,7 @@ struct ieee80211_if_sta {
>  	u32 supp_rates_bits;
>  
>  	int wmm_last_param_set;
> +	struct ieee80211_bss_data bss_data;

Are you sure this will work properly? The same stuff must also be used
for AP mode, when hostapd decides to change things, no?

> +				if (bss->has_erp_value)
> +				    ieee80211_handle_erp_ie(dev,
> +							    bss->erp_value);

Seeing that you're shuffling around this code anyway, I'd put patch 2
into this patch.
 
johannes

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

  parent reply	other threads:[~2007-10-24 13:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 10:22 [PATCH 0/2] mac80211: [RFC] pass BSS info to low level driver Ron Rindjunsky
2007-10-24 10:22 ` [PATCH 1/2] mac80211: [RFC] adding bss_config to low level driver ops Ron Rindjunsky
2007-10-24 10:22   ` [PATCH 2/2] mac80211: [RFC] eliminating erp_ie_changed from " Ron Rindjunsky
2007-10-24 11:57     ` Johannes Berg
2007-10-25 10:01       ` Ron Rindzonski
2007-10-24 12:00   ` Johannes Berg [this message]
2007-10-25  9:59     ` [PATCH 1/2] mac80211: [RFC] adding bss_config to " Ron Rindzonski
2007-10-25 13:41       ` 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=1193227218.4510.31.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=flamingice@sourmilk.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=ron.rindjunsky@intel.com \
    --cc=tomas.winkler@intel.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