linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Logitech iTouch keyboard broken scan codes
@ 2013-02-23 21:42 Götz Christ
  2013-08-27 10:49 ` Martin Pitt
  2013-08-27 16:34 ` Götz Christ
  0 siblings, 2 replies; 3+ messages in thread
From: Götz Christ @ 2013-02-23 21:42 UTC (permalink / raw)
  To: linux-hotplug

Hi, I have a Logitech "iTouch Internet Navigator" keyboard, with 5
broken scan codes.
Following the instructions from
/usr/share/doc/systemd/README.keymap.txt, I have:

$ /usr/lib/udev/findkeyboards
AT keyboard: input/event2

# /usr/lib/udev/keymap -i input/event2

(which corresponds to the keys labeled as)

0x91 shop    # Shopping
0x92 config  # iTouch
0x93 finance # Finance
0x94 prog1   # My Sites
0x95 prog2   # Community

I couldn't find something better in input.h for the last two, so I
chose prog1 and prog2.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Logitech iTouch keyboard broken scan codes
  2013-02-23 21:42 Logitech iTouch keyboard broken scan codes Götz Christ
@ 2013-08-27 10:49 ` Martin Pitt
  2013-08-27 16:34 ` Götz Christ
  1 sibling, 0 replies; 3+ messages in thread
From: Martin Pitt @ 2013-08-27 10:49 UTC (permalink / raw)
  To: linux-hotplug

Hello Götz,

sorry for the ridiculously late answer, catching up on old ML posts.

Götz Christ [2013-02-23 16:42 -0500]:
> Hi, I have a Logitech "iTouch Internet Navigator" keyboard, with 5
> broken scan codes.
> Following the instructions from
> /usr/share/doc/systemd/README.keymap.txt, I have:
> 
> $ /usr/lib/udev/findkeyboards
> AT keyboard: input/event2

I need some way of identifying that keyboard properly. Can you please
do

  udevadm info --export-db > /tmp/udev.txt

and send /tmp/udev.txt to me? (Please ensure the keyboard is
connected).

> # /usr/lib/udev/keymap -i input/event2
> 
> (which corresponds to the keys labeled as)
> 
> 0x91 shop    # Shopping
> 0x92 config  # iTouch
> 0x93 finance # Finance
> 0x94 prog1   # My Sites
> 0x95 prog2   # Community
> 
> I couldn't find something better in input.h for the last two, so I
> chose prog1 and prog2.

That sounds fine.

Thanks,

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Logitech iTouch keyboard broken scan codes
  2013-02-23 21:42 Logitech iTouch keyboard broken scan codes Götz Christ
  2013-08-27 10:49 ` Martin Pitt
@ 2013-08-27 16:34 ` Götz Christ
  1 sibling, 0 replies; 3+ messages in thread
From: Götz Christ @ 2013-08-27 16:34 UTC (permalink / raw)
  To: linux-hotplug

Hello Martin,
don't worry, you helped me with this some month ago in Launchpad
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1152377

regards,
Götz

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-08-27 16:34 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-02-23 21:42 Logitech iTouch keyboard broken scan codes Götz Christ
2013-08-27 10:49 ` Martin Pitt
2013-08-27 16:34 ` Götz Christ

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).