From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754222AbdDKIui (ORCPT ); Tue, 11 Apr 2017 04:50:38 -0400 Received: from mx2.suse.de ([195.135.220.15]:52784 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751921AbdDKIue (ORCPT ); Tue, 11 Apr 2017 04:50:34 -0400 From: Juergen Gross To: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org, linux-input@vger.kernel.org Cc: boris.ostrovsky@oracle.com, dmitry.torokhov@gmail.com, andr2000@gmail.com, Juergen Gross Subject: [PATCH v2 0/2] xen,input: xen-kbdfront pointing device resolution support Date: Tue, 11 Apr 2017 10:50:26 +0200 Message-Id: <20170411085028.6750-1-jgross@suse.com> X-Mailer: git-send-email 2.12.0 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. V2: patch 1: make resolution changes via xenstore visible in sysfs 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 | 50 ++++++++++++++++++++++++++------------- 1 file changed, 34 insertions(+), 16 deletions(-) -- 2.12.0