From: Guennadi Liakhovetski <gl@dsa-ac.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] [REGRESSION] last working kernel 2.6.18
Date: Tue, 7 Aug 2007 17:07:40 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.63.0708071702431.8578@pcgl.dsa-ac.de> (raw)
Hi,
Doing "hcitool cc" under 2.6.18 establishes a connection and keeps it
open, which can be confirmed per "hcitool cc". Under 2.6.20 and 2.6.22 a
connection gets established, but is immediately (within 1-2 seconds)
broken. Is it a change in interfaces, is one supposed to connect
differently now, or is there a bug somewhere? It is hard to believe, that
such a bug could stay unnoticed and unfixed for at least 2 kernel
releases, so, has anything been changed in the API? As a partner a Linux
system with a 2.4.21 kernel is used. We have only tried thee three (.18,
.20, and .22) kernel versions so far.
Thanks
Guennadi
---------------------------------
Guennadi Liakhovetski, Ph.D.
DSA Daten- und Systemtechnik GmbH
Pascalstr. 28
D-52076 Aachen
Germany
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2007-08-07 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 15:07 Guennadi Liakhovetski [this message]
2007-08-07 15:25 ` [Bluez-users] [REGRESSION] last working kernel 2.6.18 Guennadi Liakhovetski
2007-08-07 15:32 ` Marcel Holtmann
2007-08-07 15:56 ` Guennadi Liakhovetski
2007-08-07 16:05 ` 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=Pine.LNX.4.63.0708071702431.8578@pcgl.dsa-ac.de \
--to=gl@dsa-ac.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox