From: Johan Hedberg <johan.hedberg@nokia.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Device scan property
Date: Fri, 25 Nov 2005 16:56:57 +0200 [thread overview]
Message-ID: <20051125145657.GA18684@localhost.localdomain> (raw)
In-Reply-To: <3013cac80511250643s30a3e836qb9559289e68ee75c@mail.gmail.com>
Hi Eduardo,
On Fri, Nov 25, 2005, Eduardo Rocha wrote:
> I'm going to start the scan property implementation for device path
> now. From early discussions, I think we have agreeded to split page
> scan and inquire scan property. Starting to think in implementation
> now, I realized that this imply in an extra getdeviceinfo, as we have
> to now if the exactly page flag status to modify it. If we join this
> two properties into scan property, with 2 boolean parameters for pscan
> and iscan, we can eliminate this operation. What do you guys think?
I think we should have two boolean properties: "discoverable" and
"connectable", even if that means doing an extra HCI_Read_Scan_Enable
command when setting the value of either one.
Johan
-------------------------------------------------------
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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-11-25 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 14:43 [Bluez-devel] Device scan property Eduardo Rocha
2005-11-25 14:56 ` Johan Hedberg [this message]
2005-11-25 19:04 ` 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=20051125145657.GA18684@localhost.localdomain \
--to=johan.hedberg@nokia.com \
--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).