linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "M. Lambert" <lambertm@westman.wave.ca>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: bcm43236 chipset
Date: Mon, 30 Jan 2012 12:16:45 +0100	[thread overview]
Message-ID: <4F267C1D.40704@broadcom.com> (raw)
In-Reply-To: <1327859778.27653.5.camel@localhost>

On 01/29/2012 06:56 PM, M. Lambert wrote:
> Good morning,
> 
> I have seen a couple of posts where reference was made to usb support in
> broadcom drivers, and that the code would also support additional
> chipsets (such as the bcm43236 but not the 43231) when quote "my testing
> here is complete" unquote.

That is my line ;-) I am indeed testing/tinkering on adding USB support
to the brcmfmac driver with bcm43236 as chipset.

> As I have a Linksys AE2500 (13b1:003a) usb dongle, I am very interested
> in helping test this functionality no matter how reliable it is, or is
> not at this time.  Using Fedora 16 x64, kernel 3.2.2-1 at this time.  I
> believe I'd have to build my own kernel to enable bcma support but not
> positive about that yet.

BCMA is only needed for the brcmsmac driver. So no need to enable it.

> If the driver is near a point where testing by others with certain
> hardware could be helpful and/or useful I'd be happy to test and provide
> any feedback.

Thanks. I hope to submit the patch this week.

Gr. AvS


      reply	other threads:[~2012-01-30 11:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-29 17:56 bcm43236 chipset M. Lambert
2012-01-30 11:16 ` Arend van Spriel [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=4F267C1D.40704@broadcom.com \
    --to=arend@broadcom.com \
    --cc=lambertm@westman.wave.ca \
    --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).