From: Marcel Holtmann <marcel@holtmann.org>
To: Chafik Moalem <Chafik.Moalem@perdictum.com>,
BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] BECI
Date: Wed, 29 Nov 2006 10:12:41 +0100 [thread overview]
Message-ID: <1164791561.5071.5.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <1164788211.17085.53.camel@chmo.prologistik.com>
Hi Chafik,
> hmmm ... as I understood so far :
> a BECI Module with the right abstraction API (dbus) might "replace"
> bluez then ?
or we write a daemon that maps our D-Bus base API over BECI and all
application using our API will working on top of both.
> btw.: I am currently working with a uart module which has already a
> complete BT-Stack with profiles and all the needed logic implemented
> "inside" a CSR BC03MM ! All I need to do is initiate profile, initiate
> connection (implicit pairing), open SCO et voila : I have a nice
> PCM-eSCO connection to my HS ! just testing concurrent connections at
> the moment (SPP + HSP)
>
> Just have a look at
> http://www.lintech.de/index.php?index=19&pc=4&p=36
> .. the datasheet is "on click"
I know these kind of systems. Their usage always depends on how much
control you want and actually need.
> when they talk about "API" they mean a simple serial (uart) message
> format :)
No idea.
> Well if I have a bit more time I should try to implement a "special"
> uart<->dbus layer ... i think it is something pre-BECI !
Feel free to do so.
> Did you hear about other modules already implementing such intelligent
> subsystems and already available?
Almost every Bluetooth chip manufacturer provides a serial port profile
module somehow.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-11-29 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 20:41 [Bluez-devel] BECI Andreas Merkle
2006-11-28 4:24 ` Marcel Holtmann
2006-11-28 7:14 ` Juergen Wichmann
2006-11-28 17:53 ` Marcel Holtmann
2006-11-28 22:32 ` Andreas Merkle
2006-11-29 8:16 ` Chafik Moalem
2006-11-29 9:12 ` Marcel Holtmann [this message]
2006-11-29 10:50 ` [Bluez-devel] two concurrent a2dp connections Sergey Krivov
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=1164791561.5071.5.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=Chafik.Moalem@perdictum.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