On Tue, 2011-12-13 at 08:13 -0800, autif khan wrote:
I built the "crownbay" (not crownbay-noemgd) image as outlined in the
E660 development kit (link
I used poky-edison-6.0.tar.bz2 and crownbay-edison-6.0.0.tar.bz2 and
followed the instructions (short version - extract, move, add
meta-intel/meta-crownbay to bblayers.conf, add MACHINE="crownbay" to
local.conf, bitbake core-image-sato)
The result was the expected set of images in tmp/deploy/images
I loop mounted the core-image-sato-crownbay.ext3 and tried to find
emgd.ko in the file system - I could not find it. (find output
attached - notice that there is no emgd.ko)
Here is the kicker - crownbay-edison-6.0.0.tar.bz2 has a directory
called "binary" which contains core-image-sato-crownbay.hddimg, which
contains rootfs.img, which I also loop mounted and was able to find
the emgd.ko (however this image does not work with my hardware, I am
not sure why). Find output for this is also included below.
I very much doubt that it is included as a part of the kernel, I
looked at the kernel's .config (in
and could not find emgd there either.
In the .config, do you see this?:
If not, then for some reason the options in drm-emgd.cfg from the
drm-emgd feature aren't being picked up. Let me try a build myself here
from the instructions, and see if I can reproduce the problem.
A missing emgd.ko would be a kernel build/config problem, and nothing to
do with the emgd userspace tarballs...
So, my questions is if I am doing something wrong? Do I need to do
something to get the emgd.ko to build? I am using the latest release
(6.0 "Edison" (released on October 17th, 2011)). Please advise.
autif@xu:~/data/dev/yocto/emgd/tmp/deploy/images/1$ sudo find . | grep emgd
sudo find . | grep emgd
yocto mailing list