linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Agustin Jose Fusaro <afusaro@apexar.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Connection attempt timeout
Date: Wed, 22 Feb 2006 13:16:58 -0300	[thread overview]
Message-ID: <1140625019.3319.1.camel@localhost.localdomain> (raw)
In-Reply-To: <1140564558.22767.29.camel@localhost>

I've found the piece of code that does the trick (function _cmd_page_to
in file hciconfig.c). Thanks Marcel!


On Wed, 2006-02-22 at 00:29 +0100, Marcel Holtmann wrote:
> Hi Agustin,
> 
> > I'm developing an application using the bluetooth libraries provided by
> > Marcel. I'm working with rfcomm connections. After looking at the
> > function cmd_connect (in the file 'main.c',in the rfcomm directory of
> > the bluez-utils-2.25) I realized that (using this function) there's no
> > way to set the connection attempt timeout (the time the connection
> > attempt will last if the remote device is, for example, turned off).
> 
> what do you mean by connection attempt timeout. I think the correct term
> is page timeout and you can of course set it with hciconfig.
> 
> Regards
> 
> Marcel
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-02-22 16:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051202220703.C04EF953BA@sc8-sf-spam1.sourceforge.net>
2005-12-02 23:34 ` [Bluez-users] Errors from hcid Michael Gorbach
2005-12-03  5:20   ` Marcel Holtmann
2006-02-15 21:04   ` [Bluez-users] Cannot compile bluez-utils-2.25 Agustin Jose Fusaro
2006-02-17 11:32     ` Claudio Takahasi
2006-02-17 13:43       ` Agustín José Fusaro
2006-02-21 22:00   ` [Bluez-users] Connection attempt timeout Agustin Jose Fusaro
2006-02-21 23:29     ` Marcel Holtmann
2006-02-22 16:16       ` Agustin Jose Fusaro [this message]
2006-02-21 23:05   ` [Bluez-users] Link quality measurement Agustin Jose Fusaro
2006-02-21 23:28     ` Marcel Holtmann
2006-02-22 16:17       ` Agustin Jose Fusaro
2006-02-22 21:14   ` [Bluez-users] Bitstuffing in a Rfcomm connection? Agustin Jose Fusaro
2006-02-22 21:27     ` Marcel Holtmann
2006-02-23 15:58       ` Agustin Jose Fusaro
2006-02-23 16:51         ` Marcel Holtmann

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=1140625019.3319.1.camel@localhost.localdomain \
    --to=afusaro@apexar.com \
    --cc=bluez-users@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).