From: Marcel Holtmann <marcel@holtmann.org>
To: cijoml@volny.cz
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hidp and hidd related bugs
Date: Wed, 12 May 2004 15:21:30 +0200 [thread overview]
Message-ID: <1084368090.25099.22.camel@pegasus> (raw)
In-Reply-To: <200405120030.54220.cijoml@volny.cz>
Hi Michal,
> 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?
you own a german keyboard ;)
However I can't help you in that case, because I have little interest to
fix this. The HID parser that is used by the HIDP kernel module is the
same parser as in the USB HID driver. In some near future they will be
joined to use the same generic parser. The parser in bthid was written
for the Microsoft keyboard and maybe did some assumptions that are wrong
for other keyboards. Try to get the buttons work with current HIDP and
some external programs like hotkeys.
> hidd --killall wants atribute BDADDR
Silly typo. I only tested "-K" and that was working. It is fixed in CVS
now.
Regards
Marcel
-------------------------------------------------------
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 prev parent reply other threads:[~2004-05-12 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 22:30 [Bluez-users] hidp and hidd related bugs Michal Semler
2004-05-12 13:21 ` Marcel Holtmann [this message]
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=1084368090.25099.22.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=cijoml@volny.cz \
/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