mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brad Hards <bhards@bigpond.net.au>
To: Chris Faherty <rallymonkey@bellsouth.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Logitech Mouseman Dual Optical defaults to 400cpi
Date: Sun, 9 Jun 2002 18:07:11 +1000	[thread overview]
Message-ID: <200206091807.11524.bhards@bigpond.net.au> (raw)
In-Reply-To: <20020608165243Z317422-22020+923@vger.kernel.org> <20020609002448Z317485-22020+1014@vger.kernel.org>

On Sun, 9 Jun 2002 10:25, Chris Faherty wrote:
> On Saturday 08 June 2002 12:53 pm, Chris Faherty wrote:
> > I can't find any information on how to switch it into 800cpi mode.
>
> Well, I managed to figure it out today.  Sending the special code to the
Was that using Snoopy?

> MouseMan Dual Optical turns it into 800cpi mode.. much better!  Anyhow, I
> just put a test for this particular mouse in the hid_probe() and wrote the
> codes to the mouse.  Not sure if that's the best place.
>
> This is for 2.2.20:
Any objections to me taking this to 2.4 and 2.5?

> --- hid.c-orig  Sun Mar 25 11:37:37 2001
> +++ hid.c       Sat Jun  8 17:55:02 2002
> @@ -1523,6 +1523,19 @@
>
>         printk(" on usb%d:%d.%d\n", dev->bus->busnum, dev->devnum, ifnum);
>
> +#define USB_VENDOR_ID_LOGITECH          0x046d
> +#define USB_DEVICE_ID_LOGITECH_DOPTICAL 0xc012
> +    if ((hid->dev->descriptor.idVendor == USB_VENDOR_ID_LOGITECH) &&
> +        (hid->dev->descriptor.idProduct ==
> USB_DEVICE_ID_LOGITECH_DOPTICAL)) {
> +        printk("Setting Logitech MouseMan Dual Optical for 800cpi\n");
> +        usb_control_msg(hid->dev, usb_sndctrlpipe(hid->dev, 0),
> +            0x0a, USB_DIR_OUT | USB_TYPE_VENDOR | USB_RECIP_ENDPOINT,
> +            0x0000, 0x0000, NULL, 0, HZ);
> +        usb_control_msg(hid->dev, usb_sndctrlpipe(hid->dev, 0),
> +            0x02, USB_DIR_OUT | USB_TYPE_VENDOR | USB_RECIP_ENDPOINT,
> +            0x000e, 0x0004, NULL, 0, HZ);
> +    }
> +
>         return hid;
>  }
This could have been handled by a blacklist table quirk. Any reason why you 
chose to do it this way?

Brad

-- 
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.

  reply	other threads:[~2002-06-09  8:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-08 16:53 Chris Faherty
2002-06-09  0:25 ` Chris Faherty
2002-06-09  8:07   ` Brad Hards [this message]
2002-06-09 15:19     ` Chris Faherty
2002-06-10  0:57       ` Brad Hards
2002-06-10 21:26         ` Vojtech Pavlik
2002-06-11  4:52           ` Chris Faherty
     [not found]           ` <20020611045213.8B1FA59D354@kerberos.suse.cz>
2002-06-11  5:56             ` Vojtech Pavlik
2002-06-11  6:30               ` Chris Faherty
     [not found]               ` <20020611062940.8172959D354@kerberos.suse.cz>
2002-06-11  6:34                 ` Vojtech Pavlik
2002-06-12 19:22           ` Pavel Machek

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=200206091807.11524.bhards@bigpond.net.au \
    --to=bhards@bigpond.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rallymonkey@bellsouth.net \
    /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

all inboxes | Powered by JetHome®