From: "Levi, Shahar" <shahar_levi@ti.com>
To: Logan Gunthorpe <logang@deltatee.com>,
Luciano Coelho <luciano.coelho@nokia.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: wl1271 firmware
Date: Sun, 11 Jul 2010 07:38:33 +0200 [thread overview]
Message-ID: <AC090B9732AB2B4DB7FF476E907FE660010685F34E@dnce02.ent.ti.com> (raw)
In-Reply-To: <4C37BCA0.5090607@deltatee.com>
> -----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
next prev parent reply other threads:[~2010-07-11 5:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-10 0:19 wl1271 firmware Logan Gunthorpe
2010-07-11 5:38 ` Levi, Shahar [this message]
2010-07-12 5:35 ` Logan Gunthorpe
2010-07-16 21:41 ` Pazzo Da Legare
2010-07-17 12:20 ` Levi, Shahar
[not found] ` <AC090B9732AB2B4DB7FF476E907FE6600106966BA5@dnce02.ent.ti.com>
[not found] ` <4C45ED36.2090604@deltatee.com>
2010-07-21 17:01 ` Pazzo Da Legare
2010-07-21 17:27 ` Pazzo Da Legare
2010-07-22 6:40 ` Luciano Coelho
2010-07-22 15:41 ` Pazzo Da Legare
2010-07-22 16:34 ` Luciano Coelho
2010-07-23 23:19 ` Pazzo Da Legare
2010-07-31 13:23 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2010-06-30 11:26 Pazzo Da Legare
2010-06-30 13:42 ` Levi, Shahar
2010-07-01 7:36 ` Pazzo Da Legare
2010-07-02 9:47 ` max
2010-07-02 9:54 ` mastupristi
2010-07-05 7:36 ` Pazzo Da Legare
2010-07-05 16:49 ` Pazzo Da Legare
2010-07-06 12:28 ` Levi, Shahar
2010-07-08 8:42 ` Luciano Coelho
2010-07-06 11:55 ` Levi, Shahar
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=AC090B9732AB2B4DB7FF476E907FE660010685F34E@dnce02.ent.ti.com \
--to=shahar_levi@ti.com \
--cc=linux-wireless@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=luciano.coelho@nokia.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).