Return-path: Received: from lager.deltatee.com ([207.54.116.66]:48358 "EHLO porter.deltatee.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751273Ab0GLFf2 (ORCPT ); Mon, 12 Jul 2010 01:35:28 -0400 Message-ID: <4C3AA99C.7030406@deltatee.com> Date: Sun, 11 Jul 2010 23:35:24 -0600 From: Logan Gunthorpe MIME-Version: 1.0 To: "Levi, Shahar" CC: "linux-wireless@vger.kernel.org" References: 1278578525.8576.19.camel@chilepepper <4C37BCA0.5090607@deltatee.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: wl1271 firmware Sender: linux-wireless-owner@vger.kernel.org List-ID: Shahar, Excellent news. Thank you very much. Logan Levi, Shahar wrote: >> -----Original Message----- >> From: linux-wireless-owner@vger.kernel.org [mailto:linux-wireless- >> owner@vger.kernel.org] On Behalf Of Logan Gunthorpe >> Sent: Saturday, July 10, 2010 3:20 AM >> To: Luciano Coelho >> Cc: linux-wireless@vger.kernel.org >> Subject: RE: wl1271 firmware >> >> Hi Everyone, >> >> I too am working with a WL1271 module and have just today got it >> connected to an Atmel ARM9 development kit (AT91SAM9G45-EKES). So far it >> appears to work but I have been gated by the firmware and NVS file issues. >> >> I have a firmware binary, but it seems to be a newer version >> (6.1.3.01.5) than what you are using. Does anyone have any idea if this >> version will work? It seems to be the only one available on TI's >> website. Additionally, our device manufacturer has been hesitant to >> provide any support because we are on an unsupported platform and opted >> to use the open source driver. Are there any other ways to obtain an >> older version of the firmware? >> >> The NVS file is another problem. TI's website has instructions to use a >> cryptic tool that appears to come with their driver package. There is no >> source for this tool and for obvious reasons would not work for us. >> >> Anyway, I'd like to help in anyway I can. I've taken a look at the >> twilan.ini file and I see the commonality with wl1271_ini.h. It would be >> relatively easy to write a tool that parses the INI file and generates >> the common part of the NVS file. However, I'd have no idea how to >> generate the device specific calibration or the few fields missing from >> the INI file. >> >> Thanks, >> >> Logan >> > > Hi Logan, > I am pushing to get access to the correct FW and NVS files version in TI web. I believe the community wills nave access of those files this week. > Regarding the tool to generate the NVS file in the correct format, I will check that and reply. > Regards, > Shahar > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html