All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] fixing hidp keycodes
Date: Fri, 22 Apr 2005 12:16:27 +0200	[thread overview]
Message-ID: <1114164987.32265.53.camel@pegasus> (raw)
In-Reply-To: <20050421220305.GA28534@externe.net>

Hi Guylhem,

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

do you applied the -mh patch? If yes, then you device may run in report
mode and thus hidp_keycodes[] is not used, because it is boot mode only.

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

Use things like printk() or BT_ERR().

Regards

Marcel




-------------------------------------------------------
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-22 10:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 22:03 [Bluez-devel] fixing hidp keycodes Guylhem Aznar
2005-04-22 10:16 ` Marcel Holtmann [this message]
  -- 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=1114164987.32265.53.camel@pegasus \
    --to=marcel@holtmann.org \
    --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.