From: "John W. Linville" <linville@tuxdriver.com>
To: Pavel Roskin <proski@gnu.org>
Cc: netdev@vger.kernel.org
Subject: Re: Please make CONFIG_CFG80211 harder to enable
Date: Sat, 9 Dec 2006 11:06:46 -0500 [thread overview]
Message-ID: <20061209160640.GA3365@tuxdriver.com> (raw)
In-Reply-To: <1165654123.2816.29.camel@portland.localdomain>
On Sat, Dec 09, 2006 at 03:48:43AM -0500, Pavel Roskin wrote:
> Hello!
>
> Somebody please mark CONFIG_CFG80211 in wireless-dev.git as
> experimental/broken/incomplete/whatever. Not only doesn't it work, but
> it also breaks Wireless Extensions if enabled, even if CONFIG_D80211 is
> disabled.
>
> Driver developers should know that if they enable CONFIG_CFG80211 they
> won't be able to debug their drivers effectifely; they'll have to fix
> cfg80211 first.
Perhaps you could be more specific? I'm sending this to you from a
box booted on the current (~1 week old) wireless-dev kernel using a
WEXT-configured ipw2200 device.
What problems are you experiencing? CFG80211 shouldn't interfere w/
WEXT if a driver doesn't support it.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2006-12-09 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 8:48 Please make CONFIG_CFG80211 harder to enable Pavel Roskin
2006-12-09 16:06 ` John W. Linville [this message]
2006-12-10 6:48 ` Paul Collins
2006-12-10 8:12 ` Pavel Roskin
2006-12-10 13:17 ` Johannes Berg
2006-12-10 16:08 ` Pavel Roskin
2006-12-10 16:21 ` [PATCH] fix cfg80211 WE compat code Johannes Berg
2006-12-22 2:53 ` Pavel Roskin
2006-12-22 5:30 ` Pavel Roskin
2006-12-22 11:04 ` Johannes Berg
2006-12-10 13:27 ` Please make CONFIG_CFG80211 harder to enable Michael Buesch
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=20061209160640.GA3365@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=proski@gnu.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.