Linux bluetooth development
 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 12:42:13 +0200	[thread overview]
Message-ID: <1175078533.5815.127.camel@violet> (raw)
In-Reply-To: <007901c77124$06df3040$9d0cc70a@dlh.st.com>

Hi Mayank,

> > > > 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.
> 
> You are right as well as wrong. Both Remote Name Request Cancel and 
> Create Connection Cancel were introduced in BT1.2. Please check (I've
> done that already!).

I don't have the Bluetooth 1.1 specification at hand. I was pretty sure
that the Remote Name Request Cancel was always present since I only
added a dependency against Bluetooth 1.2 for the Create Connection
Cancel support I added to the kernel lately.

> And since this is not an optional command it is impossible to have a
> BT1.2 chip which doesn't support this command.

You wish. I have seen chips where the set of supported HCI commands is
limited. Remember there is no real HCI qualification.

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 10:42 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 [this message]
2007-03-28 12:34         ` Bastien Nocera
2007-03-28 12:47           ` Marcel Holtmann
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=1175078533.5815.127.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox