Linux bluetooth development
 help / color / mirror / Atom feed
From: Paul LeoNerd Evans <leonerd@leonerd.org.uk>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Extra keys on a Logitech Cordless Desktop Elite keyboard
Date: Sat, 9 Apr 2005 01:58:26 +0100	[thread overview]
Message-ID: <20050409015826.746a3add@nim.leo> (raw)

[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]

I have recently bought a Logitech Bluetooth keyboard/mouse combo, as
named above.. After much struggling, I've found that the -MH2 kernel
patch properly handles most of the behaviour. 

The mouse connects fine, all buttons work except the weird 8th button on
the top, but that doesn't work on a wired equivalent of the mouse that I
have elsewhere, so I suspect that's not BlueZ's fault. It even reconnects
after I remove it from the charger base too; most of the other
implementations would lose connectivity due to the mouse shutting down
for charging.

The keyboard doesn't seem too bad either. The basic 105key layout works
as expected, but the extra keys around the top do not. There's the
standard complement of play/stop, volume, application launch, etc.. keys
there. If I press any of those, the "showkey" program on the console will
not show anything. Similarly, Xfree shows a complete lack of activity on
the "xev" output.

Any thoughts..? Has anyone else had any luck with this or a similar
keyboard in this regard..? Is it likely to be easy to fix..?

-- 
Paul "LeoNerd" Evans

leonerd@leonerd.org.uk
ICQ# 4135350       |  Registered Linux# 179460
http://www.leonerd.org.uk/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2005-04-09  0:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050409015826.746a3add@nim.leo \
    --to=leonerd@leonerd.org.uk \
    --cc=bluez-users@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