From: "Fritz Code" <codefritz@googlemail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] implement hcitool cc call with dbus interface
Date: Thu, 12 Jun 2008 13:12:09 +0200 [thread overview]
Message-ID: <3e9cdced0806120412ic2904bai44cd6eee00179c2f@mail.gmail.com> (raw)
In-Reply-To: <3e9cdced0806120337p5043c4celf7092d086f937691@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2170 bytes --]
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.
On Thu, Jun 12, 2008 at 12:37 PM, Fritz Code <codefritz@googlemail.com>
wrote:
> 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.
>
> >you don't have to do that at all. Never ever establish ACL links by
> >yourself. Let the kernel do it for you.
>
> In which ways does the kernel that for me, or how can I initiate it?
> 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
>
>
>
>
--
Regards,
--Codefritz
[-- Attachment #1.2: Type: text/html, Size: 3402 bytes --]
[-- Attachment #2: Type: text/plain, Size: 247 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-06-12 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 10:09 [Bluez-users] implement hcitool cc call with dbus interface Fritz Code
2008-06-12 10:29 ` Marcel Holtmann
2008-06-12 10:37 ` Fritz Code
2008-06-12 11:12 ` Fritz Code [this message]
2008-06-12 13:09 ` Marcel Holtmann
2008-06-12 13:08 ` Marcel Holtmann
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=3e9cdced0806120412ic2904bai44cd6eee00179c2f@mail.gmail.com \
--to=codefritz@googlemail.com \
--cc=bluez-users@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