From: "Pali Rohár" <pali.rohar@gmail.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: Gery Kahn <gery.kahn@gmail.com>, Shahar Lev <shahar@wizery.com>,
Kalle Valo <kvalo@codeaurora.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Pavel Machek <pavel@ucw.cz>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
Subject: Re: wl1251 NVS calibration data format
Date: Sat, 24 Dec 2016 13:57:52 +0100 [thread overview]
Message-ID: <201612241357.52086@pali> (raw)
In-Reply-To: <201612171214.50820@pali>
[-- Attachment #1: Type: Text/Plain, Size: 921 bytes --]
On Saturday 17 December 2016 12:14:50 Pali Rohár wrote:
> I will try to play with driver if it is really truth!
>
> I already looked into original TI's multiplatform HAL driver for
> wl1251 chip (big mess) and found there that there is wl1251 command
> to read mac address from chip. It could be done by this wl1251
> function:
>
> wl1251_cmd_interrogate(wl, DOT11_STATION_ID, mac, sizeof(*mac))
>
> (same id as for setting permanent mac address, but opposite to read
> it)
Confirmed! Calling that function (before setting real linux mac address)
returns MAC address 00:00:20:07:03:09.
Changing NVS data at position 0x1c-0x21 changes also what above function
returns.
So really at position 0x1c-0x21 in NVS data is stored MAC address (in
reverse order). Just default is some unknown 00:00:20:07:03:09.
So MAC address is really part of NVS data.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2016-12-24 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 11:01 wl1251 NVS calibration data format Pali Rohár
2016-12-16 11:12 ` Pali Rohár
2016-12-17 9:37 ` Sebastian Reichel
2016-12-17 11:14 ` Pali Rohár
2016-12-17 12:03 ` Sebastian Reichel
2016-12-17 13:10 ` MAC address in wl1251 NVS data (Was: Re: wl1251 NVS calibration data format) Pali Rohár
2016-12-24 12:57 ` Pali Rohár [this message]
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=201612241357.52086@pali \
--to=pali.rohar@gmail.com \
--cc=gery.kahn@gmail.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=shahar@wizery.com \
--cc=sre@kernel.org \
/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).