linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Manuel Naranjo <manuel@aircable.net>
Cc: BlueZ <linux-bluetooth@vger.kernel.org>
Subject: Re: EDR support
Date: Fri, 17 Dec 2010 12:27:06 +0100	[thread overview]
Message-ID: <1292585241.2658.0.camel@aeonflux> (raw)
In-Reply-To: <4D03DC83.8010200@aircable.net>

Hi Manuel,

> I was checking the latest BlueZ source code and the kernel source code, 
> and I noticed that by default EDR is disabled, when a dongle is detected 
> net/bluetooth/hci_core.c initializes the packet types with DM1, DH1 and 
> HV1, and then net/bluetooth/hci_event.c does it for DM3-5 DH3-5 and 
> HV3-5, but it never initializes the 2DHx or 3DHx. Was it made on purpose 
> or is it a bug in the code?

you have read the specification and realized that EDR uses inverse
values?

Regards

Marcel



  reply	other threads:[~2010-12-17 11:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-11 20:18 EDR support Manuel Naranjo
2010-12-17 11:27 ` Marcel Holtmann [this message]
2010-12-17 16:41   ` [RFC][PATCH] " Manuel Naranjo

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=1292585241.2658.0.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=manuel@aircable.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).