linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Lochov" <mlochov@gmx.com>
To: linux-bluetooth@vger.kernel.org
Subject: Frequency Hop Selection Help
Date: Wed, 21 Sep 2011 21:20:53 +0200	[thread overview]
Message-ID: <20110921192053.136390@gmx.com> (raw)

Hi,

This question is more related to the Bluetooth specification that Bluez, specifically I'm trying to understand the frequency hopping selection for Inquiry scan mode. I have a working selection kernel that works perfectly for the basic 79 channel connected state and I now want to alter the inputs to get it working for the Inquriy state.

According to the specification (p94 of v4), BD_ADDR input to the selection kernel is replaced by the GIAC 0x9E8B33 and the DIC 0x00 for inquiry mode, so everything in my selection kernel that used an Address, i replaced with 0x009E8B33. 

The only other major change is the X input, defined as: Xi = { CLKN[16-12] + k_offset + ( CLKN[4-2,0] + CLKN[16-12] ) mod 16 } mod 32. Here I assumed the 4-2,0 bit positions of the native clock to mean I use bits 4,3,2,0. And i used 8 as the k_offset, is this correct?

The problem is I don't get the correct channel values out, but I know my selection kernel works perfectly for connected state so there is a problem specific with my inquiry mode inputs. Either im using the GIAC incorrectly and ignoring the ULAP or im understanding the X = {} forumula wrong.

To make matters more confusing, the sample data (p. 1235) is different across the 3 examples for inquiry mode? The only difference is the ULAP, which I understood was replaced with the GIAC here? So surely only the clock & k_offset should effect the frequency selection in inquiry mode.

Thanks very much.

Michael

                 reply	other threads:[~2011-09-21 19:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110921192053.136390@gmx.com \
    --to=mlochov@gmx.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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).