linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Ari Kuusava" <arikuu@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [Kernel Bug] 3.6, wpasupplicant 1.0, broadcom-sta 6.20.55.19
Date: Sun, 7 Oct 2012 12:12:41 +0200	[thread overview]
Message-ID: <50715599.9020708@broadcom.com> (raw)
In-Reply-To: <loom.20121007T111537-642@post.gmane.org>

On 10/07/2012 11:26 AM, Ari Kuusava wrote:
> I am on Gentoo and using wpasupplicant with Broadcom BCM4727 802.11 Hybrid
> Wireless Controller 5.100.82.112.
> Everything works perfect in 3,5,4
> Upgrading to 3,6,0 stable gives same bug as to you.
> Only thing chanced is kernel.
> So I believe that's kernel busines
>
> Have a nice dayservicemen

I think your device is not BCM4727 so can you give me 'lspci -v' output.

The broadcom-sta package is provided by the distros and maintained by 
Broadcom as it is a out-of-tree driver. That means it needs to keep up 
with the latest kernels, but it is lagging. Basically, this is the major 
disadvantage of *not* doing driver development upstream.

Issue with broadcom-sta package can be sent to:

	linux-wlan-client-support-list@broadcom.com

Regards,
Arend


  reply	other threads:[~2012-10-07 10:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01  9:25 [Kernel Bug] 3.6, wpasupplicant 1.0, broadcom-sta 6.20.55.19 Jasmine Hassan
2012-10-01 11:34 ` John W. Linville
2012-10-01 12:01   ` Jasmine Hassan
2012-10-07  9:26     ` Ari Kuusava
2012-10-07 10:12       ` Arend van Spriel [this message]
2012-10-01 12:01   ` Arend van Spriel
2012-10-01 13:51 ` Dan Williams
2012-10-21  9:21   ` Jasmine Hassan
2012-10-21  9:23     ` Jasmine Hassan
     [not found]   ` <CAHbMyCa_yUO1XMFRrxAhDCkO+0T1Z5HaQgjhAK6cK2J729O7Cw@mail.gmail.com>
2012-10-25  3:53     ` Jasmine Hassan

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=50715599.9020708@broadcom.com \
    --to=arend@broadcom.com \
    --cc=arikuu@gmail.com \
    --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).