Message-ID: <46A4B027.6090806@gmail.com>
Date: Mon, 23 Jul 2007 10:41:59 -0300
From: Manuel Naranjo <naranjo.manuel@gmail.com>
MIME-Version: 1.0
To: BlueZ users <bluez-users@lists.sourceforge.net>
References: <1185197769.46a4aec9d9dee@webmail.epfl.ch>
In-Reply-To: <1185197769.46a4aec9d9dee@webmail.epfl.ch>
Subject: Re: [Bluez-users] Use /dev/ttyS* instead of /dev/rfcomm*
Reply-To: BlueZ users <bluez-users@lists.sourceforge.net>
Content-Type: text/plain; charset="us-ascii"
Sender: bluez-users-bounces@lists.sourceforge.net
Errors-To: bluez-users-bounces@lists.sourceforge.net

You can create a symlink :D.
ln -s /dev/rfcomm# /dev/ttyS@
Where @ is not a used ttyS
> 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
>
>   


-------------------------------------------------------------------------
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