From: Ruben De Smet <ruben.de.smet@telenet.be>
To: b43-dev <b43-dev@lists.infradead.org>, linux-wireless@vger.kernel.org
Subject: Broadcom Corporation BCM43228 802.11a/b/g/n
Date: Thu, 20 Nov 2014 13:43:07 +0100 [thread overview]
Message-ID: <546DE1DB.7090900@telenet.be> (raw)
Hello b43 and linux-wireless
I'm not subscribed (anymore) to these lists, so please use the "reply
all" feature of your mailclient. Thank you :)
This will be the last day I'm using my Broadcom Corporation BCM43228
802.11a/b/g/n miniPCI WiFi card, as I'm switching to a faster Intel AC card.
Is there any interest in the linux-wireless or b43 community to have
this device for reverse engineering purposes? I'm able to send it for free.
Ruben
--
I prefer encrypted email. My key's signature ends in 1213DC10 and here's
a tutorial: http://lifehacker.com/180878/how-to-encrypt-your-email
-------------- 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/20141120/5dbc27a8/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Ruben De Smet <ruben.de.smet@telenet.be>
To: b43-dev <b43-dev@lists.infradead.org>, linux-wireless@vger.kernel.org
Subject: Broadcom Corporation BCM43228 802.11a/b/g/n
Date: Thu, 20 Nov 2014 13:43:07 +0100 [thread overview]
Message-ID: <546DE1DB.7090900@telenet.be> (raw)
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
Hello b43 and linux-wireless
I'm not subscribed (anymore) to these lists, so please use the "reply
all" feature of your mailclient. Thank you :)
This will be the last day I'm using my Broadcom Corporation BCM43228
802.11a/b/g/n miniPCI WiFi card, as I'm switching to a faster Intel AC card.
Is there any interest in the linux-wireless or b43 community to have
this device for reverse engineering purposes? I'm able to send it for free.
Ruben
--
I prefer encrypted email. My key's signature ends in 1213DC10 and here's
a tutorial: http://lifehacker.com/180878/how-to-encrypt-your-email
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2014-11-20 12:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 12:43 Ruben De Smet [this message]
2014-11-20 12:43 ` Broadcom Corporation BCM43228 802.11a/b/g/n Ruben De Smet
2014-11-20 12:51 ` Rafał Miłecki
2014-11-20 12:51 ` Rafał Miłecki
2014-11-20 14:49 ` Francesco Gringoli
2014-11-20 14:49 ` Francesco Gringoli
2014-11-20 20:46 ` Ruben De Smet
2014-11-20 20:46 ` Ruben De Smet
2014-11-20 20:54 ` Ruben De Smet
2014-11-20 20:54 ` Ruben De Smet
2014-11-20 13:28 ` Arend van Spriel
2014-11-20 13:28 ` Arend van Spriel
2014-11-20 20:47 ` Ruben De Smet
2014-11-20 20:47 ` Ruben De Smet
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=546DE1DB.7090900@telenet.be \
--to=ruben.de.smet@telenet.be \
--cc=b43-dev@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.