From: Marcel Holtmann <marcel@holtmann.org>
To: Andy Ross <andy@plausible.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RFCOMM bug?
Date: Wed, 18 Feb 2004 00:33:47 +0100 [thread overview]
Message-ID: <1077060827.2665.137.camel@pegasus> (raw)
In-Reply-To: <40329CA6.7080302@mdolabs.com>
Hi Andy,
> I'm having some trouble with the bluez implementation as distributed
> with fedora. I thought for a long time that this was a bug on the
> device (Ericsson P900 / Symbian 7.0) side of the connection, but it's
> now looking like a kernel issue on the linux box.
>
> The app on the other side is a simple RFCOMM echoer. It reads a byte
> at a time and writes it back out to the socket. I'm connecting to it
> with a "cat /dev/rfcomm1", while I do a "echo a > /dev/rfcomm1" from
> another shell. What comes back is an unending spew of bytes, mostly
> (but oddly not entirely) derived from the "a\r\n" that went out the
> terminal initially.
>
> FWIW, I see almost identical behavior when connecting to the "modem"
> device on the phone. The AT command work (in the sense that I can see
> the desired output appear on the socket), but come back as part of an
> infinite garbage stream.
set the RFCOMM terminal device into raw mode and everything works fine.
Regards
Marcel
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-02-17 23:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 22:58 [Bluez-devel] RFCOMM bug? Andy Ross
2004-02-17 23:33 ` Marcel Holtmann [this message]
2004-02-17 23:57 ` Andy Ross
2004-02-18 0:08 ` Marcel Holtmann
2004-02-18 0:59 ` Andy Ross
2004-02-18 6:48 ` 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=1077060827.2665.137.camel@pegasus \
--to=marcel@holtmann.org \
--cc=andy@plausible.org \
--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 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.