Hello, I tried to execute zcat /proc/config.gz | grep EVDEV, and it produced the following output:
# CONFIG_INPUT_EVDEV is not set CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y Does the above shed some light what could be the problem with the image? //Andreas -----Original Message----- From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Sent: 10. huhtikuuta 2013 17:51 To: Andreas Enbacka Cc: 'Burton, Ross'; yocto@yoctoproject.org Subject: Re: [yocto] Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow) On 13-04-10 02:34 AM, Andreas Enbacka wrote: > Ross, > > Tried to dig around a little more in the core-image-sato image; dmesg output does not list anything at all related to evdev. The evdev_drv.so module is present in the image, but e.g., lsmod | grep evdev does not produce any output (modprobe evdev reports fatal error: cannot load module). Is the evdev support missing from the kernel of some reason, and can it be fixed easily somehow? EVDEV is typically built into our images, not as a module. If you zcat /proc/config.gz, and grep for EVDEV, what do you see ? Bruce > > //Andreas > > -----Original Message----- > From: Burton, Ross [mailto:ross.bur...@intel.com] > Sent: 9. huhtikuuta 2013 13:07 > To: Andreas Enbacka > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Problem with mouse and keyboard detection in > yocto (core-image-sato on emenlow) > > Hi Andreas, > > On 8 April 2013 18:44, Andreas Enbacka <aenba...@gmail.com> wrote: >> I tried to rebuild the xf86-input-evdev; however the core-image-sato still insists on using the default mouse / keyboard drivers instead of evdev. Also no /dev/input/event* entries exist (only /dev/input/mice and /dev/input/mouse0). > > So in that case evdev won't help anyway. I wonder why that is. I guess you'll need to try evtest and look at dmesg. > >> Concerning removing xf86-input-mouse / xf86-input-keyboard from the image, what is the easiest way to achieve this using yocto? I have created a custom bitbake recipe already, inheriting from core-image-sato, which adds a few packages. Can removal of packages be easily specified in the custom recipe as well? > > They're pulled in through the machine configuration, eventually reaching XSERVER_IA32_BASE. The packages are tiny and the choice of what ones to use can be made by xorg.conf anyway. > > Ross > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
