public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ortwin Glück" <odi@odi.ch>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Mighty Mouse again
Date: Thu, 11 Jan 2007 02:28:54 +0100	[thread overview]
Message-ID: <45A592D6.4050604@odi.ch> (raw)

Okay, ignore my former emails. I figured out that the mouse data is 
parsed by net/bluetooth/hidp/core.c. A patch seems straight forward. I 
have verified that the code is executed. But I still don't see the 
events in xev. Any hints to a poor kernel newbie?

Cheers

Ortwin

--- core.c.orig 2007-01-11 01:31:29.000000000 +0100
+++ core.c      2007-01-11 02:16:05.000000000 +0100
@@ -212,6 +212,8 @@

                 if (size > 3)
                         input_report_rel(dev, REL_WHEEL, sdata[3]);
+               if (size > 4)
+                       input_report_rel(dev, REL_HWHEEL, sdata[4]);
                 break;
         }

@@ -563,7 +565,7 @@
                 input->keybit[LONG(BTN_MOUSE)] = BIT(BTN_LEFT) | 
BIT(BTN_RIGHT) | BIT(BTN_MIDDLE);
                 input->relbit[0] = BIT(REL_X) | BIT(REL_Y);
                 input->keybit[LONG(BTN_MOUSE)] |= BIT(BTN_SIDE) | 
BIT(BTN_EXTRA);
-               input->relbit[0] |= BIT(REL_WHEEL);
+               input->relbit[0] |= BIT(REL_WHEEL) | BIT(REL_HWHEEL);
         }

         input->event = hidp_input_event;


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

                 reply	other threads:[~2007-01-11  1:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=45A592D6.4050604@odi.ch \
    --to=odi@odi.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox