linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manuel Naranjo <manuel@aircable.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] CreateBonding while periodic scanning
Date: Mon, 03 Mar 2008 10:52:53 -0200	[thread overview]
Message-ID: <47CBF4A5.1050308@aircable.net> (raw)
In-Reply-To: <47AFAE50.1040508@aircable.net>

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

It's me or this mail passed through the list without much glory :S.
> Sorry I forgot the patch.
>
> I confirmed the patch worked for an old Broadcom based dongle (D-Link
> BT122) and for a CSR Bluecore 4 based dongle (AIRcable Host XR).
>
> The patch should apply against the bluez-utils-3.26 vanilla package
>   
>> Hello List,
>>
>> As I asked in the forums I'm trying to create a bonding to a device
>> while I'm running a periodic scanning.
>>
>> Thing is that for some reason hcid is blocking me to do this, and Marcel
>> suggested removing the periodic inquiry check. But as he said, and I
>> think the same, that check was created for a reason.
>>
>> The line that makes the conflict is this one (utils/hcid/adapter.c:
>>
>> static DBusHandlerResult adapter_create_bonding(DBusConnection *conn,
>>                                                 DBusMessage *msg, void
>> *data)
>> .....
>>
>> if (adapter->discov_active || (adapter->pdiscov_active &&
>> !adapter->pinq_idle))
>> return error_discover_in_progress(conn, msg)
>>
>> pinq_idle is 0 in my case, so then I get a discovery in progress exception.
>>
>> Marcel suggested that I change the code to "if (adapter->discov_active
>> )" but still we would like to know what that check is made, so we can
>> get a better solution.
>>
>> Thanks,
>> Manuel Naranjo
>> Wireless Cables Inc.
>>
>>
>>   
>>     
>
>   


[-- Attachment #2: adapter.patch --]
[-- Type: text/x-patch, Size: 443 bytes --]

--- adapter.c.orig	2008-02-01 21:16:31.000000000 -0200
+++ adapter.c	2008-02-10 23:50:31.000000000 -0200
@@ -2216,7 +2216,7 @@
 	str2ba(peer_addr, &peer_bdaddr);
 
 	/* check if there is a pending discover: requested by D-Bus/non clients */
-	if (adapter->discov_active || (adapter->pdiscov_active && !adapter->pinq_idle))
+	if (adapter->discov_active)
 		return error_discover_in_progress(conn, msg);
 
 	pending_remote_name_cancel(adapter);

[-- Attachment #3: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2008-03-03 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11  1:49 [Bluez-devel] CreateBonding while periodic scanning Manuel Naranjo
2008-02-11  2:09 ` Manuel Naranjo
2008-03-03 12:52   ` Manuel Naranjo [this message]

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=47CBF4A5.1050308@aircable.net \
    --to=manuel@aircable.net \
    --cc=bluez-devel@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).