From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933765AbdCURT6 (ORCPT ); Tue, 21 Mar 2017 13:19:58 -0400 Received: from mx2.suse.de ([195.135.220.15]:47881 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933618AbdCURTL (ORCPT ); Tue, 21 Mar 2017 13:19:11 -0400 From: Juergen Gross To: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org, linux-input@vger.kernel.org Cc: dmitry.torokhov@gmail.com, Juergen Gross Subject: [PATCH 0/2] xen,input: xen-kbdfront pointing device resolution support Date: Tue, 21 Mar 2017 18:19:03 +0100 Message-Id: <20170321171905.31584-1-jgross@suse.com> X-Mailer: git-send-email 2.10.2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org As my patch tying the resolution of the xen pointing device to that of the framebuffer wasn't accepted add support for different resolutions via a module parameter. Another possibility would be to set parameters via Xenstore, but this is broken (patch 2 fixes that) and not yet supported by Xen tools. Juergen Gross (2): xen,input: add xen-kbdfront module parameter for setting resolution xen,input: repair xen-kbdfront resolution setting via xenstore drivers/input/misc/xen-kbdfront.c | 42 ++++++++++++++++++++++++++------------- 1 file changed, 28 insertions(+), 14 deletions(-) -- 2.10.2