All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [DBUS PATCH] scan mode timeout
Date: Wed, 15 Feb 2006 15:20:22 +0100	[thread overview]
Message-ID: <1140013222.26072.80.camel@localhost> (raw)
In-Reply-To: <e1effdeb0602150611s60763bb4u6362fd401cafd4ba@mail.gmail.com>

Hi Claudio,

> Here is the first proposal to support the discoverable timeout.
> 
> Current behaviour:
> * it's using SIGALARM. We can try integrate in the main loop in the future..
> * the scan mode is changed automatically to connectable mode after 3 min
> * multiple local adapters are handled: there are separated timers.
> * scan mode changes requested by other applications(hciconfig and
> other dbus clients) are monitored too.
> 
> 
> Some points to things about:
> * bluez_timeout_add consider the function handler and the user data to
> compare if it's necessary update or add new timer. Is this approach
> acceptable?
> * Is it necessary handle race condition when updating the timeout array?
> * 8 positions to timeout handler are enough?
> 
> Any comments?

maybe you wanna separate the {Set|Get}DiscoverableTimeout code, because
this is obviously correct and would apply right away.

Using an array of 8 handles is actually not enough. Even if no sane
person would ever attach more than 8 dongles, but I might do ;)

However you need at least to support HCI_MAX_DEV from hci.h and this is
currently 16 adapters. Remember that the kernel will still accept more
than 16 device, but the userspace simply can't handle them (except you
recompile the Bluetooth library).

Do we have a function to iterate over the registered device paths and
retrieve their hci_dbus_data structures? If yes, then I would prefer to
include everything from timeout_settings there and use it.

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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-02-15 14:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 14:11 [Bluez-devel] [DBUS PATCH] scan mode timeout Claudio Takahasi
2006-02-15 14:20 ` Marcel Holtmann [this message]
2006-02-15 16:31   ` Claudio Takahasi
2006-02-15 17:18     ` Claudio Takahasi
2006-02-15 17:46       ` Marcel Holtmann
2006-02-16 18:41         ` Claudio Takahasi
2006-02-17 17:48           ` Claudio Takahasi
2006-02-17 17:58             ` 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=1140013222.26072.80.camel@localhost \
    --to=marcel@holtmann.org \
    --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 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.