On 10/10/14, 6:37 AM, "Zanussi, Tom" <[email protected]> wrote:
>On Thu, 2014-10-09 at 15:11 -0700, [email protected] wrote: >> From: Nitin A Kamble <[email protected]> >> >> The gmx500 graphics driver does not work on this BSP, but it takes >> the ownership of the graphics hardware at boot time, blocking other >> drivers from using the graphics hardware. >> >> Fix the issue by blacklisting the gma500_gfx kernel module in the kmod >> configuration, so that it doesn't get loaded at boot time. >> > >Is this really the right way to do this? It will only work if >CONFIG_XXX=m. If m->y at some point, the whole .bbappend becomes >useless at best. That is why the gma500 is converted from y to m. And with the common kernel, It should be m anyway. If you have better way to solve you can share. Nitin > >Tom > >> Fixes Bug: >> [YOCTO #6807] >> >> Signed-off-by: Nitin A Kamble <[email protected]> >> --- >> meta-crownbay/recipes-kernel/kmod/kmod_git.bbappend | 3 +++ >> 1 file changed, 3 insertions(+) >> create mode 100644 meta-crownbay/recipes-kernel/kmod/kmod_git.bbappend >> >> diff --git a/meta-crownbay/recipes-kernel/kmod/kmod_git.bbappend >>b/meta-crownbay/recipes-kernel/kmod/kmod_git.bbappend >> new file mode 100644 >> index 0000000..56d8fcb >> --- /dev/null >> +++ b/meta-crownbay/recipes-kernel/kmod/kmod_git.bbappend >> @@ -0,0 +1,3 @@ >> +do_install_append () { >> + echo "blacklist gma500_gfx" > >>${D}${sysconfdir}/modprobe.d/prohibit_gma500_gfx.conf >> +} > > -- _______________________________________________ meta-intel mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-intel
