public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Carlos AM" <Carlos@naxus.biz>
To: "lista bluez" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] RFCOMM communication gets stalled
Date: Thu, 15 Jul 2004 16:21:24 +0200	[thread overview]
Message-ID: <002c01c46a77$034a25e0$5000005a@naxus> (raw)

[-- Attachment #1: Type: text/plain, Size: 803 bytes --]

Hi

I'm using bluez-libs-2.7 and bluez-utils-2.7 to develop a GPS system that communicates via bluetooth. I use the RFCOMM and the connection and disconnection works fine but the transmission gets stalled in about ten minutes. Both sides indicate that they are still connected, but in the GPS side, the process that writes in the rfcomm device (/dev/bluetooth/rfcomm/0) stops on a blocking write call:

    write(fdbluetooth,s,strlen(s));

I open the rfcomm device this way:

    fdbluetooth= open("/dev/bluetooth/rfcomm/0",O_RDWR | O_NOCTTY);


That write call works fine for a while until the communication gets stalled.

Is a bad implementation of the process that writes in the rfcomm device?
Is that issue solved in the 2.8 version of bluez?



Carlos AM
Naxus Conectividad Móvil

[-- Attachment #2: Type: text/html, Size: 2027 bytes --]

             reply	other threads:[~2004-07-15 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-15 14:21 Carlos AM [this message]
2004-07-15 17:48 ` [Bluez-devel] RFCOMM communication gets stalled Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2004-07-15 18:11 Williams, Richard
2004-07-15 18:23 ` 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='002c01c46a77$034a25e0$5000005a@naxus' \
    --to=carlos@naxus.biz \
    --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