From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:40569)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1Yvmsv-0008C7-2n
	for qemu-devel@nongnu.org; Fri, 22 May 2015 09:21:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1Yvms9-00083G-Vy
	for qemu-devel@nongnu.org; Fri, 22 May 2015 09:21:09 -0400
Received: from mx1.redhat.com ([209.132.183.28]:34820)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1Yvms9-00082q-Nd
	for qemu-devel@nongnu.org; Fri, 22 May 2015 09:20:21 -0400
Message-ID: <1432300809.12533.55.camel@nilsson.home.kraxel.org>
From: Gerd Hoffmann <kraxel@redhat.com>
Date: Fri, 22 May 2015 15:20:09 +0200
In-Reply-To: <555F2AC7.80807@msgid.tls.msk.ru>
References: <5541B728.8020404@msgid.tls.msk.ru>
	<555C73AB.2090408@msgid.tls.msk.ru>
	<1432288894.12533.43.camel@nilsson.home.kraxel.org>
	<555F2AC7.80807@msgid.tls.msk.ru>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] ABNT2 keys again
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "R. Lemos" <rslemos@gmail.com>, 772422@bugs.debian.org, qemu-devel <qemu-devel@nongnu.org>, Joao Luis Meloni Assirati <jlma@nonada.if.usp.br>

  Hi,

> > Anyone having such a keyboard and willing to run some tests?
> 
> Adding Cc's.  This has been reported to debian too,
> http://bugs.debian.org/772422 (also in Cc).

Ok, so just replying should stick this into the debian bug tracker,
right?

Ok, instructions are here:

(a) Go grab https://www.kraxel.org/cgit/input/ please (could be there
    even is a debian package for this stuff).

(b) Use 'lsinput' to figure which input device is your keyboard (on
    the host machine).

(c) Then use 'input-events <device-number>' to get a input event log
    printed to the terminal.  Type each missing key once.

(d) Send me the log (with annotation which key is which).

thanks,
  Gerd