From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Usage of fcntl for non blocking mode...
Date: Mon, 02 Apr 2007 13:03:16 +0200 [thread overview]
Message-ID: <1175511796.5815.329.camel@violet> (raw)
In-Reply-To: <b621074b0704020400r2e1500d5u4972031e010a05e5@mail.gmail.com>
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
next prev parent reply other threads:[~2007-04-02 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 11:00 [Bluez-users] Usage of fcntl for non blocking mode Tushar Paturde
2007-04-02 11:03 ` Marcel Holtmann [this message]
2007-04-02 11:51 ` Tushar Paturde
2007-04-02 12:04 ` 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=1175511796.5815.329.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-users@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;
as well as URLs for NNTP newsgroup(s).