From: Johannes Berg <johannes@sipsolutions.net>
To: bcm43xx-dev@berlios.de
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: bcm43xx master mode works for me
Date: Tue, 06 Mar 2007 02:08:12 +0100 [thread overview]
Message-ID: <1173143292.15891.79.camel@johannes.berg> (raw)
[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]
I just gave this another try, after porting the fix for the
beacon_control kfree bug which I'd found and debugged with Michael on
IRC earlier (changeset 8ce88367b520c0fb303832026d5604a414e1259c in his
tree) to the latest wireless-dev [1] and making hostapd compile, I have
master mode working with bcm43xx.
That means I can now start working on creating a driver_nl82011.c for
hostapd and killing off the prism2 ioctls one by one :) Help is always
welcome though.
johannes
[1]
actually, that's not strictly true. my tree also contains these patches:
fix-mac80211-Kconfig [was sent to akpm for the s390 problems]
tasklet-free-debug.patch [kills scheduled tasklets in memory that is being freed]
fix-scanf.patch [fixes scanf, unfortunately nobody replied to that...]
export-device-rename.patch [gregkh has that]
wiphy-rename.patch [posted earlier]
delete-netlink-wext.patch [posted earlier]
rework-kconfig [posted earlier]
bluetape1.patch
bluetape2.patch
bluetape3.patch
bluetape4.patch
bluetape5.patch [Michael Wu's patch series]
sysfs-to-debugfs.patch [debugfs #1]
more-sysfs-to-debugfs.patch [debugfs #2]
wiphy-private-id.patch [posted earlier]
mac80211-netdev-stuff-to-debugfs.patch [debugfs #3]
fix-header-bogosities.patch [posted recently]
nl80211-new-commands.patch [work in progress]
wpa.h.patch [posted recently]
bcm43xx-fix.patch [the ported fix]
hostapd-compile.patch [posted FYI]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
reply other threads:[~2007-03-06 13:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1173143292.15891.79.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=bcm43xx-dev@berlios.de \
--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