linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Henry Ptasinski" <henryp@broadcom.com>
To: Jason <linuxdriverproject@lakedaemon.net>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"Howard Harte" <hharte@broadcom.com>,
	"gregkh@suse.de" <gregkh@suse.de>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"Henry Ptasinski" <henryp@broadcom.com>
Subject: Re: [PATCH 00/14] staging: brcm80211: brcmfmac driver cleanup
Date: Fri, 26 Aug 2011 13:15:34 -0700	[thread overview]
Message-ID: <20110826201534.GR4888@broadcom.com> (raw)
In-Reply-To: <20110826200057.GM29321@titan.lakedaemon.net>

On Fri, Aug 26, 2011 at 01:00:57PM -0700, Jason wrote:
> On Fri, Aug 26, 2011 at 10:44:46AM -0700, Henry Ptasinski wrote:
> > On Fri, Aug 26, 2011 at 10:38:55AM -0700, Jason wrote:
> > > On Fri, Aug 26, 2011 at 10:31:59AM -0700, Henry Ptasinski wrote:
> > > > A possibly better approach would be a device with a BCM4329 on the
> > > > motherboard (e.g. table, phone, etc) that can run a relatively stock
> > > > linux kernel.  However, I don't know of a specific platform at the
> > > > moment to recommend.
> > > 
> > > Nexus One phone?
> > 
> > That's a possibility.  Are people running recent, relatively unmodified linux
> > kernels on the Nexus One?  (Or you could backport brcmfmac to the Android
> > version of the kernel, perhaps using compat-wireless).
> 
> folks run debian from the sdcard [1], a mainline kernel shouldn't be too
> big of a stretch from there.  Especially if the purpose is for testing
> wifi.  Don't need PM, GSM, display, 3D, etc for that.
> 
> Note, I haven't tried it yet, myself.  It's been on the _long_ list of
> projects.  It would be higher on the list if brcmfmac supported all the
> normal Linux features like monitor mode, AP mode, multiple-VAPs, etc.
> Or, at least, was in mainline and would accept patches adding such
> features... ;-)

Would definitely accept patches for such features!  We're definitely interested
in them, and they're all on our list to add, but crossing the chasm is the
first step.

- Henry


  reply	other threads:[~2011-08-26 20:15 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 13:34 [PATCH 00/14] staging: brcm80211: brcmfmac driver cleanup Arend van Spriel
2011-08-12 13:34 ` [PATCH 01/14] staging: brcm80211: use wait queues instead of semaphores in wl_cfg80211.c Arend van Spriel
2011-08-12 14:07   ` Rafał Miłecki
2011-08-12 16:44     ` Arend van Spriel
2011-08-12 18:55       ` Arend van Spriel
2011-08-12 18:59         ` Johannes Berg
2011-08-12 18:59       ` Franky Lin
2011-08-12 19:08         ` Larry Finger
2011-08-12 19:10           ` Arend van Spriel
2011-08-16 20:27         ` Rafał Miłecki
2011-08-12 19:05   ` [PATCHv2 " Arend van Spriel
2011-08-12 19:07     ` Arend van Spriel
2011-08-12 19:09       ` Arend van Spriel
2011-08-16 17:56         ` Dan Carpenter
2011-08-12 13:34 ` [PATCH 02/14] staging: brcm80211: remove iovar IOV_BLOCKSIZE in brcmfmac Arend van Spriel
2011-08-12 14:12   ` Rafał Miłecki
2011-08-12 16:37     ` Arend van Spriel
2011-08-12 20:02       ` Rafał Miłecki
2011-08-12 13:34 ` [PATCH 03/14] staging: brcm80211: remove struct sdioh_info from brcmfmac Arend van Spriel
2011-08-12 13:34 ` [PATCH 04/14] staging: brcm80211: remove global var gInstance " Arend van Spriel
2011-08-12 13:34 ` [PATCH 05/14] staging: brcm80211: remove wext traces in fullmac Arend van Spriel
2011-08-12 13:34 ` [PATCH 06/14] staging: brcm80211: absorb brcmf_sdioh_iovar_op into brcmf_sdcard_iovar_op Arend van Spriel
2011-08-12 13:34 ` [PATCH 07/14] staging: brcm80211: absorb brcmf_sdioh_interrupt_register into brcmf_sdcard_intr_reg Arend van Spriel
2011-08-12 14:31   ` Rafał Miłecki
2011-08-12 13:34 ` [PATCH 08/14] staging: brcm80211: absorb brcmf_sdioh_interrupt_deregister into brcmf_sdcard_intr_dereg Arend van Spriel
2011-08-12 13:34 ` [PATCH 09/14] staging: brcm80211: absorb brcmf_sdioh_abort into brcmf_sdcard_abort Arend van Spriel
2011-08-12 13:34 ` [PATCH 10/14] staging: brcm80211: remove dead code from dhd_sdio.c Arend van Spriel
2011-08-12 13:34 ` [PATCH 11/14] staging: brcm80211: remove wrapper functions in bcmsdh_sdmmc.c Arend van Spriel
2011-08-12 13:34 ` [PATCH 12/14] staging: brcm80211: remove unused parameter from data interface in fullmac Arend van Spriel
2011-08-12 13:35 ` [PATCH 13/14] staging: brcm80211: remove dead SDTEST code from fullmac Arend van Spriel
2011-08-12 13:35 ` [PATCH 14/14] staging: brcm80211: remove unused func parameter in wl_cfg80211 of fullmac Arend van Spriel
2011-08-12 14:02 ` [PATCH 00/14] staging: brcm80211: brcmfmac driver cleanup Rafał Miłecki
2011-08-12 15:14   ` Hauke Mehrtens
2011-08-12 15:43     ` Rafał Miłecki
2011-08-12 16:32   ` Arend van Spriel
2011-08-12 20:04     ` Rafał Miłecki
2011-08-13  7:47       ` Arend van Spriel
2011-08-13  8:30         ` Rafał Miłecki
2011-08-26  9:20       ` Rafał Miłecki
2011-08-26 17:31         ` Henry Ptasinski
2011-08-26 17:38           ` Jason
2011-08-26 17:44             ` Henry Ptasinski
2011-08-26 20:00               ` Jason
2011-08-26 20:15                 ` Henry Ptasinski [this message]
2011-08-23 20:07 ` Greg KH

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=20110826201534.GR4888@broadcom.com \
    --to=henryp@broadcom.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@suse.de \
    --cc=hharte@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linuxdriverproject@lakedaemon.net \
    --cc=zajec5@gmail.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).