Return-path: Received: from mms3.broadcom.com ([216.31.210.19]:3729 "EHLO MMS3.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754504Ab1HVXSC (ORCPT ); Mon, 22 Aug 2011 19:18:02 -0400 Date: Mon, 22 Aug 2011 16:17:52 -0700 From: "Henry Ptasinski" To: "Tomasz Figa" cc: "linux-wireless@vger.kernel.org" , "Brett Rudley" , "Roland Vossen" , "Arend Van Spriel" , "Franky (Zhenhui) Lin" , "Kan Yan" , "Howard Harte" , "Henry Ptasinski" Subject: Re: BCM4325 support in brcm80211 or newer versions of bcm4329 driver Message-ID: <20110822231752.GU2250@broadcom.com> (sfid-20110823_011808_414185_52EA6610) References: <1514181.3grperja2F@flatron> <20110822221352.GJ2250@broadcom.com> <1555247.YGCuatTnBA@flatron> MIME-Version: 1.0 In-Reply-To: <1555247.YGCuatTnBA@flatron> Content-Type: text/plain; charset=us-ascii Sender: linux-wireless-owner@vger.kernel.org List-ID: 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 about our issue, > should I also discuss this topic with Howard? Yes, please ping Howard for more assistance. Thanks, - Henry