summaryrefslogtreecommitdiffstats
path: root/common/recipes-bsp/gma500-gfx-check
Commit message (Collapse)AuthorAgeFilesLines
* meta-intel: Reorganize the layout to remove commonSaul Wold2017-11-203-35/+0
| | | | | | | Remove the concept of the common directory and move all the recipes-* dirs to the top level as a normal layer would be. layer.conf is updated appropriately Signed-off-by: Saul Wold <sgw@linux.intel.com>
* gma500-gfx-check: Fix dependency to meta-pokyAlejandro Hernandez2016-04-224-1/+35
| | | | | | | | | | | | The gma500-gfx-check we used had a dependency to meta-poky via a bbappend file this is unnacceptable, but this check is still needed on genericx86 and intel-core2-32, so this patch makes copy of the gma500-gfx-check to meta-intel to avoid the dependency issue [YOCTO #9181] Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* gma500_gfx: Avoid inserting gma500_gfx module for certain devicesAlejandro Hernandez2016-02-191-0/+1
The gma500_gfx driver will match certain devices on which it causes incorrect functionality, we want to avoid inserting this module, basicallly blacklist it for specific hardware, but still allow it to work on other hardware by default; usually when we have an already working system, using udev rules would do the job, but since we are building it, it is impossible to blacklist a driver when a certain udev rule matches, since rootfs isn't writeable at this point during boot time, the solution is to use modprobe install, which runs a certain command instead of inserting a matching module this command needs to insert the module manually afterwards and have a flag --ignore-install so it doesn't create an infinite loop executing itself everytime it wants to insert the module, busybox's modprobe doesnt provide this functionality, so a small hack had to be used to avoid the infite loop instead. Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>