From: Marcel Holtmann <marcel@holtmann.org>
To: dsas@mega.ist.utl.pt
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Problems while sending and receiving with rfcomm sockects
Date: Sun, 06 Jun 2004 18:26:20 +0200 [thread overview]
Message-ID: <1086539180.4765.89.camel@pegasus> (raw)
In-Reply-To: <1086538596.40c34364bec57@webmail.rnl.ist.utl.pt>
Hi Didier,
> No, I don't use hcidump. I simply compare the array of chars passed in send()
> with the one I receive with recv().
then I really need a simple program that triggers this effect. It must
be a kernel bug and we should solve it.
Btw is there any difference when you use write() and read()?
Regards
Marcel
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-06-06 16:26 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 ` [Bluez-devel] " dsas
2004-06-06 15:59 ` Marcel Holtmann
2004-06-06 16:16 ` dsas
2004-06-06 16:26 ` Marcel Holtmann [this message]
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=1086539180.4765.89.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=dsas@mega.ist.utl.pt \
/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