Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752176AbdHJH5A (ORCPT ); Thu, 10 Aug 2017 03:57:00 -0400 Received: from lelnx193.ext.ti.com ([198.47.27.77]:40028 "EHLO lelnx193.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751361AbdHJH46 (ORCPT ); Thu, 10 Aug 2017 03:56:58 -0400 From: "Reizer, Eyal" To: Julian Calaby CC: Tony Lindgren , Kalle Valo , "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "sebastian.reichel@collabora.co.uk" Subject: RE: [v6] wlcore: add missing nvs file name info for wilink8 Thread-Topic: [v6] wlcore: add missing nvs file name info for wilink8 Thread-Index: AQHTEOPJBSumwybcskWe/+8ZG1iekaJ7ph6QgAB/9ACAACTrJoAAGzEAgAC58SD///evAIAAIcUA Date: Thu, 10 Aug 2017 07:56:49 +0000 Message-ID: <8665E2433BC68541A24DFFCA87B70F5B36422E83@DFRE01.ent.ti.com> References: <1502264840-10569-1-git-send-email-eyalr@ti.com> <8665E2433BC68541A24DFFCA87B70F5B36420E5A@DFRE01.ent.ti.com> <20170809172651.GA3934@atomide.com> <20170809211620.GF3934@atomide.com> <8665E2433BC68541A24DFFCA87B70F5B36422C65@DFRE01.ent.ti.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.167.188.94] x-exclaimer-md-config: f9c360f5-3d1e-4c3c-8703-f45bf52eff6b Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id v7A7v5di030535 Content-Length: 962 Lines: 28 > > On Thu, Aug 10, 2017 at 4:35 PM, Reizer, Eyal wrote: > >> > > >> > Sorry for top posting (mobile...) > >> > I have verified with system design and the data sheet that every wilink > 6/7 > >> chip has a mac address in fuse so probably the board you have (pretty old, > >> right?) has this mac address in fuse. Maybe it was from very early > batches? > >> Anyway I see no reason to change it. > >> > Anyway the calibrator can be used to store a different one into the nvs > file > >> that will overide it. > >> > >> Well clearly at least this one does not have any valid hardware > >> mac address, the hardware mac address is broken with all zeroes. > >> > > > > Looks like it is not really all zeros but rather 00:00:00:00:00:01. > > I wonder if it is just a one board issue or not... > > It's 00:00:00:00:00:01 because your code adds 1 to it. > You are right of course! I saw it as well after sending my previous reply. Best Regards, Eyal