linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ed Tomlinson <edt@aei.ca>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Chase Douglas <chase.douglas@canonical.com>,
	Greg KH <gregkh@suse.de>,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.39.1
Date: Thu, 9 Jun 2011 08:07:26 -0400	[thread overview]
Message-ID: <201106090807.27459.edt@aei.ca> (raw)
In-Reply-To: <alpine.LNX.2.00.1106081740040.22872@pobox.suse.cz>

On Wednesday 08 June 2011 11:41:03 Jiri Kosina wrote:
> On Wed, 8 Jun 2011, Chase Douglas wrote:
> 
> > > I also played a bit with 1.1 CSR dongle and couldn't find any mask that would
> > > be accepted. I think this command can be left out for older than 1.2 devices.
> > > 
> > > Following patch should do it. Could you verify it. I don't have access to old
> > > hw ATM.
> > > 
> > > diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
> > > index 19cd4af..86d1e26 100644
> > > --- a/net/bluetooth/hci_event.c
> > > +++ b/net/bluetooth/hci_event.c
> > > @@ -477,14 +477,16 @@ static void hci_setup_event_mask(struct hci_dev *hdev)
> > >          * command otherwise */
> > >         u8 events[8] = { 0xff, 0xff, 0xfb, 0xff, 0x00, 0x00, 0x00, 0x00 };
> > >  
> > > -       /* Events for 1.2 and newer controllers */
> > > -       if (hdev->lmp_ver > 1) {
> > > -               events[4] |= 0x01; /* Flow Specification Complete */
> > > -               events[4] |= 0x02; /* Inquiry Result with RSSI */
> > > -               events[4] |= 0x04; /* Read Remote Extended Features Complete */
> > > -               events[5] |= 0x08; /* Synchronous Connection Complete */
> > > -               events[5] |= 0x10; /* Synchronous Connection Changed */
> > > -       }
> > > +       /* CSR 1.1 dongles does not accept any bitfield so don't try to set
> > > +        * any event mask for pre 1.2 devices */
> > > +       if (hdev->lmp_ver <= 1)
> > > +               return;
> > > +
> > > +       events[4] |= 0x01; /* Flow Specification Complete */
> > > +       events[4] |= 0x02; /* Inquiry Result with RSSI */
> > > +       events[4] |= 0x04; /* Read Remote Extended Features Complete */
> > > +       events[5] |= 0x08; /* Synchronous Connection Complete */
> > > +       events[5] |= 0x10; /* Synchronous Connection Changed */
> > >  
> > >         if (hdev->features[3] & LMP_RSSI_INQ)
> > >                 events[4] |= 0x04; /* Inquiry Result with RSSI */
> > 
> > Where did this patch come from? I don't see it in Linus' tree. If this
> > patch is merged, I can test the a new kernel out to see if we should
> > back out the commit from Jiri. However, right now my magic trackpad
> > (which has the same issue as the magic mouse) works fine on plain 2.6.39.1.
> 
> It might be because of different versions of CSR dongles you guys might 
> have.
> 
> I am still a bit lost here -- Ed, do you say that with the patch above, 
> and with my patch reverted, your device is working properly?

Yes.  Your understanding is correct.

Thanks,
Ed

  reply	other threads:[~2011-06-09 12:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110603003835.GA20381@kroah.com>
     [not found] ` <201106032236.41294.edt@aei.ca>
     [not found]   ` <4DED20C6.1020701@canonical.com>
2011-06-06 23:26     ` Linux 2.6.39.1 Ed Tomlinson
2011-06-08 15:36       ` Chase Douglas
2011-06-08 15:41         ` Jiri Kosina
2011-06-09 12:07           ` Ed Tomlinson [this message]
2011-06-09 12:42             ` Jiri Kosina
2011-06-08 18:01         ` Gustavo F. Padovan
2011-06-12 22:11           ` Jiri Kosina
2011-06-13 17:27             ` Gustavo F. Padovan
2011-06-16 10:25               ` Jiri Kosina
2011-06-16 19:10                 ` Gustavo F. Padovan

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=201106090807.27459.edt@aei.ca \
    --to=edt@aei.ca \
    --cc=chase.douglas@canonical.com \
    --cc=gregkh@suse.de \
    --cc=jkosina@suse.cz \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@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).