From: Larry Finger <Larry.Finger@lwfinger.net>
To: John Linville <linville@tuxdriver.com>,
Bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org
Cc: Michael Buesch <mb@bu3sch.de>
Subject: bcm43xx-softmac maintainer
Date: Tue, 15 Aug 2006 18:33:50 -0500 [thread overview]
Message-ID: <44E259DE.50806@lwfinger.net> (raw)
As of today, I have taken on the duties of maintaining the bcm43xx-softmac code.
I thank Michael Buesch for the heroic job that he has done. He ruffled a few
feathers ;-) now and then, but he probably exhibited more patience than many
would have. Michael will be concentrating on the bcm43xx-dscape (AKA d80211)
code. It is expected that the many extra features of d80211 will eventually lead
to its acceptance as the "official" 802.11 stack of Linux, replacing
bcm43xx-softmac, which will probably die at that point. In the meantime, I'm
here to keep as good a product as possible for the users of mainline kernels.
Nearly everyone agrees that wireless networking is one area where Linux is
deficient; however, the situation has improved so much in the past year that I
have great hopes that it will soon be as easy to configure Wi-Fi in Linux as it
is in XP or Vista. I know that it will be more secure!
Please send bug reports to me, with proposed fixes if available. Please include
any past reports that you think might have been lost. I admit that I didn't read
all the pertinent E-mails as studiously as I will now.
I am particularly interested in the "MAC suspend failure" messages as my own
interface is one that suffers from this problem. If you see this message, please
send me the chip ID line from your logs, which will look something like
"bcm43xx: Chip ID 0x4306, rev 0x2".
Thanks,
Larry
reply other threads:[~2006-08-15 23:34 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=44E259DE.50806@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@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).