[yocto] [meta-raspberrypi][PATCH] rpi-base.inc: Add xf86-input-evdev to XSERVER
Gary Thomas
gary at mlbassoc.com
Wed Feb 15 23:48:24 PST 2017
On 2017-02-16 08:37, Jussi Kukkonen wrote:
> On 16 February 2017 at 04:14, Gary Thomas <gary at mlbassoc.com <mailto:gary at mlbassoc.com>> wrote:
>
> On 2017-02-16 02:45, Andrei Gherzan wrote:
>
> On Mon, Feb 13, 2017 at 12:25:48AM +0900, Yusuke Mitsuki wrote:
>
> In order to fix problem that mouse does not work.
>
> This is removed c40558173ffd96c499d101155f6c4c2be85d9f0f.
> However mouse does not worked from this.
> ---
> conf/machine/include/rpi-base.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/conf/machine/include/rpi-base.inc b/conf/machine/include/rpi-base.inc
> index e069e70..051c717 100644
> --- a/conf/machine/include/rpi-base.inc
> +++ b/conf/machine/include/rpi-base.inc
> @@ -11,6 +11,7 @@ XSERVER = " \
> xserver-xorg \
> ${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "xserver-xorg-extension-glx", "", d)} \
> ${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "xf86-video-modesetting", "xf86-video-fbdev", d)} \
> + xf86-input-evdev \
> "
>
> KERNEL_DEVICETREE ?= " \
> --
> 2.7.4
>
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org <mailto:yocto at yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>
>
>
> CC-ing schnitzeltony at googlemail.com <mailto:schnitzeltony at googlemail.com> as he might have an opinion about
> this. I personally don't really hold on any of the options.
>
>
> I think it's the right thing to do, in fact, I was preparing a
> similar patch myself. The change that removed this argued that
> it was not the responsibility of the BSP layer, but if you look
> around at other BSP layers, almost all of them do include this
> driver as part of their X server setup. It also lets X work
> again on the RaspberryPi "out of the box" with the simplest
> configuration - HDMI display + USB keyboard & mouse.
>
> +1
>
>
> Out of interest: Why is xf86-input-libinput not appropriate for these setups? I honestly did not know of a use case
> where -evdev would work but -libinput would not...
I'm not sure (and I don't have a setup right now to test). I've always
used -evdev as that was the recommended driver for many years now.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
More information about the yocto
mailing list