From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] C Program for Getting Link Quality
Date: Tue, 08 Nov 2005 13:49:55 +0100 [thread overview]
Message-ID: <1131454195.5824.161.camel@blade> (raw)
In-Reply-To: <94e407f00511080131u11f01d79x65d05cfe47ccbb7@mail.gmail.com>
Hi Arpit,
> I've written a C program to help me get the link quality between two
> bluetooth dongles. But, on compilation there are problems with the
> definition:
>
> cr = (hci_conn_info_req *)malloc(sizeof(*cr) + sizeof(struct
> hci_conn_info)); (Error: 'hci_conn_info_req' undeclared)
>
> This the program I'm running:
>
> //Program for finding LQ
> #include <stdio.h>
> #include <stdlib.h>
> #include <unistd.h>
> #include <bluetooth/bluetooth.h>
> #include <bluetooth/hci.h>
> #include <bluetooth/hci_lib.h>
don't forget to include <sys/socket.h> before <bluetooth/bluetooth.h> or
use a newer version of the Bluetooth library.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-11-08 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 9:31 [Bluez-devel] C Program for Getting Link Quality Arpit Rai
2005-11-08 9:46 ` Collin R. Mulliner
2005-11-08 12:49 ` Marcel Holtmann [this message]
2005-11-08 17:58 ` Arpit Rai
2005-11-08 18:17 ` Marcel Holtmann
2005-11-09 12:52 ` Arpit Rai
2005-11-09 14:02 ` 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=1131454195.5824.161.camel@blade \
--to=marcel@holtmann.org \
--cc=bluez-devel@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