From: "Chafik Moalem" <Chafik.Moalem@perdictum.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] BECI
Date: Wed, 29 Nov 2006 09:16:51 +0100 [thread overview]
Message-ID: <1164788211.17085.53.camel@chmo.prologistik.com> (raw)
In-Reply-To: <1164736384.13955.24.camel@aeonflux.holtmann.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 2265 bytes --]
Hi Marcel,
hmmm ... as I understood so far :
a BECI Module with the right abstraction API (dbus) might "replace"
bluez then ?
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"
when they talk about "API" they mean a simple serial (uart) message
format :)
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 !
Did you hear about other modules already implementing such intelligent
subsystems and already available?
regards
Chafik
Am Dienstag, den 28.11.2006, 18:53 +0100 schrieb Marcel Holtmann:
> Hi Juergen,
>
> > BECI is designeated as a Profile orientated Interface situated on top of profiles and protocols
> > to interact with aplications.
> > So its not a question of hardware.
> > However since a working group has not been established yet no specs exist.
>
> I heard about BECI and actually my understanding is that stuff like
> L2CAP and RFCOMM can run on the Bluetooth chip itself and doesn't needed
> to be implemented in the actual host OS. However my tip is that someone
> might simply have a look at our D-Bus based API, because we designed all
> methods and signals from the viewpoint of the applications. It has
> become one of the easiest to use abstractions, I have seen so far.
>
> 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
[-- Attachment #1.1.2: Type: text/html, Size: 3666 bytes --]
[-- Attachment #1.2: smiley-3.png --]
[-- Type: image/png, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
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 8:16 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 [this message]
2006-11-29 9:12 ` Marcel Holtmann
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=1164788211.17085.53.camel@chmo.prologistik.com \
--to=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