From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] where is rfcomm souce code?
Date: Fri, 11 Mar 2005 22:42:49 +0100 [thread overview]
Message-ID: <1110577369.8511.4.camel@pegasus> (raw)
In-Reply-To: <310527409.26361@bjut.edu.cn>
Hi,
> Hi, Marcel. As you said,the source code of RFCOMM protocol in Bluez could be
> found in linux-2.6.11,but I have found some source code about rfcomm in the
> bluez-utils-2.15. So I want to make it clearly that what is the difference between
> them.
the need the RFCOMM source in bluez-utils-2.15 to create the RFCOMM TTY
terminal emulation devices. It is like you need ifconfig to manage your
local ethernet interface.
Regards
Marcel
-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-03-11 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 7:50 [Bluez-users] where is rfcomm souce code? 郭瑞
2005-03-11 21:42 ` 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=1110577369.8511.4.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@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.