public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Alastair Tse <liquidx@gentoo.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 10:43:53 +0100	[thread overview]
Message-ID: <1154079833.10564.5.camel@localhost> (raw)
In-Reply-To: <1154050360.7650.13.camel@localhost>

On Fri, 2006-07-28 at 03:32 +0200, Marcel Holtmann wrote:
> > 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.

Marcel,

Thanks for the patch. That does get rid of the connection timed out
error in syslog. Although I'm still experiencing the fact that ISCAN is
not enabled, although that seems to be another problem associated with
the way 3.x works for detecting features (According to the another
thread).

Thanks,

Alastair




-------------------------------------------------------------------------
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
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-07-28  9:43 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
2006-07-28  9:43   ` Alastair Tse [this message]
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=1154079833.10564.5.camel@localhost \
    --to=liquidx@gentoo.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