public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Huang <ashuang@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] how well supported is hci_read_rssi and hci_read_link_quality?
Date: Wed, 23 Jun 2004 01:19:46 -0400	[thread overview]
Message-ID: <ef9938ec0406222219c5d442b@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 567 bytes --]

Hello,

Does anyone have a rough estimate, or even a list, of the devices that
support hci_read_rssi and hci_read_link_quality?  Am I correct in
assuming that some devices supoprt it and some don't?  For example, a
program that reads rssi and link quality that works beautifully on an
x86 with a d-link usb bluetooth dongle doesn't seem to work at all on
an HP ipaq h5550.  On the ipaq, the link quality is always 0 and rssi
is always 255.

The attached patch changes cmd_lq in hcitool.c to print out an
unsigned integer instead of a signed integer.

thanks.
-albert

[-- Attachment #2: cmd_lq.diff --]
[-- Type: text/plain, Size: 483 bytes --]

Index: tools/hcitool.c
===================================================================
RCS file: /cvsroot/bluez/utils/tools/hcitool.c,v
retrieving revision 1.44
diff -u -r1.44 hcitool.c
--- tools/hcitool.c	12 Jun 2004 09:41:17 -0000	1.44
+++ tools/hcitool.c	23 Jun 2004 05:17:27 -0000
@@ -982,7 +982,7 @@
 				rp.status);
 		exit(1);
 	}
-	printf("Link quality: %d\n", rp.link_quality);
+	printf("Link quality: %u\n", rp.link_quality);
 
 	close(dd);
 	free(cr);

             reply	other threads:[~2004-06-23  5:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23  5:19 Albert Huang [this message]
2004-06-23  7:31 ` [Bluez-devel] how well supported is hci_read_rssi and hci_read_link_quality? Marcel Holtmann
2004-06-23 15:12   ` Albert Huang

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=ef9938ec0406222219c5d442b@mail.gmail.com \
    --to=ashuang@gmail.com \
    --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