linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Mike Rapoport <mike@compulab.co.il>,
	Henry Ptasinski <henryp@broadcom.com>,
	devel@driverdev.osuosl.org, linux-wireless@vger.kernel.org
Subject: Re: [ANN] Full-source Broadcom wireless driver for 11n chips
Date: Wed, 15 Sep 2010 00:31:18 -0500	[thread overview]
Message-ID: <1284528678.10728.16.camel@dcbw.foobar.com> (raw)
In-Reply-To: <20100913154227.GB24563@kroah.com>

On Mon, 2010-09-13 at 08:42 -0700, Greg KH wrote:
> On Mon, Sep 13, 2010 at 09:59:48AM +0200, Mike Rapoport wrote:
> > 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?
> 
> I think those are supported by the broadcom driver in the android kernel
> trees, right?  If so, yes, there are plans for merging them into the
> main kernel tree, and any help you can provide would be appreciated.

That driver is convoluted; it's going to be a lot of work.  There are
simply too  many abstraction layers for one; I had to touch about 5
functions in 4 files just to get the driver to pass its 'struct device'
from the SDIO probe functions to where it called alloc_etherdev() so
that it called SET_NETDEV_DEV() so that its sysfs 'driver' link was
correctly set up.  I hope somebody is getting paid to do the cleanup :)

Dan



  parent reply	other threads:[~2010-09-15  5:28 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
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 [this message]
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=1284528678.10728.16.camel@dcbw.foobar.com \
    --to=dcbw@redhat.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=henryp@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mike@compulab.co.il \
    /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).