From: "Alan Huang" <alanh@tuks.co.za>
To: <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] rfcomm patch
Date: Wed, 5 Nov 2003 17:50:16 +0200 [thread overview]
Message-ID: <004101c3a3b4$81f42dd0$dc01a8c0@alan> (raw)
In-Reply-To: 200311050945.34166.sybren@thirdtower.com
Hi,
Regarding this topic that rfcomm doesn't flush. I just want to ask that,
I'm using an USB Bluetooth dongle that's connected to another Bluetooth
device using the rfcomm program. This other Bluetooth device is connected to
a Windows PC's COM1 port (RS-232) and connected/displayed by
hyperterminal... For some unknown reason, what ever the hyperterminal sends
on the Windows side can be shown
"cat /dev/rfcomm0". But what ever the USB Bluetooth dongle sends (using
"echo hello > /dev/rfcomm0") it can't be shown on the Windows
hyperterminal...
On my Windows side, I have a embedded Bluetooth module (CSR's BC02) and the
signal is connected to a MAX chip converting betweeen BC02's 3.3V and
RS232's logic level.
Regards,
Alan
----- Original Message -----
From: "Sybren Stuvel" <sybren@thirdtower.com>
To: <bluez-devel@lists.sourceforge.net>
Sent: Wednesday, November 05, 2003 10:45 AM
Subject: [Bluez-devel] rfcomm patch
Hi there,
I've been working with bluetooth for a few months now, trying to let BlueZ
(on
my PC) talk to Affix (on my Zaurus). One difficulty is that rfcom doesn't
flush it's stdout when a new (incoming and/or outgoing) connection has been
made.
With the attached patch, scripts can use rfcomm to connect via bluetooth and
fork() the process in order to start using the connection (ie. by running
pppd over it).
Greetings,
Sybren Stuvel
--
(o_ Q: God, root, what is difference?
//\ A: God can change the byte order on the CPU, root can't.
V_/_
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-11-05 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 8:45 [Bluez-devel] rfcomm patch Sybren Stuvel
2003-11-05 10:16 ` Marcel Holtmann
2003-11-05 12:14 ` Sybren Stuvel
2003-11-05 12:22 ` Marcel Holtmann
2003-11-05 15:00 ` Sybren Stuvel
2003-11-05 15:50 ` Alan Huang [this message]
2003-11-06 8:39 ` Marcel Holtmann
2003-11-06 20:29 ` [Bluez-users] " Alan Huang
2003-11-06 23:44 ` 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='004101c3a3b4$81f42dd0$dc01a8c0@alan' \
--to=alanh@tuks.co.za \
--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.