netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <jkm@devicescape.com>
To: Jean Tourrilhes <jt@hpl.hp.com>
Cc: Jiri Benc <jbenc@suse.cz>, mabbas <mabbas@linux.intel.com>,
	Dan Williams <dcbw@redhat.com>,
	netdev@vger.kernel.org, Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH 5/7] d80211: indicate if unassociate/radio off status
Date: Thu, 21 Sep 2006 17:42:35 -0700	[thread overview]
Message-ID: <20060922004235.GA7322@instant802.com> (raw)
In-Reply-To: <20060921225514.GA26850@bougret.hpl.hp.com>

On Thu, Sep 21, 2006 at 03:55:14PM -0700, Jean Tourrilhes wrote:

> > Jean, are there any other possibilities?
> 
> 	Yes, dropping SIOCSIWAP (set) entirely, and keep only
> SIOCGIWAP (get).

I don't think that this would be acceptable.

> 	We need to be pragmatic. Very few people need to set a fixed
> BSSID. I would even venture to say that in the case of most people
> setting a fixed BSSID, it's an error and they should not do it (it
> kills roaming, which is a desirable feature). I've yet to find a card
> which scanning is broken to the point that you need to fudge the
> BSSID.

Maybe very few _people_ use it directly, but please keep in mind that
programs like wpa_supplicant may control roaming and do it by using this
SIOCSIWAP. In addition, being able to limit AP selection to one specific
BSSID can be quite useful for number of uses.

> 	There are some drivers that don't support SIOCSIWAP (set), and
> it's usually not a problem, users are not complaining about it. That's
> why I claim we could drop the (set) support. Of course, we can't do it
> because one PhD student at Berkeley need the feature ;-)

There's more than one PhD student needing this and I would be very much
against removing it.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2006-09-22  0:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 20:49 [PATCH 5/7] d80211: indicate if unassociate/radio off status mabbas
2006-08-28 21:17 ` Michael Wu
2006-08-29 17:55   ` Jouni Malinen
2006-08-29 22:28     ` Mohamed Abbas
2006-08-29 22:50       ` Michael Wu
2006-08-29 23:01         ` Michael Wu
2006-08-30 13:41           ` Dan Williams
2006-08-30 17:22             ` Michael Wu
2006-09-21 17:01 ` Jiri Benc
2006-09-21 19:03   ` Dan Williams
2006-09-21 19:47     ` mabbas
2006-09-21 20:30       ` Dan Williams
2006-09-21 20:39         ` mabbas
2006-09-21 22:38           ` Jiri Benc
2006-09-21 22:55             ` Jean Tourrilhes
2006-09-22  0:42               ` Jouni Malinen [this message]
2006-09-22  0:57                 ` Jean Tourrilhes
2006-09-22 22:29                   ` [d80211 patch 1/1] setting bss freq and phymode using rx_status mabbas
2006-09-25 16:16                     ` Jiri Benc
2006-09-25 17:15                       ` mabbas
2006-09-27 15:34                         ` Jiri Benc
2006-09-22  8:32         ` [PATCH 5/7] d80211: indicate if unassociate/radio off status Johannes Berg
2006-09-22 14:05           ` Dan Williams

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=20060922004235.GA7322@instant802.com \
    --to=jkm@devicescape.com \
    --cc=dcbw@redhat.com \
    --cc=jbenc@suse.cz \
    --cc=johannes@sipsolutions.net \
    --cc=jt@hpl.hp.com \
    --cc=mabbas@linux.intel.com \
    --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).