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: Thu, 19 Feb 2009 08:33:37 +0200 [thread overview]
Message-ID: <87fxibhr5q.fsf@litku.valot.fi> (raw)
In-Reply-To: <1235014330.6344.18.camel@rainbow> (Jason Andryuk's message of "Wed\, 18 Feb 2009 22\:32\:10 -0500")
Jason Andryuk <jandryuk@gmail.com> writes:
> On Wed, 2009-02-18 at 22:31 +0200, Kalle Valo wrote:
>> Jason Andryuk <jandryuk@gmail.com> writes:
>>
>> > Additionally, I added some ieee80211_{wake,stop}_queues calls that
>> > were contained in the older at76_usb. There is ambiguity as to
>> > whether at76_join should be called before or after waking the queues.
>>
>> I would like to have a separate patch for this. Also I would like to
>> know what kind of bug this fixes.
>>
>> Sorry to be so picky, but I'm going to push the driver into mainline
>> soon and I try avoid regressions right now.
>
> I must admit, I do not have the best understanding of the driver.
Don't worry, we both are new here. I'm not that familiar with usb :)
> As such, I was making modifications to at76c50x-usb to be as similar
> to at76_usb+mac80211 as possible to prevent the driver from
> oops-ing.
I'm very glad that you have been working with that, it has helped me a
lot.
> I don't know the proper usage of ieee80211_{wake,stop}_queues, but my
> understanding is they should be called at different times to indicate
> readiness for transmitting frames to the mac80211 stack.
Yes, you have understood correctly. It's just that I don't see any
problems with my device, so I would like to understand why these
changes are needed and what issue they fix. I didn't analyse this
properly yet, though.
> I am having issues with my Linksys WUSB11 adapter. It has the intersil
> 3861 and the scan command is reporting Command Status of 0x03 - Invalid
> parameter. For right now, scanning does not work for me.
Oh, that's bad. And the device is working fine with the old at76_usb
driver? Can you send some debug logs, please? Especially I'm
interested about hardware differences between your Linksys and the
Belkin I have.
> Sorry about the corrupt patches. The gmail web interface was causing
> problems.
No problem, I'm used to this. For example at work our mail servers are
corrupting all patches. We need to send them as attachments and even
gzip so that the mail don't convert tabs to spaces. Not fun at all :/
--
Kalle Valo
next prev parent reply other threads:[~2009-02-19 6:33 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 [this message]
2009-02-20 4:07 ` Jason Andryuk
2009-02-21 7:57 ` Kalle Valo
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=87fxibhr5q.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).