Hi Ville, On Wed, Mar 16, 2011 at 1:53 AM, Ville Tervo <ville.tervo@xxxxxxxxx> wrote: > On Tue, Mar 15, 2011 at 10:41:55AM -0400, ext Anderson Lizardo wrote: >> IIRC the connection procedure defined on the spec requires this scan. >> See for instance the general connection establishment procedure at >> page 1715 > > But it makes "Direct Connection Establishment" impossible. I can only see on the spec "Direct Connection Establishment" allowed to be used as sub-procedures for either General or Selective connection establishment. Correct me if you find other references outside these two procedures. The problem is that, unlike BR/EDR where the address is enough, for LE you need to know the address type as well before connecting and this information can only be obtained by means of advertising reports (from a scanning during discovery, or from previously bonded devices, for which we need to have stored this information). Also see this note regarding privacy-enabled peripherals (page 1704): "A Central may connect to a Peripheral that supports the privacy feature using only the general connection establishment procedure." (I'm not sure I get this sentence right, as it uses the dubious "may ... only" sentence). > Is it needed to pass PTS for example? Note sure. Claudio may know more about PTS requirements on GAP part. Regards, -- Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
