From: "Anthony Yulo" <strikewing16th@hotmail.com>
To: "bluez devel" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] rfcomm error message?
Date: Tue, 20 Jan 2004 21:35:32 +0800 [thread overview]
Message-ID: <Law11-OE68ZvRETrSel0000e9e5@hotmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 408 bytes --]
hi!!! :)
i tried using the rfcomm program to test for connections between cellphone and linux pc...
anton@maverick home]rfcomm -i hci0 listen 2
Waiting for connection on channel 1
..when i try to connect the smartphone the program returns and outputs the error message:
"can't create RFCOMM TTY: Operation not supported"
whats wrong with this? do i have to set some configuration files?
[-- Attachment #2: Type: text/html, Size: 1270 bytes --]
next reply other threads:[~2004-01-20 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 13:35 Anthony Yulo [this message]
2004-01-20 13:49 ` [Bluez-devel] rfcomm error message? Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-01-21 8:32 Anthony Yulo
2004-01-21 12:45 ` Marcel Holtmann
[not found] ` <LAW11-OE47NCsn8BWz60002faea@hotmail.com>
2004-01-21 15:01 ` 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=Law11-OE68ZvRETrSel0000e9e5@hotmail.com \
--to=strikewing16th@hotmail.com \
--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