From: Ruben De Smet <ruben.de.smet@telenet.be>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: b43-dev <b43-dev@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Looking for someone with BCM43227 and (maybe) compilation skill ; )
Date: Wed, 12 Nov 2014 19:56:29 +0100 [thread overview]
Message-ID: <5463AD5D.6060708@telenet.be> (raw)
In-Reply-To: <CACna6rwde+H8K42FgsHH=FT2tW_3o_NwVbk0ZyM_L3fVtfwAsA@mail.gmail.com>
On 08/28/2014 02:39 PM, Rafa? Mi?ecki wrote:
> It has appeared that BCM43227 and BCM43228 are pretty much identical
> from programming POV. You can try 3.17-rc1 (or newer) to see if it
> supports your wireless card :)
Hi!
Today Fedora 20 updated to 3.17 and so I was pretty eager to try b43
instead of wl. It didn't work like I hoped it would; networkmanager was
able to scan but not to connect with my BCM43228.
I've ordered an Intel WiFi card some days ago. So if the b43 team wants
to, I can send a developer my BCM card for free for developing, reverse
engineering and debugging purposes.
(I googled an excerpt of the dmesg error message (because it had a MAC
address in it I didn't want to give to Google), but I forgot to write
down the original message:
deauthenticating by local choice (Reason: 3=DEAUTH_LEAVING)
Ruben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20141112/4ef13359/attachment.sig>
prev parent reply other threads:[~2014-11-12 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 12:32 Looking for someone with BCM43227 and (maybe) compilation skill ;) Rafał Miłecki
2014-07-03 12:50 ` Looking for someone with BCM43227 and (maybe) compilation skill ; ) Rafał Miłecki
2014-08-28 12:33 ` Ruben De Smet
2014-08-28 12:39 ` Rafał Miłecki
2014-08-28 12:42 ` Ruben De Smet
2014-11-12 18:56 ` Ruben De Smet [this message]
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=5463AD5D.6060708@telenet.be \
--to=ruben.de.smet@telenet.be \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.com \
/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