public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Problems with my own inquiry
Date: Tue, 19 Jun 2007 16:31:10 +0200	[thread overview]
Message-ID: <1182263470.10089.1.camel@aeonflux> (raw)
In-Reply-To: <200706180938.10993.fernando@bluexare.org>

Hi Fernando,

> > the solution is to use the new D-Bus based API. It takes care of
> > everything that you want.
> 
> When I install the new distribution, I update the bluetooth/bluez packages 
> with "apt-get", so there may be the later version, doesn't do?
> If it is not true, where I can update my version to one make my system works 
> ok?

running a Debian Etch for Ubuntu Feisty should be enough,

> > The new hcid switches into the best inquiry mode and that means Inquiry
> > with RSSI (which is different event) for a Bluetooth 1.2 dongle or
> > later. You have to watch for that event, too. Or use the D-Bus API that
> > does that for you and already takes care of Extended Inquiry of the
> > Bluetooth 2.1 specification.
> 
> I thought I was watching for this event, in the program:
> 
> switch (buf[1]) {
> 	case EVT_CMD_STATUS:
> 		//some code
> 		break;
> 	case EVT_INQUIRY_RESULT:
> 	case EVT_INQUIRY_RESULT_WITH_RSSI:
> 		//some code
> 		break;
> 	case EVT_INQUIRY_COMPLETE:
> 		//some code
> 		break;
> 	default:
> 		//some code
> 		break;
> }
> 
> I take the event EVT_INQUIRY_RESULT_WITH_RSSI, so I'm watching the event, 
> doesn't do?
> And in the case I have not watch properly the event, it must be executed the 
> code within the case "default", and do not execute...

that doesn't work. Both event are different. You need an extra routine
to handle it. Also you must put it in your kernel event filter.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-06-19 14:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-15 16:09 [Bluez-devel] Problems with my own inquiry Fernando Unzu
2007-06-16  7:29 ` Marcel Holtmann
2007-06-18  7:38   ` Fernando Unzu
2007-06-19 14:31     ` Marcel Holtmann [this message]
2007-06-20  0:43     ` Simon

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=1182263470.10089.1.camel@aeonflux \
    --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