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: Thu, 29 Mar 2007 18:16:42 +0200	[thread overview]
Message-ID: <1175185002.5815.201.camel@violet> (raw)
In-Reply-To: <1175174654.15698.160.camel@cookie.hadess.net>

Hi Bastien,

> > > Shouldn't it return org.bluez.Error.InProgress instead in that case?
> > 
> > it is a different operation that is in progress.
> 
> Ha. The documentation could do with a bit of rewording for that error
> (it's not clear that InProgress is when the *same* operation that one
> tried to perform is already running).

I agree. That needs a little bit better wording. In some cases we might
even have some bugs in the code.

> > > > You can wait for the completed RemoteNameUpdated or RemoteNameFailed
> > > > signals before actually starting the DiscoverDevices procedure. However
> > > > in case of devices out of range this might not be a good idea.
> > > 
> > > The problem is that I don't know for which devices hcid will try to go
> > > and fetch the names for.
> > > 
> > > Also, the doc for ListRemoteDevices should mention the fact that it
> > > might perform remote operations, as it's not really clear from the doc
> > > right now.
> > 
> > Actually ListRemoteDevices is not doing it. It happens when you call
> > GetRemoteName while you are adding it to your list.
> 
> Oh, my mistake. I'll fix my code then :)

Not your mistake. This should actually work. However we added a
GetRemoteInfo method lately that allows you to retrieve all known
information about a device as a dictionary.

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-29 16:16 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
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 [this message]
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=1175185002.5815.201.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