All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] current state of Microsoft bluetooth mouse (scroll wheel)
Date: Fri, 19 Aug 2005 16:49:00 +0200	[thread overview]
Message-ID: <1124462940.6398.6.camel@notepaq> (raw)
In-Reply-To: <1124406281.16439.8.camel@localhost.localdomain>

Hi Scott,

> I've got a "Microsoft Intellimouse Explorer for Bluetooth", and while it
> does mouse properly, neither the scroll wheel or the extra buttons work.
> I've just patched my kernel with patch-2.6.12-mh2.gz from
> http://www.bluez.org/patches.html, and I have bluetooth-utils 18.1, but
> still no luck. I get nothing out of /dev/input/mice for those buttons or
> the scroll wheel. 

is this the first or second genration of the mouse. I own the first
generation and it works fine in report protocol mode with my -mh patch.
The Bitkeeper repository is out of date, because we don't use Bitkeeper
anymore. The latest stuff is inside the Git repostiories at kernel.org.

Regards

Marcel




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-08-19 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-18 23:04 [Bluez-users] current state of Microsoft bluetooth mouse (scroll wheel) Scott Gilliland
2005-08-19 14:49 ` Marcel Holtmann [this message]
2005-08-19 15:58   ` Scott Gilliland
2005-08-19 15:59     ` Marcel Holtmann
2005-08-19 16:16       ` Scott Gilliland
2005-08-24 15:42   ` Scott Gilliland

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=1124462940.6398.6.camel@notepaq \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.