linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <mike@compulab.co.il>
To: Henry Ptasinski <henryp@broadcom.com>
Cc: devel@linuxdriverproject.org, linux-wireless@vger.kernel.org
Subject: Re: [ANN] Full-source Broadcom wireless driver for 11n chips
Date: Mon, 13 Sep 2010 09:59:48 +0200	[thread overview]
Message-ID: <4C8DD9F4.5090305@compulab.co.il> (raw)
In-Reply-To: <4C88F8CE.5090708@broadcom.com>

Hi Henry,

Henry Ptasinski wrote:
> Broadcom would like to announce the initial release of a fully-open
> Linux driver for it's latest generation of 11n chipsets.  The driver,
> while still a work in progress, is released as full source and uses the
> native mac80211 stack.   It supports multiple current chips (BCM4313,
> BCM43224, BCM43225) as well as providing a framework for supporting
> additional chips in the future, including mac80211-aware embedded chips.
>   The README and TODO files included with the sources provide more
> details about the current feature set, known issues, and plans for
> improving the driver.
> 
> The driver is currently available in staging-next git tree, available at:
> 
>     git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging-next-2.6.git 
> 
> 
> in the drivers/staging/brcm80211 directory.

Are there any plans to support BCM4319 and BCM4329 SDIO chipsets?

> ---
> Henry Ptasinski
> henryp@broadcom.com
> 
> -- 
> To unsubscribe from this list: send the line "unsubscribe 
> linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
Sincerely yours,
Mike.

  parent reply	other threads:[~2010-09-13  8:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100908150322.17dac9c3@nehalam>
     [not found] ` <20100908225132.GA12490@kroah.com>
2010-09-09 15:10   ` [ANN] Full-source Broadcom wireless driver for 11n chips Henry Ptasinski
2010-09-09 15:42     ` John W. Linville
2010-09-09 20:47     ` Nick Kossifidis
2010-09-10  6:49     ` Yuhong Bao
     [not found]       ` <AANLkTi=+pZm2bMZUFUsfTwNQHHBzM+yjmzNhim3+KRn0@mail.gmail.com>
2010-09-10  7:11         ` Yuhong Bao
2010-09-13  7:59     ` Mike Rapoport [this message]
2010-09-13 15:42       ` Greg KH
2010-09-13 18:58         ` Jason
2010-09-13 19:48           ` Greg KH
2010-09-15  5:31         ` Dan Williams
2010-09-13 17:36     ` Qasim Javed

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=4C8DD9F4.5090305@compulab.co.il \
    --to=mike@compulab.co.il \
    --cc=devel@linuxdriverproject.org \
    --cc=henryp@broadcom.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).