public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Albert Huang <ashuang@gmail.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] how well supported is hci_read_rssi and hci_read_link_quality?
Date: Wed, 23 Jun 2004 09:31:51 +0200	[thread overview]
Message-ID: <1087975911.4209.58.camel@pegasus> (raw)
In-Reply-To: <ef9938ec0406222219c5d442b@mail.gmail.com>

Hi Albert,

> 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 link quality command is vendor specific, so you can't rely on it. We
only know how CSR uses it. The RSSI must be announced in the features
bits.

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

Does this make any difference? The link quality is only uint8.

Regards

Marcel




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-06-23  7:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23  5:19 [Bluez-devel] how well supported is hci_read_rssi and hci_read_link_quality? Albert Huang
2004-06-23  7:31 ` Marcel Holtmann [this message]
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=1087975911.4209.58.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=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