public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Dan Williams <dcbw@redhat.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: Missing link quality with wireless-testing
Date: Wed, 18 Feb 2009 09:31:04 +0200	[thread overview]
Message-ID: <20090218073104.GA23366@jm.kir.nu> (raw)
In-Reply-To: <1234933059.21412.28.camel@californication>

On Wed, Feb 18, 2009 at 05:57:39AM +0100, Marcel Holtmann wrote:
> > Would setting qual->updated |= IW_QUAL_QUAL_INVALID; work for you?  If
> > some app doesn't handle that, it's totally, completely broken.
> 
> does wpa_supplicant handle this value correctly? I actually never
> checked that.

No, it doesn't use qual->updated at all. Then again, neither does it
rely on qual->qual either. The signal level (qual->level) is used first
and only if that is not available, qual->qual will be used in sorting
the results.

> However I think it is bad practice to abandon a value that has been
> previously set by mac80211 and remove it without any further warning. If
> a driver never set the value before it is a different story than
> mac80211 deciding to not set it any more from one kernel version to
> another one.

It would be interesting to know which applications depend only on
qual->qual values being there and cannot use qual->level. Anyway, I
would agree that it would be reasonable to fill in something in the
qual->qual field for now. It should be enough to do this in the wext
compat code (i.e., not changing anything in mac80211 and only touching
#ifdef CONFIG_WIRELESS_EXT blocks in net/wireless/scan.c). This would
provide somewhat useful value for applications that depend on a value
that was not really guaranteed to be there in the first place. I think I
would include the IW_QUAL_QUAL_INVALID flag anyway and just target the
broken apps with this workaround.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2009-02-18  7:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 18:52 Missing link quality with wireless-testing Marcel Holtmann
2009-02-17 19:43 ` Johannes Berg
2009-02-17 20:24   ` Marcel Holtmann
2009-02-17 20:55     ` Johannes Berg
2009-02-17 21:09       ` Marcel Holtmann
2009-02-17 23:25         ` Dan Williams
2009-02-18  4:57           ` Marcel Holtmann
2009-02-18  7:31             ` Jouni Malinen [this message]
2009-02-18  8:06               ` Marcel Holtmann
2009-02-18  8:25                 ` Jouni Malinen
2009-02-18 12:18                   ` Dan Williams
2009-02-18 12:33                     ` Jouni Malinen
2009-02-18 12:48                       ` Dan Williams
2009-02-18 13:20                         ` Dan Williams
2009-02-18 14:01                         ` Jouni Malinen
2009-02-18 14:25                         ` Johannes Berg
2009-02-18 13:37                     ` Johannes Berg
2009-02-18 15:13                       ` Dan Williams
2009-02-18 16:48                         ` Johannes Berg
2009-02-18 17:27 ` [PATCH] cfg80211/mac80211: fill qual.qual value/adjust max_qual.qual Johannes Berg
2009-02-18 17:29   ` 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=20090218073104.GA23366@jm.kir.nu \
    --to=j@w1.fi \
    --cc=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.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