All of lore.kernel.org
 help / color / mirror / Atom feed
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:56:33 +0100	[thread overview]
Message-ID: <1076342193.6869.205.camel@pegasus> (raw)
In-Reply-To: <1076340484.1167.79.camel@localhost>

Hi Nils,

> OK, maybe like this:
> ----->
> xx. RFCOMM connection using minicom or other tool fails, why?
> Problem: In case you have created the RFCOMM link using the "rfcomm
> bind" function this can be caused by application timeouts. This is not a
> problem of BlueZ or the RFCOMM implementation but rather a problem with
> the different nature of a RFCOMM virtual tty and a physical serial tty
> device which is normally used by those applications. Some applications
> implement a timeout protection function while opening the port. If
> opening the port takes longer than a certain amount of time then the
> application fails. A serial tty will usually only take several
> microseconds to open while the RFCOMM virtual tty can take several
> seconds. Additionally opening requires to create a connection to the
> remote Bluetooth device, closing the port closes the connection again.
> Application which open and close the port frequently may thus also fail!
> Solution: Try to create the connection before starting you application.
> This can be done by the "rfcomm connect" function. The Bluetooth
> connection will then remain until the rfcomm utility is stopped.
> <-----
> 
> A bit lengthy maybe ;)

thank you. I stripped a little bit and put it only ;)

> How does BT-HID mouse work?

The best is you follow this HOWTO

	http://www.bueche.ch/comp/mx900/mx900.html

And don't use the bthid from Peter Klausler until you patch it up.

> I have a BT mouse here but the bthid daemon does not connect to it nor
> can I connect another service like rfcomm to it...

RFCOMM will never work, because HID is only based on L2CAP.

> The accompanied keyboard works like a charm!

If the keyboard works, the mouse should work also.

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

  parent reply	other threads:[~2004-02-09 15:56 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
     [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 [this message]
     [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=1076342193.6869.205.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 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.