All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Henry Ptasinski" <henryp@broadcom.com>
To: "Tomasz Figa" <tomasz.figa@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Brett Rudley" <brudley@broadcom.com>,
	"Roland Vossen" <rvossen@broadcom.com>,
	"Arend Van Spriel" <arend@broadcom.com>,
	"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
	"Kan Yan" <kanyan@broadcom.com>,
	"Henry Ptasinski" <henryp@broadcom.com>,
	hharte@broadcom.com
Subject: Re: BCM4325 support in brcm80211 or newer versions of bcm4329 driver
Date: Mon, 22 Aug 2011 15:13:52 -0700	[thread overview]
Message-ID: <20110822221352.GJ2250@broadcom.com> (raw)
In-Reply-To: <1514181.3grperja2F@flatron>

On Sun, Aug 14, 2011 at 11:31:09AM -0700, Tomasz Figa wrote:
> Hi,
> 
> I'm looking into running current Linux kernel on a platform equipped with the
> BCM4325 full mac combo chip, but unfortunately the shipped DHD driver (v.
> 4.217.*) is outdated and designed for stock 2.6.29 kernel with much hardcoding
> done to glue everything together.
> 
> I did some reasearch and it led me to a newer version of the DHD driver,
> designed for BCM4329 (v. 4.218), which after some modifications (BCD protocol
> version 2, some event IDs, etc.) started to work on my hardware, with one
> exception: waiting for RxCtrl after sending an "iscanresults" request times
> out. I'm attaching driver debug output at the bottom of this message.
> 
> A bit more details about my hardware: a Samsung S3C6410-based board connected
> to a BCM4325 chip using 4-bit SDIO interface, without dedicated IRQ pin (using
> SDIO IRQ feature), so undefining of OOB_INTR_ONLY and HW_OOB and defining of
> SDIO_ISR_THREAD was needed.
> 
> Do you have any suggestions?

Tom,

The brcmfmac driver (in staging) doesn't yet support the BCM4325.  As you
found, there are a variety of older driver sources available in other repos.
You can contact Howard Harte <hharte@broadcom.com> to see about a combination
of those sources and firmware that will support your platform in the near term.

- Henry



  parent reply	other threads:[~2011-08-22 22:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-14 18:31 BCM4325 support in brcm80211 or newer versions of bcm4329 driver Tomasz Figa
2011-08-15  6:27 ` Franky Lin
2011-08-15 11:02   ` Tomasz Figa
2011-08-22 22:13 ` Henry Ptasinski [this message]
2011-08-22 23:02   ` Tomasz Figa
2011-08-22 23:17     ` Henry Ptasinski

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=20110822221352.GJ2250@broadcom.com \
    --to=henryp@broadcom.com \
    --cc=arend@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=frankyl@broadcom.com \
    --cc=hharte@broadcom.com \
    --cc=kanyan@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rvossen@broadcom.com \
    --cc=tomasz.figa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.