From: "John W. Linville" <linville@tuxdriver.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: wireless-dev.git breaks wireless extensions
Date: Sat, 17 Feb 2007 09:14:48 -0500 [thread overview]
Message-ID: <20070217141448.GB4566@tuxdriver.com> (raw)
In-Reply-To: <1171676740.29232.4.camel@dv>
On Fri, Feb 16, 2007 at 08:45:40PM -0500, Pavel Roskin wrote:
> On Fri, 2007-02-16 at 20:02 -0500, John W. Linville wrote:
> > Sounds like the new version of cfg80211's wext compatibility hook
> > is broken...?
>
> I've applied two patches by Johannes "fix wext_ioctl() exit path" and
> "fix cfg80211 modular compile w/o wext-compat", and MadWifi is working
> fine now.
Soungs good...thanks for the report!
> On the other hand, DadWifi won't compile:
>
> /home/proski/src/dadwifi/ath/if_ath_d80211.c: In function
> 'ath_d80211_calc_bssid_mask':
> /home/proski/src/dadwifi/ath/if_ath_d80211.c:305: error: 'struct
> ieee80211_hw' has no member named 'perm_addr'
>
> The same problem exists with iwlwifi. I'm away from my bcm43xx card at
> the moment.
Yep...this goes with the territory for out-of-kernel drivers.
FWIW, the changes are straight-forward. See the commits near the
top of the tree for examples.
> I'll post more if I find any problems with either upgrading the driver
> or wireless extensions for d80211 enabled drivers.
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-02-17 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 23:54 wireless-dev.git breaks wireless extensions Pavel Roskin
2007-02-17 0:09 ` 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 [this message]
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=20070217141448.GB4566@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox