From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [DBUS Patch] Device Property
Date: Thu, 24 Nov 2005 05:17:02 +0100 [thread overview]
Message-ID: <1132805822.5982.15.camel@blade> (raw)
In-Reply-To: <3013cac80511221152t2911f513jb28f3944097c1b09@mail.gmail.com>
Hi Eduardo,
> here is the new patch. I've removed the spaces (I hope so). I've also
> included the code for the dbus signal for the local name change event.
> One thing that remainded open was the timeout for hci_send_req for
> name write and name read ops. In the hciconfig this was 2s and 1s. Is
> there a reason for this big number?
you missed one whitespace/tab clash, but I fixed it. Opening a patch
inside an editor with whitespace visualization helps a lot.
The patch has been applied to the CVS and we should talk about some
serious security setting for the D-Bus interface. Question is what a
session user should be able to change?
The timeout is not really crucial for most local configuration settings
and I think it was a bad idea to have it in the API anyhow. However the
change local name command is tricky. Some older CSR chips for example
are storing the name in the PS keys, which results writing it to flash
or EEPROM. This simply can take time.
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://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-24 4:17 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 14:03 [Bluez-devel] [DBUS Patch] Device Property Eduardo Rocha
2005-11-04 15:44 ` Marcel Holtmann
2005-11-08 20:41 ` Claudio Takahasi
2005-11-08 22:20 ` Marcel Holtmann
2005-11-08 22:20 ` Johan Hedberg
2005-11-08 22:38 ` Marcel Holtmann
2005-11-17 19:16 ` Eduardo Rocha
2005-11-17 20:52 ` Eduardo Rocha
2005-11-18 8:28 ` Johan Hedberg
2005-11-18 10:51 ` Eduardo Rocha
2005-11-18 11:26 ` Johan Hedberg
2005-11-18 13:00 ` Eduardo Rocha
2005-11-22 11:51 ` Marcel Holtmann
2005-11-22 19:52 ` Eduardo Rocha
2005-11-24 4:17 ` Marcel Holtmann [this message]
2005-11-24 18:50 ` Eduardo Rocha
2005-11-24 22:54 ` Marcel Holtmann
2005-11-25 13:47 ` Claudio Takahasi
2005-11-25 14:32 ` Eduardo Rocha
2005-11-25 18:08 ` Marcel Holtmann
2005-11-25 18:34 ` Eduardo Rocha
2005-11-25 18:41 ` Marcel Holtmann
2005-11-25 19:52 ` Claudio Takahasi
2005-11-25 20:06 ` Marcel Holtmann
2005-12-01 16:55 ` Eduardo Rocha
2005-12-01 21:05 ` Marcel Holtmann
2005-12-07 12:29 ` Eduardo Rocha
2005-12-07 12:55 ` Johan Hedberg
2005-12-07 13:02 ` Marcel Holtmann
2005-12-07 16:01 ` Eduardo Rocha
2005-12-13 17:27 ` Eduardo Rocha
2005-12-13 22:03 ` Marcel Holtmann
2005-12-14 19:02 ` Eduardo Rocha
2005-12-16 18:37 ` Eduardo Rocha
2005-12-16 18:40 ` Marcel Holtmann
2005-11-25 16:51 ` Johan Hedberg
2005-11-25 18:12 ` 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=1132805822.5982.15.camel@blade \
--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).