Re: [meta-intel] [PATCH] gma500_gfx: Avoid inserting gma500_gfx module for certain devices

[Alejandro Hernandez]

On 02/24/2016 04:49 PM, Burton, Ross wrote:


On 24 February 2016 at 14:18, Trevor Woerner > wrote:


This patch assumes git://git.yoctoproject.org/meta-yocto
 is included in bbappends,
is this a requirement?

I'm asking because up until this point I haven't been using
meta-yocto since my DISTRO isn't poky but my builds seem to be
working okay. Also, there's no mention of dependencies in the README.


Hm, yeah, that's not good.  meta-intel should be standalone from 
meta-yocto-bsp.


Ross


Yes, I will send a patch in a few minutes, moving it to meta

Alejandro

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH] gma500_gfx: Avoid inserting gma500_gfx module for certain devices

[Trevor Woerner]

On 02/24/16 09:18, Trevor Woerner wrote:

This patch assumes git://git.yoctoproject.org/meta-yocto is included in


bblayers


, is this a requirement?


--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH] gma500_gfx: Avoid inserting gma500_gfx module for certain devices

[Trevor Woerner]

This patch assumes git://git.yoctoproject.org/meta-yocto is included in 
bbappends, is this a requirement?


I'm asking because up until this point I haven't been using meta-yocto 
since my DISTRO isn't poky but my builds seem to be working okay. Also, 
there's no mention of dependencies in the README.

--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [PATCH] gma500_gfx: Avoid inserting gma500_gfx module for certain devices

[Alejandro Hernandez]

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 
---
 common/recipes-bsp/gma500-gfx-check/gma500-gfx-check_1.0.bbappend | 1 +
 conf/machine/intel-core2-32.conf  | 2 ++
 2 files changed, 3 insertions(+)
 create mode 100644 
common/recipes-bsp/gma500-gfx-check/gma500-gfx-check_1.0.bbappend

diff --git a/common/recipes-bsp/gma500-gfx-check/gma500-gfx-check_1.0.bbappend 
b/common/recipes-bsp/gma500-gfx-check/gma500-gfx-check_1.0.bbappend
new file mode 100644
index 000..eb8a724
--- /dev/null
+++ b/common/recipes-bsp/gma500-gfx-check/gma500-gfx-check_1.0.bbappend
@@ -0,0 +1 @@
+COMPATIBLE_MACHINE = "intel-core2-32"
diff --git a/conf/machine/intel-core2-32.conf b/conf/machine/intel-core2-32.conf
index 5c870d9..039528c 100644
--- a/conf/machine/intel-core2-32.conf
+++ b/conf/machine/intel-core2-32.conf
@@ -19,6 +19,8 @@ MACHINE_HWCODECS ?= "va-intel gstreamer-vaapi-1.0"
 
 MACHINE_EXTRA_RRECOMMENDS += "linux-firmware"
 
+MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "gma500-gfx-check"
+
 XSERVER ?= "${XSERVER_X86_BASE} \
 ${XSERVER_X86_EXT} \
 ${XSERVER_X86_FBDEV} \
-- 
2.6.2

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [PATCH] gma500_gfx: Avoid inserting gma500_gfx module for certain devices

[Alejandro Hernandez]

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 
---
 common/recipes-bsp/gma500-gfx-check/gma500-gfx-check_1.0.bbappend | 1 +
 conf/machine/intel-core2-32.conf  | 2 ++
 2 files changed, 3 insertions(+)
 create mode 100644 
common/recipes-bsp/gma500-gfx-check/gma500-gfx-check_1.0.bbappend

diff --git a/common/recipes-bsp/gma500-gfx-check/gma500-gfx-check_1.0.bbappend 
b/common/recipes-bsp/gma500-gfx-check/gma500-gfx-check_1.0.bbappend
new file mode 100644
index 000..5e3c0f9
--- /dev/null
+++ b/common/recipes-bsp/gma500-gfx-check/gma500-gfx-check_1.0.bbappend
@@ -0,0 +1 @@
+COMPATIBLE_MACHINE_intel-core2-32 = "intel-core2-32"
diff --git a/conf/machine/intel-core2-32.conf b/conf/machine/intel-core2-32.conf
index 09303e3..e743b8e 100644
--- a/conf/machine/intel-core2-32.conf
+++ b/conf/machine/intel-core2-32.conf
@@ -19,6 +19,8 @@ MACHINE_HWCODECS ?= "va-intel gstreamer-vaapi-1.0"
 
 MACHINE_EXTRA_RRECOMMENDS += "linux-firmware"
 
+MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "gma500-gfx-check"
+
 XSERVER ?= "${XSERVER_X86_BASE} \
 ${XSERVER_X86_EXT} \
 ${XSERVER_X86_FBDEV} \
-- 
1.8.4.5

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel