Re: [Bluez-devel] hcid returning "Device or resource busy"?

[Marcel Holtmann <marcel@holtmann.org>]

Hi Mayank,

> > > 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.
> 
> But actually, the sequence of HCI commands issued is correct. First, a
> remote
> name request is issued. Then, since an inquiry is required, the remote
> name
> request is cancelled. Thus, paging should stop and inquiry should be
> possible.
> I think this use case should work with BT1.2 devices and above.
> 
> But you are right, maybe some workaround should be present in order to
> be
> compatible with BT1.1 devices as well.

we need a workaround for Bluetooth 1.1 devices. However I have no idea
what we can actually do to make this work.

My idea is to not actively request names when not in discovery mode.
That would actually fix this cases.

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