linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lamarque Vieira Souza <lamarque@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org,
	Marcel Holtmann <marcel@holtmann.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Problem with Acer Bluetooth Optical Rechargeable Mouse
Date: Fri, 25 Dec 2009 22:40:58 -0200	[thread overview]
Message-ID: <200912252240.59052.lamarque@gmail.com> (raw)
In-Reply-To: <200909221319.45013.lamarque@gmail.com>

	Any news about this patch? It has not entered kernel 2.6.32 (nor even 
2.6.32.2), is there any reason why?

Em Terça-feira 22 Setembro 2009, Lamarque Vieira Souza escreveu:
> Em Terça-feira 22 Setembro 2009, Jiri Kosina escreveu:
> > Hi,
> >
> > could you please resend your patch? It has either been lost somewhere on
> > the way, or in the dark depths of my inbox, so I am not really sure which
> > one you are referring to, sorry.
> 
> Marks Acer Bluetooth Optical Rechargeable Mouse from Ferrari 4005 notebook
>  to be ignored by hid core. This change makes hid core to use input session
>  instead of hid session with that mouse. With hid session the mouse cursor
>  moves too laggy, using input session corrects this problem.
> 
> Signed-off-by: Lamarque V. Souza <lamarque@gmail.com>
> 
> diff -Nru --show-c-function a/drivers/hid/hid-core.c
>  b/drivers/hid/hid-core.c --- a/drivers/hid/hid-core.c	2009-08-13
>  20:45:11.000000000 -0300
> +++ b/drivers/hid/hid-core.c	2009-08-13 22:25:54.504677594 -0300
> @@ -1636,6 +1636,7 @@ static const struct hid_device_id hid_ig
>  	{ HID_USB_DEVICE(USB_VENDOR_ID_WISEGROUP,
>  USB_DEVICE_ID_1_PHIDGETSERVO_20) },
>  	{ HID_USB_DEVICE(USB_VENDOR_ID_WISEGROUP, USB_DEVICE_ID_8_8_4_IF_KIT) },
>  	{ HID_USB_DEVICE(USB_VENDOR_ID_YEALINK,
>  USB_DEVICE_ID_YEALINK_P1K_P4K_B2K) },
> +	{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_KYE, 0x0058) },
>  	{ }
>  };
> 


-- 
Lamarque V. Souza
http://www.geographicguide.com/brazil.htm
Linux User #57137 - http://counter.li.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-12-26  0:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07  1:47 Problem with Acer Bluetooth Optical Rechargeable Mouse Lamarque Vieira Souza
2009-08-08  0:38 ` Jiri Kosina
2009-08-08  1:23   ` Lamarque Vieira Souza
2009-08-13 11:47     ` Jiri Kosina
2009-08-13 23:05       ` Lamarque Vieira Souza
2009-08-13 23:52       ` Lamarque Vieira Souza
2009-08-14  1:30         ` Lamarque Vieira Souza
2009-08-14 11:08           ` Jiri Kosina
2009-08-14 16:34             ` Lamarque Vieira Souza
2009-09-16  0:44               ` Lamarque Vieira Souza
2009-09-22 15:34                 ` Jiri Kosina
2009-09-22 16:19                   ` Lamarque Vieira Souza
2009-09-24  9:39                     ` Jiri Kosina
2009-09-24 13:43                       ` Lamarque Vieira Souza
2009-12-26  0:40                     ` Lamarque Vieira Souza [this message]
2010-01-04 11:33                       ` Jiri Kosina
2010-01-04 11:54                         ` Lamarque Vieira Souza

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=200912252240.59052.lamarque@gmail.com \
    --to=lamarque@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=marcel@holtmann.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).