From: Johannes Berg <johannes@sipsolutions.net>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
otus-devel@lists.madwifi-project.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/2] ar9170-fw: Roll-your-own toolchain
Date: Sat, 06 Jun 2009 20:01:43 +0200 [thread overview]
Message-ID: <1244311303.17485.18.camel@johannes.local> (raw)
In-Reply-To: <4A2AAE4A.6060100@web.de>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
On Sat, 2009-06-06 at 19:58 +0200, Jan Kiszka wrote:
> The last statement I read was: "haven't found a way to properly transmit
> multicast frames after DTIM". Does this still apply on the new STA
> firmware?
Yes.
> What is the state of AP mode in the driver source? Just
> disabled, some bits missing - or even ready to work?
It works if you're willing to live with the above limitation, by just
enabling the AP bit. I've used it before.
> Another silly question: You wrote that 802.11n works with the firmware,
> and I blindly assumed that this of course includes a/b/g. I was right?
> My current AP works in g-mode when association with the ar9170 fails...
I never said anything works...
Anyhow, I _really_ can't support the firmware in any way. I just hacked
on it for fun and it turns out it ended up kinda working...
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2009-06-06 18:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 17:12 [PATCH 0/2] ar9170-fw: Roll-your-own toolchain Jan Kiszka
2009-06-06 17:20 ` Johannes Berg
2009-06-06 17:26 ` Jan Kiszka
2009-06-06 17:28 ` Johannes Berg
2009-06-06 17:37 ` Jan Kiszka
2009-06-06 17:45 ` Johannes Berg
2009-06-06 17:58 ` Jan Kiszka
2009-06-06 18:01 ` Johannes Berg [this message]
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=1244311303.17485.18.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=jan.kiszka@web.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=otus-devel@lists.madwifi-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.