From: Tony Lindgren <tony@atomide.com>
To: "Reizer, Eyal" <eyalr@ti.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"sebastian.reichel@collabora.co.uk"
<sebastian.reichel@collabora.co.uk>
Subject: Re: [v3] wlcore: add missing nvs file name info for wilink8
Date: Tue, 25 Jul 2017 04:58:06 -0700 [thread overview]
Message-ID: <20170725115805.GU10026@atomide.com> (raw)
In-Reply-To: <8665E2433BC68541A24DFFCA87B70F5B3640DDC7@DFRE01.ent.ti.com>
* Reizer, Eyal <eyalr@ti.com> [170725 04:33]:
> > From: Tony Lindgren [mailto:tony@atomide.com]
> > Hmm so why would we ever even use this bogus nvs file? In addition to
> > warning,
> > I think we should just ignore the bogus nvs file completely.
> >
> While it looks bogus, it is still at least a valid mac address and the chip will function
> Using it.
> Wilink6/7 doesn't have a default mac address in hardware (wilink8 does have one)
> so we need to assign one for it so It can work, even if not optimally until configured
> using the calibrator tool and a unique mac address is assigned to it.
But it's not a unique mac address. What we should do in that case is
use a random mac address just like many USB devices do.
Regards,
Tony
prev parent reply other threads:[~2017-07-25 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 12:16 [v3] wlcore: add missing nvs file name info for wilink8 Reizer, Eyal
2017-07-20 12:16 ` Reizer, Eyal
2017-07-25 10:22 ` Tony Lindgren
2017-07-25 11:32 ` Reizer, Eyal
2017-07-25 11:32 ` Reizer, Eyal
2017-07-25 11:58 ` Tony Lindgren [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=20170725115805.GU10026@atomide.com \
--to=tony@atomide.com \
--cc=eyalr@ti.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sebastian.reichel@collabora.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.