From: Marcel Holtmann <marcel@holtmann.org>
To: franz keuner <franz_keuner@gmx.net>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] rfcomm receive problem and success
Date: Fri, 26 Mar 2004 00:58:25 +0100 [thread overview]
Message-ID: <1080259105.2283.65.camel@pegasus> (raw)
In-Reply-To: <18344.1080206436@www52.gmx.net>
Hi Franz,
> that's maybe a stupid question:
> but why is there a error message if the bytes are received?
actually these is a test program and not for normal use. Maybe the code
is simply wrong. I never checked it and I don't really care. If you
fixed it, send me a patch.
> when i use the dump function i can work in my program with the data sended
> by the phone and no error.
>
> when i try to use the receive function there's this error.
>
> is the fault on the phone side and what can i do about it?
> does the receive function needs any additional information compared to the
> dump(read) function?
Compare the code of the recv and the dump functions and check what
happens. Look at it with hcidump to see if it is really an error.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-03-25 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 9:07 [Bluez-devel] rfcomm receive problem and success franz keuner
2004-03-24 11:59 ` Marcel Holtmann
[not found] ` <18344.1080206436@www52.gmx.net>
2004-03-25 23:58 ` Marcel Holtmann [this message]
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=1080259105.2283.65.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=franz_keuner@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.