Return-Path: To: bluez-devel@lists.sourceforge.net From: Pascal Date: Mon, 18 Jun 2007 16:00:35 +0200 Message-ID: References: <1181925876.31424.326.camel@cookie.hadess.net> <1181977540.6846.38.camel@aeonflux.inter-touch.com> <1182011715.31424.346.camel@cookie.hadess.net> <1182022535.30934.11.camel@aeonflux.inter-touch.com> <1182111907.3161.16.camel@cookie.hadess.net> <1182171997.3161.29.camel@cookie.hadess.net> Mime-Version: 1.0 In-Reply-To: <1182171997.3161.29.camel@cookie.hadess.net> Subject: Re: [Bluez-devel] HID initiated connections and input service Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net Bastien Nocera wrote: > Jun 18 13:56:40 cookie kernel: hidp_input_report: Unknown key (scancode 0x84) pressed. > Jun 18 13:56:40 cookie kernel: hidp_input_report: Unknown key (scancode 0x82) pressed. > Jun 18 13:56:40 cookie kernel: hidp_input_report: Unknown key (scancode 0x82) released. This typically occurs when the kernel thinks the device is reporting in "boot protocol" mode, for example when net/bluetooth/hidp/core.c:hidp_add_connection() fails to parse the report descriptor and consequently initializes session->input instead of session->hid. Another possible cause is that your kernel does not have HIDP support at all (2.6.20 or earlier). Pascal ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel