From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Chase Douglas <chase.douglas@canonical.com>,
Ed Tomlinson <edt@aei.ca>, Greg KH <gregkh@suse.de>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.39.1
Date: Mon, 13 Jun 2011 14:27:39 -0300 [thread overview]
Message-ID: <20110613172739.GA2661@joana> (raw)
In-Reply-To: <alpine.LNX.2.00.1106130010360.22872@pobox.suse.cz>
* Jiri Kosina <jkosina@suse.cz> [2011-06-13 00:11:04 +0200]:
> On Wed, 8 Jun 2011, Gustavo F. Padovan wrote:
>
> > > > 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.
> >
> > This patch is in my tree. It will be on its way to Linus' tree today.
>
> Doesn't seem to be present in Linus' tree as of today. Has there been any
> issue discovered in the meantime?
No, it is on wireless-2.6 right now. Then goes to net-2.6 and finally linus-2.6.
Gustavo
next prev parent reply other threads:[~2011-06-13 17:27 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
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 [this message]
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=20110613172739.GA2661@joana \
--to=padovan@profusion.mobi \
--cc=chase.douglas@canonical.com \
--cc=edt@aei.ca \
--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).