From: Brian Gix <bgix@codeaurora.org>
To: johan.hedberg@gmail.com
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: Add address type to mgmt_pair_device
Date: Thu, 10 Nov 2011 14:15:38 -0800 [thread overview]
Message-ID: <4EBC4D0A.7070704@codeaurora.org> (raw)
In-Reply-To: <1320962855-19036-1-git-send-email-johan.hedberg@gmail.com>
Hi Johan,
On 11/10/2011 2:07 PM, johan.hedberg@gmail.com wrote:
>
> - entry = hci_find_adv_entry(hdev,&cp->bdaddr);
> - if (entry)
> - conn = hci_connect(hdev, LE_LINK,&cp->bdaddr, sec_level,
> + if (cp->addr.type == MGMT_ADDR_BREDR)
> + conn = hci_connect(hdev, ACL_LINK,&cp->addr.bdaddr, sec_level,
> auth_type);
> else
> - conn = hci_connect(hdev, ACL_LINK,&cp->bdaddr, sec_level,
> + conn = hci_connect(hdev, LE_LINK,&cp->addr.bdaddr, sec_level,
> auth_type);
>
Are we differentiating between Dual Mode and BR/EDR here? If we are, we
may want to reverse the logic so that it connects with an LE_LINK if the
addr type == MGMT_ADDR_LE, and then connects to an ACL_LINK otherwise
(as the else).
Unless this is being implimented as a bitmask, in which case the if
would be "if (cp->addr.type & MGMT_ADDR_BREDR)", at which point I have
no objection.
Because of course Dual mode devices must use the ACL_LINK between each
other.
--
Brian Gix
bgix@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2011-11-10 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 22:07 [PATCH 1/2] Bluetooth: Add address type to mgmt_pair_device johan.hedberg
2011-11-10 22:07 ` [PATCH 2/2] Bluetooth: Fix mgmt_pair_device imediate error responses johan.hedberg
2011-11-16 18:00 ` Gustavo Padovan
2011-11-10 22:15 ` Brian Gix [this message]
2011-11-10 22:33 ` [PATCH 1/2] Bluetooth: Add address type to mgmt_pair_device Johan Hedberg
2011-11-10 22:37 ` Brian Gix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EBC4D0A.7070704@codeaurora.org \
--to=bgix@codeaurora.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.