From mboxrd@z Thu Jan  1 00:00:00 1970
From: Martin Pitt <martin.pitt@ubuntu.com>
Date: Tue, 27 Aug 2013 10:49:47 +0000
Subject: Re: Logitech iTouch keyboard broken scan codes
Message-Id: <20130827104947.GA3021@piware.de>
List-Id: <linux-hotplug.vger.kernel.org>
References: <CAGc31=qQe1d9f76roQE-wXhzHVA2CRtLTRqXqYuy3083ke-=zQ@mail.gmail.com>
In-Reply-To: <CAGc31=qQe1d9f76roQE-wXhzHVA2CRtLTRqXqYuy3083ke-=zQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
To: linux-hotplug@vger.kernel.org

Hello G=F6tz,

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

G=F6tz 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:
>=20
> $ /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
>=20
> (which corresponds to the keys labeled as)
>=20
> 0x91 shop    # Shopping
> 0x92 config  # iTouch
> 0x93 finance # Finance
> 0x94 prog1   # My Sites
> 0x95 prog2   # Community
>=20
> I couldn't find something better in input.h for the last two, so I
> chose prog1 and prog2.

That sounds fine.

Thanks,

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