From: mike <mikelee@avantwave.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] rfcomm socket and rfcomm tty
Date: Tue, 28 Dec 2004 17:03:20 +0800 [thread overview]
Message-ID: <41D12158.6020206@avantwave.com> (raw)
Dear all
I have little knowledge on tty structure, so i want to clarify
something is that, if i want to connect to a rfcomm enabled phone. Are
there any difference when i sending raw data to the phone with tty
rfcomm and socket rfcomm? I ask this question because i see that from
bluez-util rfcomm source code, tty connection is built up from socket
first and then set the tty attr. So if i do not need tty functions, only
read/write from/to external device is needed, socket rfcomm will be more
simple. Am i right?
If i make any thing wrong, please tell me.
Thanks
Mike,Lee
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-12-28 9:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 9:03 mike [this message]
2004-12-29 10:25 ` [Bluez-devel] rfcomm socket and rfcomm tty Marcel Holtmann
2004-12-30 1:55 ` mike
2005-01-01 18:42 ` Marcel Holtmann
2005-01-03 7:15 ` mike
2005-01-03 9:51 ` Marcel Holtmann
2005-01-04 7:32 ` mike
2005-01-04 11:51 ` Marcel Holtmann
2005-01-05 8:15 ` mike
2005-01-05 11:39 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2005-01-03 18:49 omap
2005-01-03 18:54 ` Marcel Holtmann
2005-01-03 19:12 omap
2005-01-03 19: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=41D12158.6020206@avantwave.com \
--to=mikelee@avantwave.com \
--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.