From: "Arend van Spriel" <arend@broadcom.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Jasmine Hassan" <jasmine.aura@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [Kernel Bug] 3.6, wpasupplicant 1.0, broadcom-sta 6.20.55.19
Date: Mon, 1 Oct 2012 14:01:44 +0200 [thread overview]
Message-ID: <50698628.9050800@broadcom.com> (raw)
In-Reply-To: <20121001113456.GA31313@tuxdriver.com>
On 10/01/2012 01:34 PM, John W. Linville wrote:
> Why aren't you using brcmsmac?
>
Because the chip is bcm43142. No support for that in brcmsmac.
Gr. AvS
next prev parent reply other threads:[~2012-10-01 12:01 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
2012-10-01 12:01 ` Arend van Spriel [this message]
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=50698628.9050800@broadcom.com \
--to=arend@broadcom.com \
--cc=jasmine.aura@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).