From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] L2CAP device specific information
Date: Thu, 28 Sep 2006 11:18:54 +0200 [thread overview]
Message-ID: <1159435134.21120.7.camel@localhost> (raw)
Hi,
with the release of bluez-utils-3.6 and bluez-utils-3.6.1, I added an
additional command to the l2test program to determine the extended
features of the remote L2CAP implementation. This will help us to
identify which devices will support retransmission and flow control
and/or connectionless connections.
# ./l2test -z 00:04:76:*:*:*
Connectionless MTU size is 670
Extended feature mask is not supported
The program must be run as root and can be found in the test directory
of bluez-utils. The switch --enable-test for configure enables its
compilation. There is not need to install it, you can run it from that
directory directly. If it stalls, then this might be a bug in the remote
L2CAP implementation when it doesn't answer to information requests. In
this case you might wanna run hcidump and check what happens.
So please report back information about your devices and I will collect
them and make them public at this location:
http://www.holtmann.org/linux/bluetooth/l2cap.html
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-09-28 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 9:18 Marcel Holtmann [this message]
2006-09-28 13:11 ` [Bluez-devel] L2CAP device specific information Martin Röhricht
2006-09-28 13:38 ` 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=1159435134.21120.7.camel@localhost \
--to=marcel@holtmann.org \
--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