public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Lenherr <lenherr@netpeople.ch>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Once again some media-keys from logitech...
Date: Thu, 01 Apr 2004 23:36:34 +0200	[thread overview]
Message-ID: <406C8B62.4000802@netpeople.ch> (raw)

[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]

Hi,
because quite all of my media-keys from my logitech elite keyboard did 
not work,
I started googling and found ... nothing (almost). So I started 
searching the sources
and came to parser.c where I found the producer of these nice "unknown 
consumer"
messages. As somebody else already told in this forum, the keyboard 
seems to
have all the codes wrong by 1 (or there's something wrong with the 
source, but
that doesn't matter), so I just decided to place a nice -1 at the right 
place et voila,
all these messages where gone in the log (except for FLock and the 
change user-button,
but that's something else). After that I lived happily ever after.

Not really... Well, the messages in the log were gone, but neither 
"scankey -s" nor "xev"
were somehow interested in my banging actions on my keyboard.

So, once for short, here are my three questions:
1) Why are these keys lost somewhere in the kernel? (At least I think 
it's there)
2) If I'd like a working FLock-LED, how should I do this?
3) And why the hell is my key for the "anti-{" not working (although 
this one IS
generating an event, but "xev" tells me, this button is for printing...)

Thanks a lot and good night
    Thomas Lenherr

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

                 reply	other threads:[~2004-04-01 21:36 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=406C8B62.4000802@netpeople.ch \
    --to=lenherr@netpeople.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox