Return-Path: Date: Tue, 15 Mar 2011 09:57:42 +0200 From: Ville Tervo To: ext Andre Guedes Cc: linux-bluetooth@vger.kernel.org Subject: Re: [RFC v2 0/6] LE advertising cache Message-ID: <20110315075742.GD4369@null> References: <1299850377-3734-1-git-send-email-andre.guedes@openbossa.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: <1299850377-3734-1-git-send-email-andre.guedes@openbossa.org> Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi, On Fri, Mar 11, 2011 at 10:32:51AM -0300, ext Andre Guedes wrote: > During a LE connection establishment, the host should be able to infer the > bdaddr type from a given bdaddr. > > To achieve that, during the LE scanning, the host stores the bdaddr and the > bdaddr type gathered from advertising reports. The host keeps a list of > advertising entry (bdaddr and bdaddr_type) for later lookup. This list will > be called Advertising Cache. > > Since the penality to connect to an unreachable device is relatively high, > we must keep only fresh advertising entries on the advertising cache. So, > before each LE scanning the advertising cache is cleared. Also, after the LE > scanning, a timer is set to clear the cache. I tested these pathes with a device which had random address. Connection works which is good. How ever I'm not yet sure if mandatory scanning before every connect is acceptable. I have been playing with idea to derive address type from msb bits of the address. Any ideaѕ what would lose in that way? -- Ville