From: Albert Huang <ashuang@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] how to do inquiry with RSSI in bluetooth 1.2 devices?
Date: Fri, 15 Oct 2004 14:32:25 -0400 [thread overview]
Message-ID: <ef9938ec04101511326a6342c3@mail.gmail.com> (raw)
In-Reply-To: <1097658003.4643.17.camel@notepaq>
Hi Marcel,
> looks like it is correct. Send me a patch for the Bluetooth library to
> include this as API functions.
I'll do this once I manage to get everything working, just to be sure
it is correct.
> > When I run this with the anycom bluetooth device, the very first
> > hci_send_req never returns. I expected the READ_INQUIRY_MODE command
> > to generate a CMD_COMPLETE event, but no event is ever generated (I
> > tested this separately). Also, when hcidump is run concurrently with
> > this program, it doesn't pick anything up (no events are read by
> > hcidump) The same happens if I try to set the inquiry mode directly
> > without reading it first (the WRITE_INQUIRY_MODE command never
> > returns)
>
> I never saw that on my dongle. Please recompile your kernel without the
> SCO audio support for the hci_usb driver. What kind of USB host
> controller are you using? What kernel version do you use?
I am using kernel 2.4.27, compiled from sources available in the
debian repository. I recompiled without SCO audio support for hci_usb
and got the same result.
How do I find out what kind of USB host controller I'm using? lspci
gives the following output:
0000:00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 04)
0000:00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 04)
0000:00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 04)
dmesg shows the following lines related to USB
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 17:39:55 Oct 14 2004
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: USB UHCI at I/O 0xff80, IRQ 19
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
usb-uhci.c: USB UHCI at I/O 0xff60, IRQ 18
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
hub.c: new USB device 00:1f.2-2, assigned address 2
usb.c: USB device 2 (vend/prod 0xa12/0x1) is not claimed by any active driver.
BlueZ HCI USB driver ver 2.7 Copyright (C) 2000,2001 Qualcomm Inc
usb.c: registered new driver hci_usb
hub.c: new USB device 00:1f.4-1, assigned address 2
-albert
next prev parent reply other threads:[~2004-10-15 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 19:59 [Bluez-devel] how to do inquiry with RSSI in bluetooth 1.2 devices? Albert Huang
2004-10-13 9:00 ` Marcel Holtmann
2004-10-15 18:32 ` Albert Huang [this message]
2004-10-16 12:10 ` Marcel Holtmann
2004-10-19 21:44 ` Albert Huang
2004-10-19 21:55 ` Marcel Holtmann
2004-10-19 23:58 ` Albert Huang
2004-10-20 0:11 ` Albert Huang
2004-10-25 7:43 ` 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=ef9938ec04101511326a6342c3@mail.gmail.com \
--to=ashuang@gmail.com \
--cc=albert@csail.mit.edu \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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