From: Daniel Paschka <monkey20181@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [ipw2200] add monitor and qos entries to Kconfig
Date: Thu, 05 Jan 2006 19:29:06 +0100 [thread overview]
Message-ID: <43BD6572.9090100@gmx.net> (raw)
In-Reply-To: <5rHzm-7c4-21@gated-at.bofh.it>
Andreas Happe wrote:
> Add the following config entries for the ipw2200 driver to
> drivers/net/wireless/Kconfig
> * IPW2200_MONITOR
> enables Monitor mode
> * IPW2200_QOS
> enables QoS feature - this is under development right now, so it depends
> upon EXPERIMENTAL
>
> driver compiles and enters monitor mode.
>
> Signed-off-by: Andreas Happe <andreashappe@snikt.net>
> --- drivers/net/wireless/Kconfig.orig 2006-01-05 18:30:10.000000000 +0100
> +++ drivers/net/wireless/Kconfig 2006-01-05 18:30:13.000000000 +0100
> @@ -217,6 +217,19 @@ config IPW2200
> say M here and read <file:Documentation/modules.txt>. The module
> will be called ipw2200.ko.
>
> +config IPW2200_MONITOR
> + bool "Enable promiscuous mode"
> + depends on IPW2200
> + ---help---
> + Enables promiscuous/monitor mode support for the ipw2200 driver.
> + With this feature compiled into the driver, you can switch to
> + promiscuous mode via the Wireless Tool's Monitor mode. While in this
> + mode, no packets can be sent.
> +
> +config IPW2200_MONITOR
> + bool "Enable QoS support"
> + depends on IPW2200 && EXPERIMENTAL
> +
> config IPW_DEBUG
> bool "Enable full debugging output in IPW2200 module."
> depends on IPW2200
I think you made a copy&paste error here. QoS is enabling monitor mode.
You probably meant IPW_QOS.
next parent reply other threads:[~2006-01-05 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5rHzm-7c4-21@gated-at.bofh.it>
2006-01-05 18:29 ` Daniel Paschka [this message]
2006-01-05 19:07 [ipw2200] add monitor and qos entries to Kconfig Bonilla, Alejandro
-- strict thread matches above, loose matches on Subject: below --
2006-01-05 17:56 Andreas Happe
2006-01-05 18:40 ` Andreas Happe
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=43BD6572.9090100@gmx.net \
--to=monkey20181@gmx.net \
--cc=linux-kernel@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