Date:   Thu, 20 Dec 2018 19:19:05 +0100
From:   Michal Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com>
To:     "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Advertising report address types in mesh-io-generic
Message-ID: <20181220181905.3r4fv45qe3y6sq75@kynes>
Mail-Followup-To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
References: <20181220161707.lxrzzvknqa64pmyc@kynes>
 <DEBB0CAA2616974FAE35E4B560B9A4375D8E337C@ORSMSX101.amr.corp.intel.com>
 <20181220180318.gwsj6aflihlppbgu@kynes>
 <DEBB0CAA2616974FAE35E4B560B9A4375D8E351D@ORSMSX101.amr.corp.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <DEBB0CAA2616974FAE35E4B560B9A4375D8E351D@ORSMSX101.amr.corp.intel.com>
User-Agent: NeoMutt/20180716
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

On 12/20, Gix, Brian wrote:
> > says that "address type" in that event is one of:
> > 
> > 0x00 Public Device Address
> > 0x01 Random Device Address
> > 0x02 Public Identity Address (Corresponds to Resolved Private Address)
> > 0x03 Random (static) Identity Address (Corresponds to Resolved Private
> >      Address)
> > 
> > and nowhere does it mention BR/EDR.
> > 
> > I don't think we're supposed to even receive BR/EDR addresses via HCI LE
> > Meta Event.
> 
> I think you are probably correct.  This may be a remnant that we picked up from code that was
> intended to serve both BR/EDR and LE advertisements.  I will remove that check first thing after 
> the existing patchset is applied.
Thanks! \o/

Thanks for the work by the way, we're still digging into the codebase
and getting our heads around it, but I'll make sure to give you folks a
hand when we finally manage to add something substantial.

cheers
-- 
Michał Lowas-Rzechonek <michal.lowas-rzechonek@silvair.com>
Silvair http://silvair.com
Jasnogórska 44, 31-358 Krakow, POLAND