I've been following the list for a while, but I never picked up on
what exactly DBus does for BlueZ. It is my understanding that in
BlueZ before 3.0, the socket() interface for userland API is
implemented by an ioctl() interface to the kernel. In BlueZ 3.x, is
all the HCI is handled by passing messages via DBus instead of
ioctl()?
If this conversation is already laid to rest in the archives, please
send me a URL.
Thanks for your time,
Jeff
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hi Jeff,
> I've been following the list for a while, but I never picked up on
> what exactly DBus does for BlueZ. It is my understanding that in
> BlueZ before 3.0, the socket() interface for userland API is
> implemented by an ioctl() interface to the kernel. In BlueZ 3.x, is
> all the HCI is handled by passing messages via DBus instead of
> ioctl()?
with our D-Bus API for BlueZ we provide a really nice an easy
configuration interface that can be used without linking the Bluetooth
library or be bound the C/C++ language.
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel