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 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.j...@intel.com> > > > > Signed-off-by: Jussi Kukkonen <jussi.kukko...@intel.com> > > > > > > This doesn't sound right. In qemu, we add a usb touchpad which > > > allows > > > absolute coordinate entry, which means qemu doesn't have to grab > > > the > > > mouse. > > > > > > Are there two devices? A mouse shouldn't be seen as an absolute > > > coordinate device. > > > > Yes, both qemu monitor and xinput_calibrator in target shows two > > devices: > > > > (qemu) info mice > > Mouse #2: QEMU PS/2 Mouse > > * Mouse #3: QEMU HID Tablet (absolute) > > > > # xinput_calibrator --list > > Device "QEMU QEMU USB Tablet" id=8 > > Device "ImExPS/2 Generic Explorer Mouse" id=9 > > So with these patches, are we still calibrating the tablet input?
We won't be calibrating tablet input in qemu targets.This patch is supposed to be a work-around to avoid mouse input calibration only in qemu targets. > pointercal ships default calibrations for that under the current setup > but those likely aren't compatible with xinput and we'd need the same > thing but for xinput here? Yes, the default values shipped by pointercal aren't compatible with xinput. > Cheers, > Richard Best Regards, Maxin -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core