From: kernelmail.jms@gmail.com (Julie Sullivan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: BCM4313 802.11b/g/n Wireless LAN Controller error in kernel 3.0
Date: Mon, 9 Jan 2012 22:09:59 +0000 [thread overview]
Message-ID: <CAAVPGOM9hJMag_JAfJG8av9JYVQ1pbeQ0UTjMihHTozwzNZVEQ@mail.gmail.com> (raw)
In-Reply-To: <CAAVPGOPhxsfZTVCLv3p1tvWS+7Oh4yffw1_2Se+AE+mOaU+oEg@mail.gmail.com>
(oops, sorry, replying to the list as well this time)
>
> Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
>
>
>
> Please let me know if this needs to be taken up with broadcom or with linux community..
>
>
>
> Regards
> Rajaneesh
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Hi Rajaneesh
If you are using a distro kernel (i.e. if you did not configure/build
the Broadcom driver in yourself) you should tell your distro
maintainers (i.e. Ubuntu support), because they are likely to be the
quickest to respond to you, and they will be in the best position to
find out/chase up what this is with whoever is responsible. Also if
this is a bug they will need to get it fixed for their other users
too.
If it's caused by an open source driver that's in the kernel tree they
_should_ then push their fix to the wireless/Broadcom devs working on
the mainline kernel, that is not your responsibility ;-)
Cheers
Julie
prev parent reply other threads:[~2012-01-09 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1325869202.8599.kernelnewbies@kernelnewbies.org>
2012-01-09 5:53 ` BCM4313 802.11b/g/n Wireless LAN Controller error in kernel 3.0 rajaneesh acharya
[not found] ` <CAAVPGOPhxsfZTVCLv3p1tvWS+7Oh4yffw1_2Se+AE+mOaU+oEg@mail.gmail.com>
2012-01-09 22:09 ` Julie Sullivan [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=CAAVPGOM9hJMag_JAfJG8av9JYVQ1pbeQ0UTjMihHTozwzNZVEQ@mail.gmail.com \
--to=kernelmail.jms@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).