From: steve.morard@epfl.ch
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Use /dev/ttyS* instead of /dev/rfcomm*
Date: Mon, 23 Jul 2007 15:36:10 +0200 [thread overview]
Message-ID: <1185197769.46a4aec9d9dee@webmail.epfl.ch> (raw)
Hello !
I would like to know if it is possible to use /dev/ttyS* instead of /dev/rfcomm*
to connect to a bluetooth device.
Indeed I tried :
rfcomm connect /dev/ttyS2 xx:xx:xx:xx:xx:xx
But I get :
Connected /dev/rfcomm0 to xx:xx:xx:xx:xx:xx on channel 1
Any help would be appreciated
Thanks
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2007-07-23 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 13:36 steve.morard [this message]
2007-07-23 13:41 ` [Bluez-users] Use /dev/ttyS* instead of /dev/rfcomm* Manuel Naranjo
2007-07-23 14:21 ` 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=1185197769.46a4aec9d9dee@webmail.epfl.ch \
--to=steve.morard@epfl.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox