From: Marcel Holtmann <marcel@holtmann.org>
To: sancane <sancane@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: MCAP implementation in BlueZ
Date: Thu, 06 Aug 2009 13:12:24 -0700 [thread overview]
Message-ID: <1249589544.21101.25.camel@localhost.localdomain> (raw)
In-Reply-To: <4A7B28D7.8040902@gmail.com>
Hi,
> I have seen that BlueZ has begun to incorporate enhanced retransmission
> mode support to L2CAP. This is a happy new because i work with medical
> devices that have begun to incorporate health device profile (HDP) in
> bluetooth communications. I would like to use that devices in linux and
> i saw that MCAP is not included in the bluetooth linux stack so i was
> thinking in develop it for BlueZ.
> I've studying the possibility of integrate it as kernel module like
> rfcomm does but i have some doubts about that approximation. I think
> that it is not the best place for it and i believe that is better
> develop MCAP in user space.
you wanna do that in userspace (like we did with AVDTP). The kernel
option would be only required if it interacts with another kernel
subsystem which I highly doubt.
Currently it is not 100% clear what will be the best implementation of
HDP, but there are two choices. First one would be a bluetoothd plugin
or second would be similar to what obexd is doing. The real question
here is if it runs more in the user session or as a system daemon.
Regards
Marcel
prev parent reply other threads:[~2009-08-06 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 19:02 MCAP implementation in BlueZ sancane
2009-08-06 20:12 ` 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=1249589544.21101.25.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sancane@gmail.com \
/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