public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] implement hcitool cc call with dbus interface
Date: Thu, 12 Jun 2008 15:09:44 +0200	[thread overview]
Message-ID: <1213276184.17870.52.camel@violet.holtmann.net> (raw)
In-Reply-To: <3e9cdced0806120412ic2904bai44cd6eee00179c2f@mail.gmail.com>

Hi Fritz,

> 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 ....

I am serious here. If you are trying to do this, then you are doing
something wrong. Your application should not deal with low-level ACL
link establishment.

> But anyway is there a way to do that through  the comfortable dbus
> interface? I guess not.

No and that is because it is not needed.

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

  reply	other threads:[~2008-06-12 13:09 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
2008-06-12 13:09       ` Marcel Holtmann [this message]
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=1213276184.17870.52.camel@violet.holtmann.net \
    --to=marcel@holtmann.org \
    --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