public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Anthony Yulo <strikewing16th@hotmail.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Difference between rctest.c and main.c in /rfcomm directory
Date: Mon, 19 Apr 2004 18:13:20 +0200	[thread overview]
Message-ID: <1082391200.4403.59.camel@pegasus> (raw)
In-Reply-To: <BAY16-F358WlSOBCCLj0001e0fe@hotmail.com>

Hi Anthony,

> I am only familiar with rfcomm that uses plain sockets...
> 
> I am only familiart with the rctest.c code that just setup the socket for 
> RFCOMM..
> 
> but i noticed some additional constants i.e. RFCOMM_REUSE_DLC, 
> RFCOMM_RELEASE_ONHUP..  in main.c of the /rfcomm directory (src)
> 
> Can someone explain to me briefly whats this for?

they are for transforming a Bluetooth RFCOMM socket into a TTY device.

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

      reply	other threads:[~2004-04-19 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19 15:37 [Bluez-devel] Difference between rctest.c and main.c in /rfcomm directory Anthony Yulo
2004-04-19 16:13 ` 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=1082391200.4403.59.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=strikewing16th@hotmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox