From: Kalle Valo <kvalo@adurom.com>
To: David Gnedt <david.gnedt@davizone.at>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
Grazvydas Ignotas <notasas@gmail.com>,
Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Subject: Re: [PATCH 17/18] wl1251: enable tx path in monitor mode if necessary for packet injection
Date: Mon, 31 Jan 2011 18:02:06 +0200 [thread overview]
Message-ID: <8762t5dptt.fsf@purkki.adurom.net> (raw)
In-Reply-To: <4D45B7DC.3060303@davizone.at> (David Gnedt's message of "Sun\, 30 Jan 2011 20\:11\:24 +0100")
David Gnedt <david.gnedt@davizone.at> writes:
> If necessary enable the tx path in monitor mode for packet injection using
> the JOIN command with BSS_TYPE_STA_BSS and zero BSSID.
Ok, this answers my question, you send TX_ENABLE command during the
first frame transmission. I have to admit that it sounds a bit
hackish. I would prefer to keep the driver as simple as possible,
makes it easier to maintain it that way.
I would like to step back and first look at the problem you are trying
to solve and maybe there's a way we can fix the join command. Was it
something to do with firmware sending extra frames? Unfortunately TI
firmwares are notorious for that.
--
Kalle Valo
next prev parent reply other threads:[~2011-01-31 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D45A79A.1030102@davizone.at>
2011-01-30 19:11 ` [PATCH 17/18] wl1251: enable tx path in monitor mode if necessary for packet injection David Gnedt
2011-01-31 16:02 ` Kalle Valo [this message]
2011-01-31 23:00 ` David Gnedt
2011-02-01 22:47 ` Kalle Valo
2011-02-18 21:01 ` David Gnedt
2011-03-08 7:39 ` 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=8762t5dptt.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=GNUtoo@no-log.org \
--cc=david.gnedt@davizone.at \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=notasas@gmail.com \
/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.