From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] kernel/userspace communication interface
Date: Tue, 18 Oct 2005 19:37:28 +0200 [thread overview]
Message-ID: <1129657048.10721.48.camel@localhost.localdomain> (raw)
In-Reply-To: <e1effdeb0510180522l33037a86rbd0231a3ba1b7201@mail.gmail.com>
Hi Claudio,
> 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.
I still doesn't had time to finally implement the first rough steps into
this direction. Give some more time and I always to some thought about
what you need between kernel and userspace. The kernel for example is
already doing complete connection tracking and this means we don't need
to re-implement it in userspace.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-10-18 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-18 12:22 [Bluez-devel] kernel/userspace communication interface Claudio Takahasi
2005-10-18 17:37 ` 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=1129657048.10721.48.camel@localhost.localdomain \
--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