All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Langdale <philipl@mail.utexas.edu>
To: Philip Langdale <philipl@mail.utexas.edu>
Cc: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: Experiences with mx-5000 bluetooth mouse+keyboard combo
Date: Sat, 06 May 2006 11:48:36 -0700	[thread overview]
Message-ID: <445CEF84.3050305@mail.utexas.edu> (raw)
In-Reply-To: <444A7810.4090607@mail.utexas.edu>

Philip Langdale wrote:
> Philip Langdale wrote:
>> Hi all,
>>
>> I decided to get myself an mx-5000 set this week and I've been fiddling
>> with it and while I've got it working well, I'm not quite there yet. I
>> do want to report my initial findings however.
>>
>> 0) Everything works fine in HID mode. All the buttons on the mouse
>>    and keyboard work correctly at the input level as reported by evtest.
>>
>>
>> 5) The keyboard is in a similar situation but I have not mapped out the
>>    broken usages yet, and even some of the multimedia keys that do work
>>    report different codes from HID mode.
>>
> 
> This is only partially true. There are some keys that don't generate
> input events in either mode, and some keys that generate different codes
> in HCI mode. So, there's two problems there.

I did some more investigation today and came up with useful conclusions.

1) The initial attempt at mapping the usage code is correct, but a later
step in the configuration mangles the codes so they end up incorrect.
(incorrect is a relative term as long as your desktop environment/apps
supports configurable keybindings - so it's not a deal breaker).

This step is:

while (usage->code <= max && test_and_set_bit(usage->code, bit)) {
    usage->code = find_next_zero_bit(bit, max + 1, usage->code);
}

in hidinput_configure_usage.

eg: It mangles KEY_UNDO (131) into KEY_SENDFILE (145) which doesn't seem
very useful.

2) Some of the keys that generated no input events are simply keys that
hidinput_configure_usage doesn't know about. I added entries for them
and now they work (some are mangled, some are not).

3) Much more interestingly, there are multiple keys that generate *no*
meaningful events, even at the hcidump level. I assume that these can
only be made to work by downloading programs to the keyboard (the
mx-5000 and di novo are programmable but the interface is apparently
unknown).

--phil


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-05-06 18:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-22 18:31 [Bluez-devel] Experiences with mx-5000 bluetooth mouse+keyboard combo Philip Langdale
2006-04-22 18:38 ` [Bluez-devel] " Philip Langdale
2006-05-06 18:48   ` Philip Langdale [this message]
2006-05-06 13:26 ` [Bluez-devel] " Philip Lawatsch

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=445CEF84.3050305@mail.utexas.edu \
    --to=philipl@mail.utexas.edu \
    --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.