All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Oli Ellis <oliver.ellis@ntlworld.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] dinovo multimedia keys
Date: Tue, 23 Mar 2004 15:20:05 +0100	[thread overview]
Message-ID: <1080051605.2515.20.camel@pegasus> (raw)
In-Reply-To: <406005DB.2090109@ntlworld.com>

Hi Oli,

> I have had a poke around utils2/hid/, specifically parser.c and 
> uinput.h. Correct me if I am wrong, but I am figuring that bthid 
> collects events from hcid and converts them into events that the kernel 
> input system can understand. (uinput.h repeats the kernel's input.h key 
> definitions.)

the hcid has nothing to do with it. It reads the HID reports from the
L2CAP control and interrupts sockets.

> My question is, are the consumer keymaps in parser.c some sort of 
> immutable bluetooth standard or just what your personal keyboard is? For 
> example, you have the following for volumes:
>         case 0xe2:    butt = KEY_MUTE;    break;
>         case 0xe9:    butt = KEY_VOLUMEUP;    break;
>         case 0xea:    butt = KEY_VOLUMEDOWN;    break;
> Whereas, my dinovo works with
>         case 0xe3:    butt = KEY_MUTE;    break;
>         case 0xea:    butt = KEY_VOLUMEUP;    break;
>         case 0xeb:    butt = KEY_VOLUMEDOWN;    break;
> What sort of keyboard do you have?
> 
> Presumably for now it would not matter if the events reported to the 
> kernel input system did not match what was written on the button labels, 
> as most people use, for example, gnome acme, which maps arbitrary keys 
> to program executions. However, the names in kernel input.h must be 
> there for a reason. I think the long term plan is for things like X to 
> read /dev/eventX, where it might become important to get it right. Does 
> this mean that bthid should become configurable?

Maybe there is a bit error somewhere in parser.c. Actually the consumer
usages are defined in the USB HID standard and should be general for all
Bluetooth keyboards.

> I am happy to help with this as best I can (patches, testing etc), but 
> my c/c++ is a little flaky...

Go ahead and try. Every patch is welcome.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-03-23 14:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23  9:39 [Bluez-users] dinovo multimedia keys Oli Ellis
2004-03-23 14:20 ` Marcel Holtmann [this message]
2004-03-23 16:01   ` Oli Ellis
2004-03-23 20:55     ` Marcel Holtmann

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=1080051605.2515.20.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=oliver.ellis@ntlworld.com \
    /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.