public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Several problems with bluez-utils 3.1, kbluetoothd and a	Belkin dongle in Debian
Date: Fri, 28 Jul 2006 03:32:40 +0200	[thread overview]
Message-ID: <1154050360.7650.13.camel@localhost> (raw)
In-Reply-To: <1154042299.16913.6.camel@localhost>

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

Hi Alastair,

> I'm also experiencing the same behaviour as Felix with a Belkin dongle
> (Broadcom) with bluez-libs-3.2, bluez-utils-3.2. This is where ISCAN is
> not set even though it is enabled in hcid.conf. I've compiled from
> source on a Gentoo Linux box.
> 
> One additional thing that I would like to add is that I see this in my
> syslog:
> 
> Jul 28 00:10:15 qoo hcid[23009]: HCI dev 0 registered
> Jul 28 00:10:15 qoo hcid[23009]: Device hci0 has been added
> Jul 28 00:10:15 qoo hcid[23009]: Register path:/org/bluez/hci0
> fallback:0
> Jul 28 00:10:15 qoo hcid[23009]: HCI dev 0 up
> Jul 28 00:10:15 qoo hcid[23009]: Starting security manager 0
> Jul 28 00:10:16 qoo hcid[23009]: Can't write inquiry mode for hci0:
> Connection timed out (110)

the attached patch might help. If we have a Bluetooth 1.0b or 1.1 device
without a quirk to enable inqmode, we shouldn't even try to change the
inquiry mode. Seems that the Broadcom dongles are really sensible if you
try to send a command they don't support.

Regards

Marcel


[-- Attachment #2: patch --]
[-- Type: text/x-patch, Size: 1094 bytes --]

Index: hcid/device.c
===================================================================
RCS file: /cvsroot/bluez/utils/hcid/device.c,v
retrieving revision 1.14
diff -u -r1.14 device.c
--- hcid/device.c	26 Jul 2006 13:42:10 -0000	1.14
+++ hcid/device.c	28 Jul 2006 01:30:41 -0000
@@ -189,6 +189,7 @@
 	if (hci_read_local_version(dd, &ver, 1000) < 0) {
 		error("Can't read version info for hci%d: %s (%d)",
 					dev_id, strerror(errno), errno);
+		hci_close_dev(dd);
 		return -errno;
 	}
 
@@ -200,19 +201,24 @@
 	if (hci_read_local_features(dd, features, 1000) < 0) {
 		error("Can't read features for hci%d: %s (%d)",
 					dev_id, strerror(errno), errno);
+		hci_close_dev(dd);
 		return -errno;
 	}
 
 	memcpy(dev->features, features, 8);
 
 	inqmode = get_inquiry_mode(dev);
+	if (inqmode < 1)
+		goto done;
 
 	if (hci_write_inquiry_mode(dd, inqmode, 1000) < 0) {
 		error("Can't write inquiry mode for hci%d: %s (%d)",
 					dev_id, strerror(errno), errno);
+		hci_close_dev(dd);
 		return -errno;
 	}
 
+done:
 	hci_close_dev(dd);
 
 	info("Device hci%d has been activated", dev_id);

[-- Attachment #3: Type: text/plain, Size: 348 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-07-28  1:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 23:18 [Bluez-users] Several problems with bluez-utils 3.1, kbluetoothd and a Belkin dongle in Debian Alastair Tse
2006-07-28  1:32 ` Marcel Holtmann [this message]
2006-07-28  9:43   ` Alastair Tse
2006-07-29 12:58     ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2006-07-27 10:40 Felix Homann
2006-07-27 10:43 ` Marcel Holtmann
2006-07-27 10:58   ` Felix Homann
2006-07-27 11:04     ` Marcel Holtmann
2006-07-29 12:26       ` Felix Homann
2006-07-29 12:42         ` Marcel Holtmann
2006-07-27 20:08     ` Felix Homann
2006-07-28  1:20       ` Marcel Holtmann
2006-07-28  9:00         ` Felix Homann
2006-07-28  9:09           ` Marcel Holtmann
2006-07-28  9:28             ` Felix Homann
2006-07-28  9:38               ` Marcel Holtmann
2006-07-28 10:03                 ` Felix Homann
2006-07-28 10:06                   ` Marcel Holtmann
2006-07-28 10:14                     ` Felix Homann
2006-07-28 10:33                       ` Marcel Holtmann
2006-07-28 10:46                         ` Felix Homann
2006-07-28 10:51                           ` Marcel Holtmann
2006-07-28 10:40                     ` hugues
2006-07-28 11:07                       ` Felix Homann
2006-07-28 15:00                     ` Felix Homann
2006-07-28 15:07                       ` Marcel Holtmann
2006-07-29 12:11                         ` Felix Homann
2006-07-29 12:33                           ` 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=1154050360.7650.13.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-users@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