Commit Graph

2 Commits (pyro)

Author SHA1 Message Date
Alejandro Hernandez 7fc38ead68 gma500-gfx-check: Fixes infinite calling to modprobe gma500_gfx
The previous script caused an infinite call to modprobe gma500_gfx on certain
situations, this fixes a typo and uses a new flag to avoid the infinite loop

(From meta-yocto rev: 9a341596fd0cdf892e125b2eead7b5e334a590b4)

Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-18 07:40:06 +00:00
Alejandro Hernandez c4acacefc1 gma500_gfx: Avoid inserting gma500_gfx module for certain devices
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 doesnt create an infinite loop executing itself everytime it wants to insert the module,
busybox's modprobe doesn't provide this functionality, so a small hack had to be used to avoid
the infite loop instead.

(From meta-yocto rev: 70c143767a8b63921e668a62ac463b3a6b8c6132)

Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-11-25 07:50:33 +00:00