DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        b=YGVTAWW4ngyQGXAt2BXVsMGhRvCV6GMgixD4/9qWjWlwKw+/8kHPHzx52EQ+jPIDZk
         G2H7LEFrq+BNHh/b2467oRD2gYrbzwd/9RTbTACN6e2c5f6f8UYLtrl6NZPWWTbeeWUb
         sy5IqbRuxgf7oGwILJyjLBDx2HZSKFloEAZiQ=
MIME-Version: 1.0
Reply-To: corey@kansanian.com
In-Reply-To: <013c01cc1af9$361b00e0$a25102a0$@ytram.com>
References: <BANLkTinG_qCtHQYRYFQUJ9oGv4H1cuznWg@mail.gmail.com>
	<201105250711.17971.edt@aei.ca>
	<20110525113614.GQ2480@null>
	<201105250812.43246.edt@aei.ca>
	<5B4B9A479BF6994B88EA975675EC5B79057A399D82@MES1OS2SXC003.mes1.tconet.net>
	<BANLkTi=ec3bh24=2r8f3tmj2g0n0bMnq1Q@mail.gmail.com>
	<5B4B9A479BF6994B88EA975675EC5B79057A60296D@MES1OS2SXC003.mes1.tconet.net>
	<013c01cc1af9$361b00e0$a25102a0$@ytram.com>
Date: Wed, 25 May 2011 21:11:19 -0400
Message-ID: <BANLkTikxR3AZJK5Bhc5b=7dq6CbXd2iBtQ@mail.gmail.com>
Subject: Re: Linux 2.6.39
From: Corey Boyle <corey@kansanian.com>
To: wyrles@ytram.com, Ville Tervo <ville.tervo@nokia.com>,
        "Cufi, Carles" <carles.cufi@nordicsemi.no>
Cc: Ed Tomlinson <edt@aei.ca>,
        Bluettooth Linux <linux-bluetooth@vger.kernel.org>,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 3158
Lines: 70

On Wed, May 25, 2011 at 12:31 PM, Tom Allebrandi <wyrles@ytram.com> wrote:
> -----Original Message-----
> From: linux-bluetooth-owner@vger.kernel.org
> [mailto:linux-bluetooth-owner@vger.kernel.org] On Behalf Of Cufi, Carles
> Sent: Wednesday, May 25, 2011 7:15 AM
> To: corey@kansanian.com
> Cc: Ed Tomlinson; Ville Tervo; Bluettooth Linux;
> linux-kernel@vger.kernel.org
> Subject: RE: Linux 2.6.39
>
> (Snipping...)
> On Wed, May 25, 2011 at 8:46 AM, Cufi, Carles <carles.cufi@nordicsemi.no>
> wrote:
>> On Wednesday 25 May 2011 07:36:14 Ville Tervo wrote:
>>> On Wed, May 25, 2011 at 07:11:17AM -0400, ext Ed Tomlinson wrote:
>>> > On Wednesday 25 May 2011 06:54:54 Corey Boyle wrote:
>>> > > > On Mon, May 23, 2011 at 06:08:36PM -0400, ext Ed Tomlinson wrote:
>>> > > > > On Saturday 21 May 2011 16:31:00 Ed Tomlinson wrote:
>>> > > > > > On Saturday 21 May 2011 13:56:20 Milan Oravec wrote:
> ...
>>> > Read Local Version Information (0x04|0x0001) plen 0
>>> > > HCI Event: Command Complete (0x0e) plen 12
>>> > ? ? Read Local Version Information (0x04|0x0001) ncmd 1
>>> > ? ? status 0x00
>>> > ? ? HCI Version: 1.1 (0x1) HCI Revision: 0x20d
> *************************
>>> > ? ? LMP Version: 1.1 (0x1) LMP Subversion: 0x20d
> *************************
>>> > ? ? Manufacturer: Cambridge Silicon Radio (10) < HCI Command: Set
>>> > Event Mask (0x03|0x0001) plen 8
>>> > ? ? Mask: 0xfffffbff00000000
> *************************
>>> > > HCI Event: Command Complete (0x0e) plen 4
>>> > ? ? Set Event Mask (0x03|0x0001) ncmd 1
>>> > ? ? status 0x12
>>> > ? ? Error: Invalid HCI Command Parameters
>>
>>Set Event Mask has been in the Bluetooth Spec since day 1, so it must be
> the bitmask, which has been extended with each new spec release to cover
> newly >added events. Looking at the latest spec, and judging by the year
> your chipset was released in (it probably is a 1.1 compliant chipset) I
> believe that >0x000000008FFFFFFF is the highest event mask it would support
> (up until and including Page Scan Repetition Mode Change Event), but since I
> don't have the >old 1.1 spec around I may be one or two bits off.
>
> The device appears to have identified itself as CSR firmware using Bluetooth
> version 1.1.
>
> I do happen to have the 1.1 spec lying around :-), for Set_Event_Mask it
> says
>
> 0x0000000100000000
> To ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?Reserved for future use
> 0x8000000000000000
>
> 0x00000000FFFFFFFF ? ? ?Default (All events enabled)
>

I am beginning to think that my adapter simply does not support this
command.  I have tried with all the suggested bitmasks, all zeros, all
ones, all combinations where a single bit is set, etc.  I'm not sure
where to go from here other than add a flag which incidates that
certain devices don't support this command so it can be skipped.
Again, the only way I have gotten it to work is by not sending the
command at all.  Thoughts?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/