archive mirror
 help / color / mirror / Atom feed
From: Luciano Coelho <>
To: "ext Levi, Shahar" <>
Cc: Pazzo Da Legare <>,
	"" <>
Subject: RE: wl1271 firmware
Date: Thu, 08 Jul 2010 11:42:05 +0300	[thread overview]
Message-ID: <1278578525.8576.19.camel@chilepepper> (raw)
In-Reply-To: <>


On Tue, 2010-07-06 at 14:28 +0200, ext Levi, Shahar wrote:
> > I start from tiwlan.ini file for tiwlan driver to produce an nvs file.
> > Could you please indicate values to use for the following parameters
> > of struct wl1271_nvs_file: general_params.srf1[],
> > general_params.srf2[], general_params.srf3[],
> > dyn_radio_params_2[].params.degraded_low_to_normal_thr,
> > dyn_radio_params_2[].params.normal_to_degraded_high_thr,
> > dyn_radio_params_5[i].params.degraded_low_to_normal_thr,
> > dyn_radio_params_5[i].params.normal_to_degraded_high_thr
> Hi,
> The tiwlan driver ini&NVS files has a different stature then the mac80211 NVS. The parameters you mentioned are RF parameters. 
> I believe it will be the best to get the NVS that mach to the mac80211 (that I am pushing to get).
> Regards,
> Shahar  

You need to get the firmware (wl1271-fw.bin) directly from TI or from
your device manufacturer.  I don't have the permission to redistribute
it.  The latest version that we are using is Rev. (you can
check this by running strings on and grepping the binary file).

The NVS file is another story.  It contains device-specific calibration
values and you should probably get those from the device manufacturer.
There is a common part (which is the INI file in tiwlan's terms), which
you need to use to create the binary (check wl1271_ini.h for the binary
file structure).  The more problematic part is the device-specific self
generated calibration.  You need to run a specific sequence of commands
in order to get these values and then apply these values to the correct
place in the binary file.

Shahar, maybe you could contribute a tool to generate the NVS file in
the correct format for wl1271? That would be very cool and would help
lots of people.  Please let me know if you have interest and we can
discuss this in more details.


  reply	other threads:[~2010-07-08  8:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30 11:26 wl1271 firmware 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 [this message]
2010-07-06 11:55     ` Levi, Shahar
2010-07-10  0:19 Logan Gunthorpe
2010-07-11  5:38 ` Levi, Shahar
2010-07-12  5:35   ` Logan Gunthorpe
2010-07-16 21:41   ` Pazzo Da Legare
2010-07-17 12:20     ` Levi, Shahar
     [not found]       ` <>
     [not found]         ` <>
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

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1278578525.8576.19.camel@chilepepper \ \ \ \ \

* 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).