public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: dsas@mega.ist.utl.pt
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: Problems while sending and receiving with rfcomm sockects
Date: Sun,  6 Jun 2004 16:46:44 +0100	[thread overview]
Message-ID: <1086536804.40c33c64e8456@webmail.rnl.ist.utl.pt> (raw)
In-Reply-To: <1086102474.40bc9bca939eb@webmail.rnl.ist.utl.pt>

Hello Marcel,

I've compiled kernel-2.6.6 with the new mh3 patch and now, everything wor=
ks
fine. So, I think it is a kernel bug (2.4.20). It also works without
semaphores.

Just one more thing about this: The number of bytes sent and received is =
the
same but the data received appears shifted by one byte... Strange.

If you're still interested, I'll send you a small program in a few days (=
I have
some work to do for now...).

Once again, thank you Marcel.

Regards,

Didier

> > When I execute 2 servers on masters side (one only sending and the ot=
her
> > only receiving) using diferents rfcomm channels, I also receive corru=
pt
> > data (very rarely :-( ). If they"re both sending or receiving, everyt=
hing
> > works fine...
> >
> > think it"s possible to use semaphores to synchronize the 2 processes =
but I"d
> > like to use a simpler solution or at least understand where the probl=
em is.
>
> if you are using two different RFCOMM channels and this happens it look=
s
> like a bug in the kernel code. As I said, check the latest kernel and
> try to send us a simple program that triggers this effect.





-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2004-06-06 15:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01 11:16 [Bluez-devel] Problems while sending and receiving with rfcomm sockects dsas
2004-06-01 12:34 ` Marcel Holtmann
2004-06-01 12:56   ` Collin R. Mulliner
2004-06-01 14:31     ` Marcel Holtmann
     [not found]   ` <1086094626.40bc7d22eab66@webmail.rnl.ist.utl.pt>
2004-06-01 14:32     ` Marcel Holtmann
     [not found] ` <1086094054.1978.26.camel@fischer>
2004-06-01 15:07   ` dsas
2004-06-01 15:16     ` Marcel Holtmann
2004-06-06 15:46     ` dsas [this message]
2004-06-06 15:59       ` [Bluez-devel] " Marcel Holtmann
2004-06-06 16:16         ` dsas
2004-06-06 16:26           ` Marcel Holtmann
2004-06-06 20:52           ` 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=1086536804.40c33c64e8456@webmail.rnl.ist.utl.pt \
    --to=dsas@mega.ist.utl.pt \
    --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