From: Pavel Roskin <proski@gnu.org>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: wireless-dev.git breaks wireless extensions
Date: Fri, 16 Feb 2007 18:54:17 -0500 [thread overview]
Message-ID: <1171670057.28539.5.camel@dv> (raw)
Hello!
Today's wireless-dev.git breaks wireless extensions. It forces
CONFIG_CFG80211 to be enabled. I reported that it breaks legacy driver=
s
back in December 2006. It's still broken. That's what I get for
MadWifi:
ath0 4=BF3=C0=D8=BD=BF ESSID:"" [51] Nickname:""
Channel:-0 Access Point: 9F:DD:13:94:33:C0 Bit Rate=3D-576=
733 kb/s =20
Tx-Power=3Doff Sensitivity=3D-576733388 dBm =20
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=3D0/94 Signal level=3D-96 dBm Noise level=3D-9=
6 dBm
Rx invalid nwid:2088 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
I'll appreciate if things known be broken are not enabled by default,
let alone unconditionally.
--=20
Regards,
Pavel Roskin
-
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2007-02-16 23:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 23:54 Pavel Roskin [this message]
2007-02-17 0:09 ` wireless-dev.git breaks wireless extensions Johannes Berg
2007-02-17 0:50 ` Pavel Roskin
2007-02-17 1:02 ` John W. Linville
2007-02-17 1:45 ` Pavel Roskin
2007-02-17 14:14 ` John W. Linville
2007-02-17 1:03 ` [PATCH] fix wext_ioctl() exit path Johannes Berg
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=1171670057.28539.5.camel@dv \
--to=proski@gnu.org \
--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