From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753365Ab0BIHWn (ORCPT ); Tue, 9 Feb 2010 02:22:43 -0500 Received: from mail-iw0-f182.google.com ([209.85.223.182]:62572 "EHLO mail-iw0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752517Ab0BIHWl convert rfc822-to-8bit (ORCPT ); Tue, 9 Feb 2010 02:22:41 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=MagVuUcZUmMktGXI18Fh9L6shkpEEdeG9OIs5DKhhjcIp3ms7kybyWhJSYX0yeFtfK v0y5gJOVl5aOYAWDzYip1ktu1Bt1sOFbUg8GS7inNMTiSo+IxUwFwp5icNsbR1693vI1 FSqLCHbQ7RX8bQLBhqUN4/OntftuQ5d+5T4kk= MIME-Version: 1.0 In-Reply-To: <201002082106.06301.edt@aei.ca> References: <87vdebfvfk.fsf@troilus.org> <1265392303.31341.235.camel@localhost.localdomain> <201002082106.06301.edt@aei.ca> Date: Mon, 8 Feb 2010 23:22:40 -0800 Message-ID: Subject: Re: [PATCH] Bluetooth: Keep a copy of each HID device's report descriptor. From: Justin Mattock To: Ed Tomlinson Cc: Marcel Holtmann , Michael Poole , Bastien Nocera , Jiri Kosina , "Gunn, Brian" , Ping , linux-kernel@vger.kernel.org, BlueZ development Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > TIA > Ed Tomlinson > > On Friday 05 February 2010 12:51:43 Marcel Holtmann wrote: >> Hi Michael, >> >> > > looks good to me. I just prefer that you do the allocation of the report >> > > descriptor before the HID object: >> > >> > An updated patch is below.  Sorry for the delay -- inclement weather >> > here got in the way of testing this as quickly as I would have liked. >> > >> > From e245ef87247f5e257db40c412af7991c9af375ab Mon Sep 17 00:00:00 2001 >> > From: Michael Poole >> > Date: Fri, 5 Feb 2010 12:21:38 -0500 >> > Subject: [PATCH] Bluetooth: Keep a copy of each HID device's report descriptor. >> > >> > The report descriptor is read by user space (via the Service >> > Discovery Protocol), so it is only available during the ioctl >> > to connect.  However, the probe function that needs the >> > descriptor might not be called until a specific module is >> > loaded.  Keep a copy of the descriptor so it is available for >> > later use. >> >> patch has been applied. Thanks. >> >> Regards >> >> Marcel >> >> >> -- >> 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/ > Hi, > > I have been trying to test Michael's magic mouse drivers against 32.7 (or .8-rc). Is there a tree > based on .32 with these patches? If not would it be possible to post the patches to lkml? I do not > mind sorting out a few conflicts - this thread assume one knows a little more about the process being > used here than is obvious. > just got one of those magic things as well. I did apply the patchs to the current HEAD, but am getting a lifeless result i.g. here's what I did: sudo /usr/bin/hcitool scan sudo /usr/bin/simple-agent hci0 D4:9A:20:88:C7:48 sudo /usr/bin/dbus-send --system --dest=org.bluez --print-reply /org/bluez/1897/hci0/dev_D4_9A_20_88_C7_48 org.bluez.Input.Connect sudo /usr/bin/test-device trusted D4:9A:20:88:C7:48 the thing works after that(no scroll), fast cursor though. then reboot once up and running nothing. cat /var/log/daemon.log (shows this) Feb 8 22:57:40 Linux-1 bluetoothd[1973]: link_key_request (sba=00:25:00:C0:6C:4F, dba=D4:9A:20:88:C7:48) Feb 8 22:58:21 Linux-1 bluetoothd[1973]: last message repeated 5 times Feb 8 22:59:21 Linux-1 bluetoothd[1973]: last message repeated 3 times Feb 8 23:03:10 Linux-1 bluetoothd[1973]: link_key_request (sba=00:25:00:C0:6C:4F, dba=D4:9A:20:88:C7:48) (could be missing something though(don't use gnome/kde-bluetooth)although mightymouse works). bluez is v59(in the morning I can load up the latest and see). and then go from there if you need me to be a test subject let me know. BTW: ed I can attach the patch(seperate e-mail) which is updated to rc6*(to the most part) if you want.? this way you can give it a try, then once these are in the mainline you wont have todo so. -- Justin P. Mattock From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 In-Reply-To: <201002082106.06301.edt@aei.ca> References: <87vdebfvfk.fsf@troilus.org> <1265392303.31341.235.camel@localhost.localdomain> <201002082106.06301.edt@aei.ca> Date: Mon, 8 Feb 2010 23:22:40 -0800 Message-ID: Subject: Re: [PATCH] Bluetooth: Keep a copy of each HID device's report descriptor. From: Justin Mattock To: Ed Tomlinson Cc: Marcel Holtmann , Michael Poole , Bastien Nocera , Jiri Kosina , "Gunn, Brian" , Ping , linux-kernel@vger.kernel.org, BlueZ development Content-Type: text/plain; charset=ISO-8859-1 List-ID: > TIA > Ed Tomlinson > > On Friday 05 February 2010 12:51:43 Marcel Holtmann wrote: >> Hi Michael, >> >> > > looks good to me. I just prefer that you do the allocation of the re= port >> > > descriptor before the HID object: >> > >> > An updated patch is below. =A0Sorry for the delay -- inclement weather >> > here got in the way of testing this as quickly as I would have liked. >> > >> > From e245ef87247f5e257db40c412af7991c9af375ab Mon Sep 17 00:00:00 2001 >> > From: Michael Poole >> > Date: Fri, 5 Feb 2010 12:21:38 -0500 >> > Subject: [PATCH] Bluetooth: Keep a copy of each HID device's report de= scriptor. >> > >> > The report descriptor is read by user space (via the Service >> > Discovery Protocol), so it is only available during the ioctl >> > to connect. =A0However, the probe function that needs the >> > descriptor might not be called until a specific module is >> > loaded. =A0Keep a copy of the descriptor so it is available for >> > later use. >> >> patch has been applied. Thanks. >> >> Regards >> >> Marcel >> >> >> -- >> 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 =A0http://vger.kernel.org/majordomo-info.html >> Please read the FAQ at =A0http://www.tux.org/lkml/ > Hi, > > I have been trying to test Michael's magic mouse drivers against 32.7 (or= .8-rc). Is there a tree > based on .32 with these patches? If not would it be possible to post the= patches to lkml? I do not > mind sorting out a few conflicts - this thread assume one knows a little = more about the process being > used here than is obvious. > just got one of those magic things as well. I did apply the patchs to the current HEAD, but am getting a lifeless result i.g. here's what I did: sudo /usr/bin/hcitool scan sudo /usr/bin/simple-agent hci0 D4:9A:20:88:C7:48 sudo /usr/bin/dbus-send --system --dest=3Dorg.bluez --print-reply /org/bluez/1897/hci0/dev_D4_9A_20_88_C7_48 org.bluez.Input.Connect sudo /usr/bin/test-device trusted D4:9A:20:88:C7:48 the thing works after that(no scroll), fast cursor though. then reboot once up and running nothing. cat /var/log/daemon.log (shows this) Feb 8 22:57:40 Linux-1 bluetoothd[1973]: link_key_request (sba=3D00:25:00:C0:6C:4F, dba=3DD4:9A:20:88:C7:48) Feb 8 22:58:21 Linux-1 bluetoothd[1973]: last message repeated 5 times Feb 8 22:59:21 Linux-1 bluetoothd[1973]: last message repeated 3 times Feb 8 23:03:10 Linux-1 bluetoothd[1973]: link_key_request (sba=3D00:25:00:C0:6C:4F, dba=3DD4:9A:20:88:C7:48) (could be missing something though(don't use gnome/kde-bluetooth)although mightymouse works). bluez is v59(in the morning I can load up the latest and see). and then go from there if you need me to be a test subject let me know. BTW: ed I can attach the patch(seperate e-mail) which is updated to rc6*(to the most part) if you want.? this way you can give it a try, then once these are in the mainline you wont have todo so. --=20 Justin P. Mattock