Hi,
On Thu, Jun 16, 2016 at 09:43:40AM +0100, Richard Purdie wrote:
> On Thu, 2016-06-16 at 11:05 +0300, Maxin B. John wrote:
> > Hi RP,
> >
> > On Wed, Jun 15, 2016 at 05:58:18PM +0100, Richard Purdie wrote:
> > > On Wed, 2016-06-15 at 16:13 +0300, Maxin B. John wrote:
> > > > In qemu, the
On Thu, 2016-06-16 at 11:05 +0300, Maxin B. John wrote:
> Hi RP,
>
> On Wed, Jun 15, 2016 at 05:58:18PM +0100, Richard Purdie wrote:
> > On Wed, 2016-06-15 at 16:13 +0300, Maxin B. John wrote:
> > > In qemu, the emulated PS/2 mouse reports itself as an "absolute
> > > coordinate"
> > > device and
Hi RP,
On Wed, Jun 15, 2016 at 05:58:18PM +0100, Richard Purdie wrote:
> On Wed, 2016-06-15 at 16:13 +0300, Maxin B. John wrote:
> > In qemu, the emulated PS/2 mouse reports itself as an "absolute
> > coordinate"
> > device and that makes xinput_calibrator think it could be calibrated.
> >
> >
On Wed, 2016-06-15 at 16:13 +0300, Maxin B. John wrote:
> 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
>
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
