From: Michal Semler <cijoml@volny.cz>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] hidp and hidd related bugs
Date: Wed, 12 May 2004 00:30:54 +0200 [thread overview]
Message-ID: <200405120030.54220.cijoml@volny.cz> (raw)
Hi Marcel,
I did little research and here is output:
keys which are not reported in xev:
Eigene Dateien
Eigene Bilder
Eigene Musik
Messenger
Abmelden
Reported badly
Rechner is reported like Pause
Standby like Print
Do you want send keycodes which reports bthid in 2.4.26 to have the same
hotkeys events?
hidd --killall wants atribute BDADDR
Michal
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2004-05-11 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 22:30 Michal Semler [this message]
2004-05-12 13:21 ` [Bluez-users] hidp and hidd related bugs Marcel Holtmann
2004-05-12 19:09 ` Michal Semler
2004-05-12 19:20 ` 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=200405120030.54220.cijoml@volny.cz \
--to=cijoml@volny.cz \
--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