Re: keyboard/trackpad combo unusable on MacBookPro4,1 with bcm5974.ko

2015-04-10 Thread Alan Stern
On Fri, 10 Apr 2015, Christian Böhme wrote: > Alan Stern writes: > > > > Given that hid_mouse_ignore_list[] actually contains the proper > > > (USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING2_ISO) pair > > > as far as I can make out and assuming a properly working compiler, > > > hid_match_

Re: keyboard/trackpad combo unusable on MacBookPro4,1 with bcm5974.ko

2015-03-22 Thread Alan Stern
On Sun, 22 Mar 2015, Christian Böhme wrote: > Alan Stern writes: > > > I came back to this old email today, and it turns out that > > usbhid_probe() already includes the following lines: > > > > if (intf->cur_altsetting->desc.bInterfaceProtocol == > > USB_INTERFACE_PROTO

Re: keyboard/trackpad combo unusable on MacBookPro4,1 with bcm5974.ko

2015-03-22 Thread Christian Böhme
Alan Stern writes: > I came back to this old email today, and it turns out that > usbhid_probe() already includes the following lines: > > if (intf->cur_altsetting->desc.bInterfaceProtocol == > USB_INTERFACE_PROTOCOL_MOUSE) > hid->type = HID_TYPE_USBMOUS

Re: keyboard/trackpad combo unusable on MacBookPro4,1 with bcm5974.ko

2015-03-22 Thread Christian Böhme
Jiri Slaby writes: > It would be helpful to see who is actually bound to the two interfaces > of the device. What's the output of > readlink /sys/bus/usb/devices/≤device>:1.*/driver > for the corresponding ? The mouse should be handled by bcm5974, > the other by usbhid (and by hid-apple one lay

Re: keyboard/trackpad combo unusable on MacBookPro4,1 with bcm5974.ko

2015-03-17 Thread Jiri Slaby
On 03/17/2015, 03:20 PM, Alan Stern wrote: > On Mon, 2 Mar 2015, Alan Stern wrote: > >> On Fri, 27 Feb 2015, Christian Böhme wrote: >> >>> Alan Stern writes: >>> > Specifically, HID_QUIRK_IGNORE_MOUSE existed in 2.6.27 > and was dealt with in drivers/hid/usbhid/hid-core.c:730, > there

Re: keyboard/trackpad combo unusable on MacBookPro4,1 with bcm5974.ko

2015-03-17 Thread Alan Stern
On Mon, 2 Mar 2015, Alan Stern wrote: > On Fri, 27 Feb 2015, Christian Böhme wrote: > > > Alan Stern writes: > > > > > > Specifically, HID_QUIRK_IGNORE_MOUSE existed in 2.6.27 > > > > and was dealt with in drivers/hid/usbhid/hid-core.c:730, > > > > thereby somehow "fixing things". But those li

Re: keyboard/trackpad combo unusable on MacBookPro4,1 with bcm5974.ko

2015-03-03 Thread Christian Böhme
Alan Stern writes: > I agree. The problem is that the HID core now tests for hdev->type == > HID_TYPE_USBMOUSE, but it doesn't test for bInterfaceProtocol == > USB_INTERFACE_PROTOCOL_MOUSE like the older code did. > > This issue should be reported to the author of that second commit > (CC'ed).

Re: keyboard/trackpad combo unusable on MacBookPro4,1 with bcm5974.ko

2015-03-02 Thread Alan Stern
On Fri, 27 Feb 2015, Christian Böhme wrote: > Alan Stern writes: > > > > Specifically, HID_QUIRK_IGNORE_MOUSE existed in 2.6.27 > > > and was dealt with in drivers/hid/usbhid/hid-core.c:730, > > > thereby somehow "fixing things". But those lines (and > > > the symbol) disappeared after 2.6.27.

Re: keyboard/trackpad combo unusable on MacBookPro4,1 with bcm5974.ko

2015-02-27 Thread Christian Böhme
Alan Stern writes: > > Specifically, HID_QUIRK_IGNORE_MOUSE existed in 2.6.27 > > and was dealt with in drivers/hid/usbhid/hid-core.c:730, > > thereby somehow "fixing things". But those lines (and > > the symbol) disappeared after 2.6.27. Why were they > > removed? > > They weren't removed. T

Re: keyboard/trackpad combo unusable on MacBookPro4,1 with bcm5974.ko

2015-02-27 Thread Alan Stern
On Fri, 27 Feb 2015, "Christian Böhme" wrote: > Hello all, > > this is a response to > > https://bugzilla.kernel.org/show_bug.cgi?id=14987#c6 > > whose main thread more or less merely rehashes what was > already said in other (bug) reports before it elsewhere. > > I'd like for this to be a rem

keyboard/trackpad combo unusable on MacBookPro4,1 with bcm5974.ko

2015-02-26 Thread Christian Böhme
Hello all, this is a response to https://bugzilla.kernel.org/show_bug.cgi?id=14987#c6 whose main thread more or less merely rehashes what was already said in other (bug) reports before it elsewhere. I'd like for this to be a reminder that the issue never really was resolved but left lingering b