Re: [Bluez-users] Usage of fcntl for non blocking mode...

[Marcel Holtmann <marcel@holtmann.org>]

Hi Tushar,

> I'm getting some problem while using Bluez hci function calls. The
> pseudo code is as under:
> 
> ...
> devId = hci_devid(addr);
> sock = hci_open_dev(devId);
> ...
> fcntl(sock, F_SETFL, O_NONBLOCK); /** whats the problem ??? */
> ...
> hci_read_local_name(sock, size, name, 0)
> ....
> 
> 
> If I comment call to fcntl()  , I get correct name of device by using
> hci_read_local_name() function. 
> But if the call is made to fcntl(),  subsequent  calls of hci_*
> function does not work properly. In fact hci_read_local_name()
> returns  null name.  
> Any idea what is the problem with usage of  fcntl() this way ?

I never tried to have a non-blocking HCI socket. And I have no idea why
you actually need it. It is better to use the D-Bus API anyway.

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