[meta-amd] Integrating Open Source ATI and Glamor drivers into Yocto
Nath, Arindam
Arindam.Nath at amd.com
Wed Apr 1 04:29:44 PDT 2015
Hi Simon,
I am assuming that you are trying to create an yocto image for AMD baldeagle platform. if yes, then you do need to include openembedded layer in your bblayers.conf file since meta-amd depends on it. Since you are using dizzy release of poky, make sure you checkout dizzy branch of meta-amd as well as meta-openembedded.
Also I noticed that your local.conf file has MACHINE variable set to generic86-64. Change it to baldeagle, and you should be good to go.
HTH.
Thanks,
Arindam
From: meta-amd-bounces at yoctoproject.org [mailto:meta-amd-bounces at yoctoproject.org] On Behalf Of Chen, Simon (N-DCR SYSTEM HOUSE)
Sent: Wednesday, April 01, 2015 4:01 AM
To: meta-amd at yoctoproject.org
Subject: [meta-amd] Integrating Open Source ATI and Glamor drivers into Yocto
Hi all,
I am trying to integrate the open source AMD Radeon driver (otherwise known as xf86-video-ati), along with Glamor, into my Yocto image (poky-dizzy-12.0.1) using the latest version of meta-amd (dizzy branch). In my bblayer.conf, I included meta-amd's common and meta-baldeagle layers. When I initially bitbaked, I encountered errors relating to .bbappend files in common/recipes-benchmark, common/recipes-multimedia, common/recipes-support, and common/recipes-core/llvm folders. They appear to be trying to append to recipes found in meta-oe, which I don't have. Worrying that I might encounter incompatibility issues when mixing Yocto and OE components, I've decided to discard these recipe folders for the time being. I've also chose to comment out some code from common/recipes/grub/grub-efi_2.00.bbappend and meta-baldeagle/conf.layer.conf, since they were acting up with the rest of my yocto build.
Afterwards I was able to build a Yocto image successfully. But when I try booting the image on my target board, I was not able to find the ATI or the Glamor .so driver files in any of the lib folders that I had in my system. They also did make on to the list of running modules when I did "lsmod."
Do you have any ideas on what could be wrong? Am I missing some configuration steps? It also appears meta-amd was originally meant for integration for the OpenEmbedded environment rather than Yocto. Perhaps I am applying this amd layer the wrong way?
If interested, I've also attached changed files with path locations included at the top of each one.
Thanks,
Simon
More information about the meta-amd
mailing list