From: Pierre-Yves Paulus <py@idlum.be>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] CreateProxy usage?
Date: Wed, 02 Apr 2008 18:05:16 +0200 [thread overview]
Message-ID: <47F3AEBC.9010407@idlum.be> (raw)
In-Reply-To: <200803311404.06902.denis.kenzior@trolltech.com>
Hi,
>>>From our experience using RFCOMM ttys is not a good idea. The bluetooth
> rfcomm tty driver in the kernel is too unreliable in certain situations. We
> actually have to patch our device kernels in order to get it working somewhat
> correctly.
I've observed the same thing: rfcomm ttys are not reliable. I've
reported several time Oopses related to them, and so far each time one
Oops/Warning/Bug is fixed, another one happens. Basically, I know no
kernel version which is robust regarding rfcomm ttys.
At the moment I'm looking for a reliable alternative to the ttys. From
what I understand, using an rfcomm socket instead of the ttys would be a
solution, as they are reputed more reliable. But going the socket's way
would mean abandonning the DBus API and linking against the bluetooth
lib, or am I mistaken? My application is currently only accessing BlueZ
through this DBus API, and it is indeed a great API. It would be sad to
have to abandon that to get reliable rfcomm functionnality.
I've no experience at all with the rfcomm sockets from the Bluetooth
library (so take what I say with the required amount of salt). Wouldn't
a solution be to allow opening sockets through the DBus serial service,
instead of the current rfcomm ttys-only approach? I'm talking mostly
about the ConnectService and ConnectServiceFromAdapter in the serial
manager hierarchy.
Denis, could you also expand further about the kind of patching you
perform on your kernels, regarding rfcomm tty's reliability?
Regards,
Pierre-Yves
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-04-02 16:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 2:52 [Bluez-devel] CreateProxy usage? Manuel Naranjo
2008-03-31 3:20 ` Marcel Holtmann
2008-03-31 3:25 ` Manuel Naranjo
2008-03-31 3:31 ` Marcel Holtmann
2008-03-31 3:39 ` Manuel Naranjo
2008-03-31 3:56 ` Marcel Holtmann
2008-03-31 4:01 ` Manuel Naranjo
2008-03-31 4:09 ` Marcel Holtmann
2008-03-31 13:58 ` Manuel Naranjo
2008-03-31 4:04 ` Denis KENZIOR
2008-03-31 13:33 ` Manuel Naranjo
2008-04-02 16:05 ` Pierre-Yves Paulus [this message]
2008-04-02 16:13 ` Manuel Naranjo
2008-04-02 16:22 ` Pierre-Yves Paulus
2008-04-02 23:37 ` Denis KENZIOR
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=47F3AEBC.9010407@idlum.be \
--to=py@idlum.be \
--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