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>,
"Howard Harte" <hharte@broadcom.com>,
"Henry Ptasinski" <henryp@broadcom.com>
Subject: Re: BCM4325 support in brcm80211 or newer versions of bcm4329 driver
Date: Mon, 22 Aug 2011 16:17:52 -0700 [thread overview]
Message-ID: <20110822231752.GU2250@broadcom.com> (raw)
In-Reply-To: <1555247.YGCuatTnBA@flatron>
On Mon, Aug 22, 2011 at 04:02:40PM -0700, Tomasz Figa wrote:
> Thanks for your response.
>
> Well, I already found that this chip isn't supported yet. Basically, what I'm
> into is getting it or any other driver compatible with Linux 3.0 and
> Android 2.3 to work with our hardware. The problem is that the newest
> firmware-driver pair I can get for this chip is 4.217.95.x and it would require
> pretty much work to make it compatible with our software target, because
> the driver was designed for Linux 2.6.32 sources specific for this hardware
> with much hardcoding done.
>
> I'm already in contact with Franky Lin <frankyl@broadcom.com> about our issue,
> should I also discuss this topic with Howard?
Yes, please ping Howard for more assistance.
Thanks,
- Henry
prev parent reply other threads:[~2011-08-22 23:18 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
2011-08-22 23:02 ` Tomasz Figa
2011-08-22 23:17 ` Henry Ptasinski [this message]
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=20110822231752.GU2250@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.