From: Marcel Holtmann <marcel@holtmann.org>
To: Nils Faerber <nils.faerber@kernelconcepts.de>
Cc: bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] Pairing fails with RFCOMM
Date: Mon, 09 Feb 2004 16:01:09 +0100 [thread overview]
Message-ID: <1076338869.6869.174.camel@pegasus> (raw)
In-Reply-To: <1076337219.2892.57.camel@localhost>
Hi Nils,
> It seems that minicom implements a timeout on open()ing the tty. This
> times out before the authentication took place. When using rfcomm
> connect first or using cat the connect works.
> So this is indeed not a BlueZ/RFCOMM problem, because IMHO there is no
> real way to fix it (only possible solution would be to always allow
> open()ing the port, paired or not, connected or not).
this is not really a solution, because it moves the detection of
Bluetooth connection errors out of the scope.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-02-09 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 17:03 [Bluez-devel] Pairing fails with RFCOMM Nils Faerber
2004-02-06 19:57 ` Marcel Holtmann
[not found] ` <1076337219.2892.57.camel@localhost>
2004-02-09 15:01 ` Marcel Holtmann [this message]
[not found] ` <1076339124.1169.67.camel@localhost>
2004-02-09 15:08 ` Marcel Holtmann
[not found] ` <1076340484.1167.79.camel@localhost>
2004-02-09 15:56 ` Marcel Holtmann
[not found] ` <1076342698.1167.90.camel@localhost>
2004-02-09 16:14 ` 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=1076338869.6869.174.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sf.net \
--cc=nils.faerber@kernelconcepts.de \
/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