Ok taking a look at hcitool.c I understand.
I will simply take the functions hci_open_dev and hci_create_connection (provided by bluez-lib) in order to implement the
hcitool cc call in my application. So the kernel handles the low-level stuff like socket-calls etc ....
But anyway is there a way to do that through the comfortable dbus interface? I guess not.
hm but I have to setup a connection manually just like hcitool does (hcitool cc --role=s) in my programm.
Is there now way to do that through the comfortable dbus interface?
So just the same as hcitool cc --role=s <bdaddr> (this establishes a ACL connection, right? ) but more comfortable to implement error-handling etc.In which ways does the kernel that for me, or how can I initiate it?
>you don't have to do that at all. Never ever establish ACL links by
>yourself. Let the kernel do it for you.
I thought this can be done with socket-calls etc. as it done by a lot of tools like hcitool etc.
Thanks,
Fritz--On Thu, Jun 12, 2008 at 12:29 PM, Marcel Holtmann <marcel@holtmann.org> wrote:
Hi Fritz,
> hcitool cc --role=s <bdaddr>
> establishes a low level ACL connection.
>
> I have to do that in a self-written tool with error-handling etc.
> How can this be done through the dbus-interface, I've actually found
> no method in the interfaces listed here http://wiki.bluez.org/wiki
>>you don't have to do that at all. Never ever establish ACL links by
>>yourself. Let the kernel do it for you.
Regards
Marcel
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
Regards,
--Codefritz