Re: [Bluez-devel] bluetooth socket + rfcomm tty

[Marcel Holtmann <marcel@holtmann.org>]

Hi Victor,

> Could not find it through the archives... 
> I create a bluetooth socket and then create TTY (/dev/rfcomm0) based on it (like it is done in dund from bluez-utils). 
> Is it still allowed to use the descriptor of the open socket to send/receive data through the channel? 
> Cause when I send data to the _socket_ it looks like it is sent (like 
> ATD1234 command to the phone, I see the phone starting to dial, though it 
> stops half way for no reason), but when I'm trying to read from the socket 
> select() returns that there is data to be read, but then read() blocks.

this is maybe possible, but it is not intended. When you converted a
socket into a TTY the socket should be closed. Otherwise we must
duplicate the incoming data and if one party is not reading the flow
control will be brocken and both parties are blocked.

> P.S. Is there any way to check if read() is non-blocking (like ioctl() 
> FIONREAD)?

Check the fcntl() manpage.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel