From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Cc: swegmann@repr.at
Subject: Re: [Bluez-devel] rfcomm bluez problem
Date: Tue, 20 Sep 2005 13:45:28 +0200 [thread overview]
Message-ID: <1127216728.5168.24.camel@localhost.localdomain> (raw)
In-Reply-To: <432CA117.5060109@psi.co.at>
Hi Raphael,
> the connection to my bluetooth modem doesn't work very reliable.
> When I connect successfully, "hcidump -V -X" looks like this:
the support for a 2.4 kernel is deprecated. Move to the latest 2.6
kernel and use the latest hcidump. I am not looking at hex numbers.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-09-20 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 23:04 [Bluez-devel] rfcomm bluez problem Raphael Wegmann
2005-09-20 11:45 ` Marcel Holtmann [this message]
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=1127216728.5168.24.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=swegmann@repr.at \
/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.