public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: help needed with rfcomm
Date: Wed, 24 Aug 2005 22:56:18 +0200	[thread overview]
Message-ID: <1124916978.8019.22.camel@pegasus> (raw)
In-Reply-To: <259637e05082413431076f7b@mail.gmail.com>

Hi Rui,

> I also notice now, that I don't have any /dev/rfcomm* or
> /dev/bluetooth/rfcomm* devices under /dev. I'm using udev as a device
> manager. anyone?? please

the rfcommX devices are optional. They must be created with a special
ioctl() after you established the connection. However most applications
don't need a TTY. They work perfect through a socket.

Regards

Marcel




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-08-24 20:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24 19:21 [Bluez-devel] help needed with rfcomm Rui Silva
2005-08-24 20:43 ` [Bluez-devel] " Rui Silva
2005-08-24 20:56   ` Marcel Holtmann [this message]
2005-08-24 20:55 ` [Bluez-devel] " Marcel Holtmann
2005-08-25 13:43   ` Rui Silva
2005-08-25 14:29     ` Marcel Holtmann
2005-08-26 13:35       ` Rui Silva
2005-08-26 20:56         ` Rui Silva
2005-08-26 21:02           ` Albert Huang
2005-08-27 12:55         ` 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=1124916978.8019.22.camel@pegasus \
    --to=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox