From: Mayank BATRA <mayank.batra@st.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcidump EDR packet type
Date: Mon, 29 Jan 2007 16:08:08 +0530 [thread overview]
Message-ID: <45BDCE90.5070906@st.com> (raw)
In-Reply-To: <1169573111.5861.12.camel@violet>
Hi Marcel,
> actually it is totally wrong. Sending the 3-DH5 bit only means that you
> wanna enable DM1 and all EDR packets except 3-DH5, because setting that
> bit means you disable that packet type. The corresponding response
> should be DM1 + 3-DH5 bit set.
>
> Since this is custom firmware, it is interpreting the bitmask of the
> change connection packet type in the wrong way.
>
> And to be clear on this, I don't care about the packet mask at all and
> nobody should mess with it (except for testing). Let the link manager
> decide which packet type to use. BlueZ can't make any intelligent
> decision on which is the best packet type. It doesn't know anything
> about the piconet it is using besides its handle.
OK. But my question is why display different packet lists in the command
and event?
< HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
handle 1 ptype 0x2000
Packet type: 3-DH5
...
> HCI Event: Connection Packet Type Changed (0x1d) plen 5
status 0x00 handle 1 ptype 0x1306
Packet type: 2-DH1 2-DH3 2-DH5 3-DH1 3-DH3
Both of them should show the same packet list. Isn't it?
Best Regards,
Mayank
-------------------------------------------------------------------------
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 prev parent reply other threads:[~2007-01-29 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 3:42 [Bluez-devel] hcidump EDR packet type Quinton Yuan
2007-01-23 6:23 ` Marcel Holtmann
2007-01-23 6:38 ` Mayank BATRA
2007-01-23 17:25 ` Marcel Holtmann
2007-01-29 10:38 ` Mayank BATRA [this message]
2007-01-29 10:55 ` Marcel Holtmann
2007-01-29 11:08 ` Mayank BATRA
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=45BDCE90.5070906@st.com \
--to=mayank.batra@st.com \
--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