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:38:04 +0530 [thread overview]
Message-ID: <45BDD594.9040000@st.com> (raw)
In-Reply-To: <1170068129.15389.122.camel@violet>
Hi Marcel,
> that must be a bug in their firmware. They should be the same with the
> only exception of DM1.
>
> My assumption is that change connection packet type is treating this
> command as enable 3-DH5 only. However that is not what that command
> means. It means enable DM1 and all 2-* and 3-* packets except 3-DH5.
You are right. Its the job of the firmware and not the host to toggle
the EDR packet type bits (in contrast to what I said in a previous post).
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
prev parent reply other threads:[~2007-01-29 11:08 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
2007-01-29 10:55 ` Marcel Holtmann
2007-01-29 11:08 ` Mayank BATRA [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=45BDD594.9040000@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 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.