From: Marcel Holtmann <marcel@holtmann.org>
To: Dick <dm@chello.nl>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] missing keys from logitech dinovo keyboard
Date: Tue, 06 Jul 2004 12:40:33 +0200 [thread overview]
Message-ID: <1089110433.4504.134.camel@pegasus> (raw)
In-Reply-To: <200407061222.47729.dm@chello.nl>
Hi Dick,
> I'm playing with showkey from kbd (http://freshmeat.net/projects/kbd/)
> All keys are shown except "New" (FnF1), "Reply" (FnF2), "Forward" (FnF3),
> "Send" (FnF4), "Redo" (FnF6), "Print" (FnF7), "Save" (FnF8), "My
> Doc" (FnF10), "My Pic" (FnF11) and "My Music" (FnF12) (you get those by
> enabling F-Lock)
> Undo (FnF5) and MyComp (FnF9) work though, giving keycode 144 and 145
> I'm using 2.6.7-mh1 and bluez-(utils/libs)2.7
> Is this a bug or am I missing something?
I don't know. I never checked the extra keys of my diNovo desktop, but
maybe the HID parser didn't take them into account and transforms them
into the correct key events. Feel free to look at the kernel code.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-07-06 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 10:22 [Bluez-devel] missing keys from logitech dinovo keyboard Dick
2004-07-06 10:40 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-29 11:36 Rutger Hendriks
2005-09-01 18:57 ` Rutger Hendriks
2005-09-01 20:31 ` Paul Webster
2005-09-09 12:23 ` Rutger Hendriks
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=1089110433.4504.134.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=dm@chello.nl \
/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