Linux bluetooth development
 help / color / mirror / Atom feed
From: Guylhem Aznar <bluez-devel@externe.net>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] fixing hidp keycodes
Date: Thu, 21 Apr 2005 18:03:05 -0400	[thread overview]
Message-ID: <20050421220305.GA28534@externe.net> (raw)

Hello

I'm trying to replace hidp keycodes for a dell axim bluetooth keyboard
with has conflicting keycodes with my zaurus internal keys.

I tried to change the keycodes in hidp/core.c - However looks like my
modifications are only half applied, certainly due to a stupid
mistake.

How could I easily syslog the keycode from hidp_keycodes[] array being
sent to the input layer ?

--=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


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2005-04-21 22:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 22:03 Guylhem Aznar [this message]
2005-04-22 10:16 ` [Bluez-devel] fixing hidp keycodes Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2005-04-22 10:56 Guylhem Aznar
2005-04-22 11:10 ` Marcel Holtmann
2005-05-05 20:32   ` Guylhem Aznar

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=20050421220305.GA28534@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox