Re: Advertising cache and random address support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Claudio

Thanks for clarifying on passive scanning will wait for Andre's
patches on the same.

Yes we are using Android platform, I will try to go through the
proximity API's and get back in case of any comments

Regards
Vishwanath

On Mon, Aug 1, 2011 at 11:16 PM, Claudio Takahasi
<claudio.takahasi@xxxxxxxxxxxxx> wrote:
>
> Hi Vishwanath,
>
> On Mon, Aug 1, 2011 at 10:29 AM, VISHWANATH KM <a21174@xxxxxxxxxxxx> wrote:
> > Hi,
> >
> > Advertising cache seem to temporarily store the peer_addr_type info,
> > if we reboot, then we loose the information and subsequent connection
> > fails as we don't have the peer_addr_type, unless we re-scan
>
> we are aware about this limitation. Andre Guedes is already working on it.
>
> >
> > The better approach may be
> > 1) bluez while receiving the advertising events would also store the
> > peer_addr_type info ( may be in dev_info structure in hciops )
> > 2) while initiating connection bluez may pass the peer_addr_type as
> > part of  bt_io_connect in l2cap_connect (attrib/client.c) as part of
> > new option BT_IO_OPT_
> >
> > Please let me know your comments on above, or if any better
> > approaches/alternatives on the same, thx
>
> We are trying to keep the consistency between Basic Rate and BLE,
> avoiding transport specific parameters in the Bluetooth socket
> operations.
> Passive scanning needs to be executed if the address is not found in
> the cache, otherwise re-connections will not work. In BlueZ it is
> necessary to address multiple connections, so probably the final
> solution will use passive scanning "together" with LE create
> connection(using whitelist or general connection procedure). Remember
> that address resolution is handled by the host, this is another
> argument to implement passive scanning in the kernel.
>
> Are you working in the Android team? I'd be good cooperation and
> interoperability tests.
> I sent some Proximity patches to the ML, let me know if you have
> comments about the proposed Proximity API changes and the
> implementation. You can find the git repository address in the email
> that I sent last week: "Current status on BLE development".
>
> Regards,
> Claudio.
>
> >
> > Regards
> > Vishwanath
--
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


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux