From: "Franky Lin" <frankyl@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>,
"Henry Ptasinski" <henryp@broadcom.com>,
"Roland Vossen" <rvossen@broadcom.com>,
"Arend Van Spriel" <arend@broadcom.com>,
"Kan Yan" <kanyan@broadcom.com>
Subject: Re: BCM4325 support in brcm80211 or newer versions of bcm4329 driver
Date: Sun, 14 Aug 2011 23:27:08 -0700 [thread overview]
Message-ID: <4E48BC3C.3030303@broadcom.com> (raw)
In-Reply-To: <1514181.3grperja2F@flatron>
On 08/14/2011 11:31 AM, Tomasz Figa wrote:
> 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.
Hi Tomasz,
RxCtrl time out is probably caused by Firmware crash. Based on your
description this is the most likely reason. A mismatch between host
driver and firmware is not recommended. Is it possible to switch to
bcm4329 or get a newer firmware/host driver?
Franky
next prev parent reply other threads:[~2011-08-15 6:27 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 [this message]
2011-08-15 11:02 ` Tomasz Figa
2011-08-22 22:13 ` Henry Ptasinski
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=4E48BC3C.3030303@broadcom.com \
--to=frankyl@broadcom.com \
--cc=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=henryp@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 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).