All of lore.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] hcid returning "Device or resource busy"?
Date: Wed, 28 Mar 2007 14:47:37 +0200	[thread overview]
Message-ID: <1175086057.5815.132.camel@violet> (raw)
In-Reply-To: <1175085249.2996.1.camel@dhcp-1-148.fab.redhat.com>

Hi Bastien,

> > > > HCI Event: Command Status (0x0f) plen 4
> > > >     Remote Name Request Cancel (0x01|0x001a) status 0x01 ncmd 1
> > > >     Error: Unknown HCI Command
> > > 
> > > Looks like a BT1.1 dongle to me since Remote Name Request Cancel was
> > > introduced after that.
> > > And since the device is not yet finished paging during the remote name
> > > request, it disallows the Inquiry Command.
> > > 
> > > Solution: Get yourself a dongle > BT1.1 !
> > 
> > actually it was the Create Connection Cancel that was introduced with
> > Bluetooth 1.2. The Remote Name Request Cancel was always present, but it
> > seems we have a chip that doesn't support it.
> > 
> > Bastien, what does "hciconfig hci0 version" tells you?
> 
> Same device, different machine (the dongle followed me to the office):
> 
> $ hciconfig hci0 version
> hci0:   Type: USB
>         BD Address: 00:08:F4:00:43:8D ACL MTU: 192:8 SCO MTU: 64:8
>         HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver:
> 0x20d
>         Manufacturer: Cambridge Silicon Radio (10)
> 
> I hope there's at least some way to get it working. I'd rather not have
> to have another dongle just because hcid doesn't like it :)

the problem is that the baseband is busy with the remote name request.
It has to page the remote device for getting the name and in that case
you simply can't run an inquiry. All currently available Bluetooth chips
have this limitation.

Main question is why we have the remote name request just before you
wanna start the inquiry. What D-Bus methods are you actually calling in
what order? I think you constructed a use case that we never tested.

Regards

Marcel



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

  reply	other threads:[~2007-03-28 12:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-28  9:16 [Bluez-devel] hcid returning "Device or resource busy"? Bastien Nocera
2007-03-28  9:28 ` Marcel Holtmann
2007-03-28  9:56   ` Bastien Nocera
2007-03-28 10:06     ` Mayank BATRA
2007-03-28 10:18       ` Marcel Holtmann
2007-03-28 10:29         ` Mayank BATRA
2007-03-28 10:42           ` Marcel Holtmann
2007-03-28 12:34         ` Bastien Nocera
2007-03-28 12:47           ` Marcel Holtmann [this message]
2007-03-28 13:07             ` Bastien Nocera
2007-03-28 13:20               ` Marcel Holtmann
2007-03-28 15:05                 ` [Bluez-devel] L2CAP: ECONNRESET is set for every l2cap disconnect Aarti Kumar
2007-03-29 12:18                 ` [Bluez-devel] hcid returning "Device or resource busy"? Bastien Nocera
2007-03-29 12:20                   ` Marcel Holtmann
2007-03-29 13:24                     ` Bastien Nocera
2007-03-29 16:16                       ` Marcel Holtmann
2007-03-29  5:58             ` Mayank BATRA
2007-03-31 13:56               ` 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=1175086057.5815.132.camel@violet \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.