linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] ACL packet types
Date: Wed, 28 Jun 2006 20:16:44 +0200	[thread overview]
Message-ID: <1151518604.26495.13.camel@localhost> (raw)
In-Reply-To: <1151505157.599646.3431.nullmailer@galant.ukfsn.org>

Hi Iain,

>    In bluez-lib-2.25 (I'm not up on latest version, sorry) there are
> functions to convert packet types to bit masks and vice versa but they are
> wrong.
> 
> If you look at the 2.0 Core specification for the "Create Connection"
> command, it shows that the bits for the 2Mbps and 3Mbps packet types are
> inverted - ie, when the bit is set, the packet type is NOT permitted.
> 
> I noticed this using hcidump, it prints the packet types wrongly.
> 
> 0xff1e = DH1 DM1 DH3 DM3 DH5 DM5
> 0xcc18 = DH1 DM1 DH3 DM3 DH5 DM5 2-DH1 3-DH1 2-DH3 3-DH3 2-DH5 3-DH5

I don't get your point. If you see 2-x and 3-x, it means that EDR has
been disabled. You will see this if a EDR capable dongle tries to
connect to a non-EDR capable device.

Regards

Marcel



Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2006-06-28 18:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 14:32 [Bluez-devel] ACL packet types Iain Hibbert
2006-06-28 18:16 ` 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=1151518604.26495.13.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sf.net \
    --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;
as well as URLs for NNTP newsgroup(s).