public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hidd weirdness under 2.4.20
Date: Wed, 01 Dec 2004 20:39:33 +0100	[thread overview]
Message-ID: <1101929973.15615.32.camel@pegasus> (raw)
In-Reply-To: <D041B252-43B9-11D9-9BD7-00039390D626@pepper.com>

Hi Michael,

> I am currently running with great success the hidd patch for 2.4.20 
> from Marcel.  However when using a bluetooth mouse and keyboard, I get 
> the following message from the kernel.
> 
> keyboard.c: can't emulate rawmode for keycode 272
> keyboard.c: can't emulate rawmode for keycode 272
> keyboard.c: can't emulate rawmode for keycode 272
> keyboard.c: can't emulate rawmode for keycode 272
> 
> This seems to happen quite often, and sometimes I get extra characters 
> typed into my system randomly.
> 
> Has anyone else seen this?  What could be causing this?

this is keycode out of the PS/2 range. What device are you using?

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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-12-01 19:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01 16:55 [Bluez-devel] hidd weirdness under 2.4.20 Michael Frey
2004-12-01 19:39 ` Marcel Holtmann [this message]
2004-12-01 19:45   ` Michael Frey
2004-12-01 19:50     ` Marcel Holtmann
2004-12-01 19:55       ` Michael Frey
2004-12-01 20:16         ` Marcel Holtmann
2004-12-01 20:22           ` Michael Frey
2004-12-01 20:35             ` 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=1101929973.15615.32.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox