From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Kalle Valo <kvalo@adurom.com>
Cc: Jason Andryuk <jandryuk@gmail.com>,
linux-wireless@vger.kernel.org, Ivo Van Doorn <ivdoorn@gmail.com>,
Gertjan van Wingerde <gwingerde@gmail.com>,
Johannes Stezenbach <js@sig21.net>
Subject: Re: 5GHz 802.11n USB Adapter
Date: Tue, 11 Jan 2011 15:57:46 +0100 [thread overview]
Message-ID: <201101111557.46845.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <87ipxvfqg1.fsf@purkki.adurom.net>
Am Dienstag, 11. Januar 2011 schrieb Kalle Valo:
> Helmut Schaa <helmut.schaa@googlemail.com> writes:
>
> >> If some hardware models don't support broadcast/multicast buffering in
> >> that case the driver shouldn't allow AP mode, at least not in mainline
> >> kernels. We shouldn't break the standarnd knowingly.
> >>
> >> From a quick grep it looks like rt2800usb enables AP mode. Is that the
> >> case or did I misunderstood something?
> >
> > You're right, rt2800usb enables AP mode despite the lack of proper
> > mc- and bc buffering.
>
> Ok, thanks. I'll try to come up with a patch which disables AP mode
> for rt2800usb.
Fine with me but AFAIK there are quite some users out there that use rt2800usb
in AP mode. In the end Ivo or Gertjan should have a chance to comment ;)
And furthermore Johannes Stezenbach is interested in getting rt2800usb
to do the mc- and bc buffering correctly. Not sure if he already had a chance
to investigate more.
Helmut
next prev parent reply other threads:[~2011-01-11 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 19:21 5GHz 802.11n USB Adapter Jason Andryuk
2011-01-08 20:32 ` Helmut Schaa
2011-01-10 4:16 ` Kalle Valo
2011-01-10 16:03 ` Helmut Schaa
2011-01-11 14:46 ` Kalle Valo
2011-01-11 14:57 ` Helmut Schaa [this message]
2011-01-11 15:45 ` Kalle Valo
2011-01-11 16:34 ` Johannes Stezenbach
2011-01-11 16:39 ` Ivo Van Doorn
2011-01-11 22:10 ` Kalle Valo
2011-01-14 23:07 ` Jason Andryuk
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=201101111557.46845.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=gwingerde@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=jandryuk@gmail.com \
--cc=js@sig21.net \
--cc=kvalo@adurom.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).