From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] kernel/userspace communication interface
Date: Tue, 18 Oct 2005 10:22:46 -0200 [thread overview]
Message-ID: <e1effdeb0510180522l33037a86rbd0231a3ba1b7201@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 626 bytes --]
Hi Marcel,
You wrote in an old email that a new communication interface between
the kernel and the userspace has been developed.
Could you give us more information about that? What is the status, how
it will work...
We are facing some problems related to blocking operations(eg: remote
name request and inquiry.) in the BlueZ D-Bus services.
The hcid D-Bus main loop can't be blocked and we wouldn't like open
another hci raw socket.
Regards,
Claudio.
--
---------------------------------------------------------
Claudio Takahasi
Nokia's Institute of Technology - INdT
claudio.takahasi@indt.org.br
[-- Attachment #2: Type: text/html, Size: 760 bytes --]
next reply other threads:[~2005-10-18 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 12:22 Claudio Takahasi [this message]
2005-10-18 17:37 ` [Bluez-devel] kernel/userspace communication interface 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=e1effdeb0510180522l33037a86rbd0231a3ba1b7201@mail.gmail.com \
--to=cktakahasi@gmail.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