Return-path: Received: from mms2.broadcom.com ([216.31.210.18]:2251 "EHLO mms2.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753373Ab1KUXmR convert rfc822-to-8bit (ORCPT ); Mon, 21 Nov 2011 18:42:17 -0500 From: "Howard Harte" To: =?iso-8859-1?Q?Thomas_Lang=E5s?= , "Franky (Zhenhui) Lin" cc: "Arend Van Spriel" , "linux-wireless@vger.kernel.org" Date: Mon, 21 Nov 2011 15:42:08 -0800 Subject: RE: brcm80211 (with bcm4329-chip) Message-ID: <4F34EB345A846E42B8D432EA578382CC154E402FB4@SJEXCHCCR01.corp.ad.broadcom.com> (sfid-20111122_004220_783985_17D0CB65) References: <4ECA8908.7070304@broadcom.com> <4ECA98DB.4030608@broadcom.com> <4ECAAD6C.4080103@broadcom.com> <4ECAC99B.8090507@broadcom.com> <4ECAD52A.6050509@broadcom.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hello Thomas, The max clock speed supported by 4329 is 50MHz. -Howard -----Original Message----- From: Thomas Lang?s [mailto:thomas.langas@fxitech.com] Sent: Monday, November 21, 2011 3:41 PM To: Franky (Zhenhui) Lin Cc: Arend Van Spriel; linux-wireless@vger.kernel.org; Howard Harte Subject: Re: brcm80211 (with bcm4329-chip) On Mon, Nov 21, 2011 at 11:48 PM, Franky Lin wrote: > I think both firmware is fine. I was referring to the > brcm/bcm4329-fullmac-4.txt It's a nvram file contains critical information > used by firmware. And it's hardware dependent. We have submitted a patch to > remove the one in Linux firmware repository to avoid confusion as it's for a > Broadcom internal development board. It may not work with your set up. I > think there should be a similar file comes with the proprietary driver > package if you are using a module instead of a 4329 chip. Please use that > one. I did two tests one with only changing the nvram-file, and one with changing both the firmware and the nvram-file (this is the latest logfile you got). Both had the same result. > I don't have Exynos 4210 spec. But I guess for a such new chip the SDIO host > should be able to run the bus at 50MHz. You could try to hack the MMC/SDIO > host driver and reduce the max frequency to 25MHz or even further to 12MHz > to see if any improvement. Max clock is 63MHz, and the setting we have now works with 2.6.36 and the proprietary driver (bcm4329). Looking at the platform-code we have for 2.6.x, I see that we set .cd_type = S3C_SDHCI_CD_GPIO, Instead of .cd_type = S3C_SDHCI_CD_INTERNAL, I don't know if this matters (looking at the schematics, the clk-pin is the same for mmc2 as it is for the gpio). Is this something related to the old proprietary driver? Regards, Thomas