From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 4/4] pointercal-xinput: add a dummy calibration file for qemu
Date: Wed, 15 Jun 2016 16:13:00 +0300 [thread overview]
Message-ID: <1465996380-32444-4-git-send-email-maxin.john@intel.com> (raw)
In-Reply-To: <1465996380-32444-1-git-send-email-maxin.john@intel.com>
In qemu, the emulated PS/2 mouse reports itself as an "absolute coordinate"
device and that makes xinput_calibrator think it could be calibrated.
Add a dummy calibration file as a work around to prevent xinput_calibrator from
popping up on every boot in qemu.
[YOCTO #8380]
Signed-off-by: Maxin B. John <maxin.john@intel.com>
Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
---
.../xinput-calibrator/pointercal-xinput/qemuall/pointercal.xinput | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 meta/recipes-graphics/xinput-calibrator/pointercal-xinput/qemuall/pointercal.xinput
diff --git a/meta/recipes-graphics/xinput-calibrator/pointercal-xinput/qemuall/pointercal.xinput b/meta/recipes-graphics/xinput-calibrator/pointercal-xinput/qemuall/pointercal.xinput
new file mode 100644
index 0000000..a816d6d
--- /dev/null
+++ b/meta/recipes-graphics/xinput-calibrator/pointercal-xinput/qemuall/pointercal.xinput
@@ -0,0 +1,2 @@
+# Dummy pointercal.xinput file to prevent xinput_calibrator
+# from running on qemu startup
--
2.4.0
next prev parent reply other threads:[~2016-06-15 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 13:12 [PATCH 1/4] xtscal: remove recipe Maxin B. John
2016-06-15 13:12 ` [PATCH 2/4] x11-common: replace xtscal with xinput-calibrator Maxin B. John
2016-06-15 13:12 ` [PATCH 3/4] distro_alias.inc: remove xtscal Maxin B. John
2016-06-15 13:13 ` Maxin B. John [this message]
2016-06-15 16:58 ` [PATCH 4/4] pointercal-xinput: add a dummy calibration file for qemu Richard Purdie
2016-06-16 8:05 ` Maxin B. John
2016-06-16 8:43 ` Richard Purdie
2016-06-16 11:11 ` Maxin B. John
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1465996380-32444-4-git-send-email-maxin.john@intel.com \
--to=maxin.john@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox