From: Guylhem Aznar <bluez-devel@externe.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] fixing hidp keycodes
Date: Thu, 5 May 2005 16:32:57 -0400 [thread overview]
Message-ID: <20050505203257.GA12178@externe.net> (raw)
In-Reply-To: <1114168206.32265.62.camel@pegasus>
On Friday, 22 April 2005 at 13:10:06 (+0200), Marcel Holtmann wrote:
> > This suggest that my approach should work. I don't understand why it'=
s
> > not working with tab/capslock/esc.
>=20
> To make this working in report mode, you must replace the HID descripto=
r
> or tell hidd to use the boot mode only. Speaking of which, I just saw
> that I never added support for pushing a device into boot mode. However
> the --nosdp option should do the trick.
It doesn't. Here's the table I'm using in
kernel/net/bluetooth/hidp/core.c :
static unsigned char hidp_keycode[256] =3D {
0, 0, 0, 0, 125, 48, 46, 32, 18, 33, 34, 35, 23, 36, 37, 38,
50, 49, 24, 25, 16, 19, 31, 20, 22, 47, 17, 45, 21, 44, 2, 3,
4, 5, 6, 7, 8, 9, 10, 11, 28, 58, 14, 1, 57, 12, 13, 26,
27, 43, 43, 39, 40, 41, 51, 52, 53, 15, 59, 60, 61, 62, 63, 64,
0, 0, 67, 68, 87, 67, 99, 70,119,110,102,104,111,107,109,106,
105,108,103, 69, 98, 55, 74, 78, 96, 79, 80, 81, 75, 76, 77, 71,
72, 73, 82, 83, 86,127,116,117,183,184,185,186,187,188,189,190,
191,192,193,194,134,138,130,132,128,129,131,137,133,135,136,113,
115,114, 0, 0, 0,121, 0, 89, 93,124, 92, 94, 95, 0, 0, 0,
122,123, 90, 91, 85, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
29, 42, 56, 30, 97, 54,100,126,164,166,165,163,161,115,114,113,
150,158,159,128,136,177,178,176,142,152,173,140
};
As you can see, 30/125 1/15/58 have been swapped, and 65/66 have been rem=
oved. (that's necessary).
Yet it doesn't work. I still even get 65 and 66. I'm using bluez 2.16 (ex=
cept sdptool - cf other message) with
the kernel patch. The kernel is on
http://externe.net/zaurus/kernel/sources/linux-2.4.18-rmk7-pxa3-20050501.=
tar.gz
I first though my ifdef were at fault. I removed everything- I only have =
this hidp_keycode now. Still doesn't work anyway.
Would you have a patch for hidd or a suggestion?
--=20
Bien =E0 vous - Best regards,
Guylhem P. Aznar
--=20
*@externe.net http://externe.n=
et
P=E9rim=E9/Deprecated: @oeil.qc.ca, @metalab.unc.edu, @ibiblio.org, @7=
un.org
GPG: 92EB37C1 DD11C9C9 20519D01 E8FA1B11 42975AF7 http://externe.net/pubk=
ey
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-05-05 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 10:56 [Bluez-devel] fixing hidp keycodes Guylhem Aznar
2005-04-22 11:10 ` Marcel Holtmann
2005-05-05 20:32 ` Guylhem Aznar [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-21 22:03 Guylhem Aznar
2005-04-22 10:16 ` 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=20050505203257.GA12178@externe.net \
--to=bluez-devel@externe.net \
--cc=bluez-devel@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 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.