From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [DBUS] remote name patch
Date: Thu, 09 Feb 2006 16:56:58 +0100 [thread overview]
Message-ID: <1139500618.17280.30.camel@localhost> (raw)
In-Reply-To: <e1effdeb0602090555u507a1567tb0b3dcb8b1369f1a@mail.gmail.com>
Hi Claudio,
> According with your request, I am sending the patch again.
> The function get_device_name should be moved to a common library.
we maybe need to create a storage plugin which can be replaced very
easily, but for now it is fine.
> Basically, this patch try retrieve the remote name from the
> cache(names file) instead of send the HCI command everytime.
The pscan_rep_mode must be 0x02 if you don't have any cached value from
an inquiry result. I fixed it and committed it to the CVS.
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
prev parent reply other threads:[~2006-02-09 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 18:37 [Bluez-devel] [DBUS] remote name patch Claudio Takahasi
2006-01-21 1:48 ` Marcel Holtmann
2006-01-23 16:33 ` Claudio Takahasi
2006-01-23 17:08 ` Marcel Holtmann
2006-01-23 18:54 ` Claudio Takahasi
2006-01-23 20:14 ` Marcel Holtmann
2006-01-26 14:09 ` Claudio Takahasi
2006-01-26 18:03 ` Marcel Holtmann
2006-02-09 13:55 ` Claudio Takahasi
2006-02-09 15:56 ` Marcel Holtmann [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=1139500618.17280.30.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 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).