From: Jordan McCarthy <mccarthy@opentechinstitute.org>
To: linux-wireless@vger.kernel.org
Subject: IBSS-RSN support for BCM4313
Date: Wed, 24 Jul 2013 08:32:04 -0400 [thread overview]
Message-ID: <51EFC944.40502@opentechinstitute.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Linux wireless folk,
I am a developer at a non-profit working on a wireless mesh networking
platform, and we've just discovered that we have a fleet of netbooks
with the Broadcom 4313 chipset, one that does not work particularly well
(and sometimes not at all) in ad-hoc mode.
What's more, none of the available drivers seem to support IBSS-RSN,
which is absolutely essential for the requirements of our platform.
Accordingly, I wondered if anyone has any experience trying to get the
BCM4313 to work in an IBSS-RSN configuration, and if not, what is needed
to get either of the following:
- - brcmsmac to support adhoc mode
- - b43 to cover the BCM4313
Many thanks,
Jordan
- --
Jordan McCarthy
Technical Program Associate | Open Technology Institute | New America
Foundation
My Public Key: 0xC08D8042 | 4A61 3D39 4125 127D 65EA DDC2 BFBD A2E9 C08D
8042
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJR78lDAAoJEL+9ounAjYBClsUH/RgqnocuAhxTyHaXR9EHenhA
ZaSvOQCoCcWP5nOvSNSVHF/xmE7GJq+sPWzQs6O9iLI9bYiSE5NlO1V5wfISaQo/
xxdhczKyVZNFmzUgHnN+HCus99l6wOq5g+nHB8hALP9+iJ9gxJ5zyPVzgiOLLlgZ
3VXLRkQTeNNN/htTPrbiYQ6H/FPHXi4WOOxovpsYWSTw2B0BXwAJXDvP5wsBxzza
W0Gqb25Ipu3z2GtcH1qupPX1myARF1ZIN6hksJPcxgY5g/1IkYVI7kqr5B99ANo8
CCMxi/non3sFSPEBsiDlXKIw2toQG8xmjKYyAh+EY1PLQE48f2XAbj/jbwSmyPo=
=9usr
-----END PGP SIGNATURE-----
next reply other threads:[~2013-07-24 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 12:32 Jordan McCarthy [this message]
2013-07-24 14:40 ` IBSS-RSN support for BCM4313 Hauke Mehrtens
2013-07-24 20:57 ` Arend van Spriel
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=51EFC944.40502@opentechinstitute.org \
--to=mccarthy@opentechinstitute.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;
as well as URLs for NNTP newsgroup(s).