From: Marcel Holtmann <marcel@holtmann.org>
To: Nitin Mahajan <nitinm76@yahoo.com>
Cc: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BlueZ APIs
Date: Wed, 29 Aug 2007 15:54:22 +0200 [thread overview]
Message-ID: <1188395662.6109.48.camel@violet> (raw)
In-Reply-To: <244253.57477.qm@web50108.mail.re2.yahoo.com>
Hi Nitin,
> Thanks for your inputs, is that possible I can use the BlueZ without D-BUS also?
you could use libbluetooth directly to access HCI, but you really don't
wanna do that. It is like working with plain IP packets instead of TCP
and you will do a lot of things wrong. In some cases the kernel or hcid
will not even allow you certain changes and simply go ahead and
overwrite them. The D-Bus API is the only one that makes sense, because
it takes care of a lot of things you normally don't think about. Trust
me on this one. We spent a lot of time in getting this right.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-08-29 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 11:25 [Bluez-users] BlueZ APIs Nitin Mahajan
2007-08-29 13:54 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-26 5:08 Nitin Mahajan
2007-09-26 22:12 ` Marcel Holtmann
2007-08-29 8:57 Nitin Mahajan
2007-08-29 9:48 ` 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=1188395662.6109.48.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=nitinm76@yahoo.com \
/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