From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] rfcomm question 3
Date: Thu, 03 Feb 2005 15:54:41 +0100 [thread overview]
Message-ID: <1107442481.11944.75.camel@pegasus> (raw)
In-Reply-To: <20050203142619.94035.qmail@web60902.mail.yahoo.com>
Hi,
> Now I put all parts of rctest.c in my main program
> to test, and then I found the error message " Can't
> set RFCOMM link mode: Protocol not available (92)",
> and this happens in do_listen part. My T610 has
> included my PC in the menu of "My device". So, what
> have I do so that the RFCOMM link can be set?
you have two possibilities. First you can install a Linux kernel where
RFCOMM link mode is supported. This is a 2.6.10-mh3 or a 2.6.11-rc3.
Second you don't use any link mode features. Means that no master, auth,
encrypt or secure variable should be set to 1.
I really would feel better if you try to understand what the code in
rctest.c means and actually does, instead of only copy it and then try
to use it.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-02-03 14:54 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 14:06 [Bluez-users] rfcomm question 1 Ka Kin Cheung
2005-01-28 17:36 ` Marcel Holtmann
2005-01-29 5:32 ` Ka Kin Cheung
2005-01-29 14:03 ` Marcel Holtmann
2005-01-31 13:41 ` Ka Kin Cheung
2005-01-31 14:22 ` Marcel Holtmann
2005-01-31 14:30 ` Ka Kin Cheung
2005-01-31 14:38 ` Marcel Holtmann
2005-02-01 6:25 ` [Bluez-users] rfcomm question 3 Ka Kin Cheung
2005-02-01 8:14 ` Marcel Holtmann
2005-02-01 14:39 ` Ka Kin Cheung
2005-02-02 2:49 ` Ka Kin Cheung
2005-02-02 3:10 ` Marcel Holtmann
2005-02-02 4:54 ` Ka Kin Cheung
2005-02-02 5:34 ` Marcel Holtmann
2005-02-03 3:42 ` Ka Kin Cheung
2005-02-03 5:22 ` Alain Volmat
2005-02-03 10:50 ` Ka Kin Cheung
2005-02-03 10:59 ` Alain Volmat
2005-02-03 13:01 ` Ka Kin Cheung
2005-02-03 13:20 ` Marcel Holtmann
2005-02-03 14:26 ` Ka Kin Cheung
2005-02-03 14:54 ` Marcel Holtmann [this message]
2005-02-04 16:56 ` Marco Trudel
2005-02-05 12:48 ` Ka Kin Cheung
2005-02-05 13:17 ` Marco Trudel
2005-02-05 13:51 ` Marcel Holtmann
2005-02-05 14:00 ` Marco Trudel
2005-02-05 14:14 ` Marcel Holtmann
2005-02-05 17:39 ` Marco Trudel
2005-02-05 18:08 ` Marcel Holtmann
2005-02-17 5:37 ` Ka Kin Cheung
2005-02-17 6:28 ` Alain Volmat
2005-02-17 9:08 ` mike
2005-02-17 13:08 ` Marco Trudel
2005-02-17 13:54 ` Ka Kin Cheung
2005-02-17 14:10 ` Marco Trudel
2005-02-17 14:43 ` Ka Kin Cheung
2005-02-17 17:04 ` Marco Trudel
2005-02-18 3:28 ` Ka Kin Cheung
2005-02-19 6:49 ` Marco Trudel
2005-02-19 8:27 ` Ka Kin Cheung
2005-02-19 10:06 ` Marco Trudel
2005-02-19 13:45 ` Ka Kin Cheung
2005-02-18 3:33 ` Ka Kin Cheung
2005-02-18 7:51 ` [Bluez-users] multiple instances of OPUSH server Janice M. Ballesteros
2005-02-17 13:14 ` [Bluez-users] rfcomm question 3 Marco Trudel
2005-02-02 3:16 ` Alain Volmat
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=1107442481.11944.75.camel@pegasus \
--to=marcel@holtmann.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.