From: Dan Williams <dcbw@redhat.com>
To: Dave <kilroyd@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH] [try 2] orinoco: more reliable scan handling
Date: Tue, 04 Dec 2007 12:42:46 -0500 [thread overview]
Message-ID: <1196790166.14628.2.camel@localhost.localdomain> (raw)
In-Reply-To: <47489C2D.7030606@gmail.com>
On Sat, 2007-11-24 at 21:48 +0000, Dave wrote:
>
>
> Dan Williams wrote:
> > Bring scan result handling more in line with drivers like ipw. Scan
> > results are aggregated and a BSS dropped after 15 seconds if no beacon
> > is received. This allows the driver to interact better with userspace
> > where more than one process may request scans or results at any time.
>
> I've only seen this recently, and am using it as a basis for some other changes. However I've noticed a couple issues:
Will clean up these and submit for 2.6.25 then, thanks.
Dan
> > +static int orinoco_process_scan_results(struct net_device *dev,
> > + unsigned char *buf,
> > + int len)
> > +{
> <snip>
> > + /* Try to update an existing bss first */
> > + list_for_each_entry(bss, &priv->bss_list, list) {
> > + if (compare_ether_addr(bss->bss.a.bssid, atom->a.bssid))
> if (!compare_ether_addr(bss->bss.a.bssid, atom->a.bssid))
>
> So that we proceed to the next bss when ether_addr doesn't match. Otherwise this loop never matches.
>
> > + continue;
> > + if (le16_to_cpu(bss->bss.a.essid_len) !=
> > + le16_to_cpu(atom->a.essid_len))
> > + continue;
> > + if (memcmp(bss->bss.a.essid, atom->a.essid,
> > + le16_to_cpu(atom->a.essid_len)))
> > + continue;
> memcpy(&bss->bss, atom, sizeof(bss->bss);
>
> So we actually update the scan results when we find an older set.
>
>
> HTH,
>
> Dave.
>
> PS. I couldn't figure how I could get a copy of this message to reply to, so this is going through gmane. Apologies if this confuses things, or doesn't come out right.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-12-04 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 16:17 [RFC PATCH] orinoco: more reliable scan handling Dan Williams
2007-10-10 18:32 ` John W. Linville
2007-10-11 3:56 ` [RFC PATCH] [try 2] " Dan Williams
[not found] ` <47489C2D.7030606@gmail.com>
2007-12-04 17:42 ` Dan Williams [this message]
2007-12-04 18:19 ` John W. Linville
2007-12-04 17:55 ` Dan Williams
2007-12-04 18:59 ` Dave
2007-12-04 20:19 ` 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=1196790166.14628.2.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=kilroyd@googlemail.com \
--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).