From: Kalle Valo <kalle.valo@iki.fi>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: "linux-wireless\@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] at76c50x-usb: support cfg80211 scanning
Date: Sat, 21 Feb 2009 09:57:49 +0200 [thread overview]
Message-ID: <87hc2okyrm.fsf@litku.valot.fi> (raw)
In-Reply-To: <c4d76b3b0902192007s347ea4e3hcfa3fae1a1e3060b@mail.gmail.com> (Jason Andryuk's message of "Thu\, 19 Feb 2009 23\:07\:03 -0500")
Jason Andryuk <jandryuk@gmail.com> writes:
> I thought before I was not getting any scan results. I may have been
> wrong. However right now with the driver from wireless-testing
> 2009-02-18, 4 APs show up in NetworkManager. Unfortunately, my AP is
> not one of them.
What's your distance to the AP?
> No signal strength is reported for any of them.
Yes, this is a know issue. I'll try to fix it soon.
> Curiously, there are distinct results for each of at76c50x-usb, a
> semi-operational iwl3945 and the functional rtl8187.
>
> CMD_SCAN is receiving a lot of status 0x03 CMD_STATUS_INVALID_PARAMETER
>
> With debug=0xf022c001 I get the output below. I was wondering if
> status=0x03 was being received because CMD_SET_MIB was called before
> CMD_SCAN's status was checked. Hopefully you can make some sense out
> of the below logs.
After a quick look I didn't find anything, but I will investigate this
more.
Is at76_usb (the staging driver) is working fine with your device? Can
you take logs from it so that we can compare?
--
Kalle Valo
next prev parent reply other threads:[~2009-02-21 7:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 0:43 [PATCH] at76c50x-usb: support cfg80211 scanning Jason Andryuk
2009-02-18 20:31 ` Kalle Valo
2009-02-19 3:32 ` Jason Andryuk
2009-02-19 6:33 ` Kalle Valo
2009-02-20 4:07 ` Jason Andryuk
2009-02-21 7:57 ` Kalle Valo [this message]
2009-02-21 21:44 ` Jason Andryuk
2009-02-21 22:00 ` Jason Andryuk
2009-02-22 11:49 ` Kalle Valo
2009-02-22 23:54 ` Jason Andryuk
2009-02-23 3:29 ` Jason Andryuk
2009-02-22 11:46 ` Kalle Valo
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=87hc2okyrm.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=jandryuk@gmail.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).