All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Question regarding MS bluetooth keyboard/mouse
Date: Fri, 07 Oct 2005 09:13:12 +0200	[thread overview]
Message-ID: <1128669192.8750.3.camel@localhost.localdomain> (raw)
In-Reply-To: <4345A239.5060901@fusion-labs.com>

Hi Shawn,

> I am unsure as to where to post this, if this is the wrong place, 
> please feel free to let me know.  Please don't be irritated if this is 
> in the wrong list, I am out of ideas, and this was the last place I had 
> left to ask this question.
> 
> I recently purchased the MS Keyboard Elite/Intellimouse combo for 
> bluetooth, and I do have them running with bluez (Version 2.19) under 
> kernel version 2.6.13.2.   While I could care less about getting the 
> multimedia keys working on the keyboard, I do have a problem with the 
> mouse wheel not working in anything(Including xev). 
> 
> I usually just run hidd --search and it brings up both the devices, but 
> when I do a(n) hidd --show, it shows both of the devices connected using 
> boot-protocol.  My thought (At least from reading about the 
> boot-protocol in the kernel documentation) was that this setup was the 
> very basic setup for a wireless mouse/keyboard combination, and that 
> nothing else besides the 104 key/3 mouse buttons were supported).
> 
> I have scoured the web and found lots of somewhat out-dated material 
> involving bt-hidd (Which from what I gather has since been incorporated 
> into Bluez), changing my xorg.conf script to use ExplorerPS/2, etc, but 
> nothing has helped me find a solution to this issue.  Running cat on 
> /dev/mouseX from the command line will show activity in the mouse when I 
> move, and press one of the 3 common mouse buttons, but nothing shows up 
> for the wheel (the 2 side buttons and the tilt buttons are in the same 
> category, but of little importance to me).
> 
> I should also let you know that I have no problems being a test subject, 
> if there are any patches (I did try applying the 2.6.13-MH1) I could 
> test out for anyone.  I am also fairly competent with c (I would love to 
> wrestle with this problem myself, but have a quite a bit on my plate 
> already), and am willing to help out wherever possible.

using patch-2.6.13-mh1 gives report mode protocol support, but this
doesn't mean all Microsoft specific stuff is supported. I only have the
old Microsoft Bluetooth desktop at home and the mouse works perfect with
this patch. Maybe they changed some reports for their new model.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-10-07  7:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-06 22:16 [Bluez-devel] Question regarding MS bluetooth keyboard/mouse Shawn Fisher
2005-10-07  7:13 ` Marcel Holtmann [this message]
2005-10-07 18:19   ` Shawn Fisher

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=1128669192.8750.3.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@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.