[meta-ti] Building for TI 8148 EVM

[Koen Kooi]

Op 24 okt. 2011, om 10:48 heeft Rainer Koenig het volgende geschreven:

> Koen,
> 
> Am 21.10.2011 11:14, schrieb Koen Kooi:
> 
>>> I'm currently trying to build an image for the TI 8148 EVM board. For
>>> that I added the meta-ti layer to the standard Yocto/Edison environment.
>> 
>> Please follow the instructions detailed in the meta-ti README: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/README
>> 
>> Yocto/Poky lacks support for various meta-ti (and OE-classic) constructs needed for a successfull build. Following the instructions above you will get a proper setup.
> 
> Tried this over the weekend on my home PC. Yes, works. But I was just
> able to build a console image. The build of systemd-gnome-image fails
> with the error that nothing provides "DRI". MACHINE=dm8148-evm.

I'm not seeing that with this set of metadata:

OE Build Configuration:
BB_VERSION        = "1.13.3"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "dm814x-evm"
DISTRO            = "angstrom"
DISTRO_VERSION    = "v2011.10-core"
TUNE_FEATURES     = "armv7a vfp neon cortexa8"
TARGET_FPU        = "vfp-neon"
meta-angstrom     = "master:14f73c63403525f85a15f61f88895ba377364338"
meta-oe           
meta-efl          
meta-gpe          
meta-gnome        
meta-xfce         = "master:5da48e6e4a4ab0488943c5e93f005211bd7a22f7"
meta-ti           = "master:2ea9f93740259be7eee59edeb88e632c5441fb58"
meta-ettus        = "master:617506b5cfd2b8325d85f0dcba0232c3f796d044"
meta-efikamx      = "master:2ef47fdd4e8232d766c0c63d9427253ee56e31d0"
meta-nslu2        = "master:17853811179f2760791c6b138f96e9dd15493517"
meta-htc          
meta-nokia        
meta-openmoko     
meta-palm         = "oe-core:794b32d234dbf7e6626c8a0efc915fc04804b9d0"
meta-sugarbay     
meta-crownbay     
meta-emenlow      
meta-fishriver    
meta-jasperforest 
meta-n450         = "master:0ea04b02119c44865e5e1c2529c74950928c3347"
meta              = "master:99da9a4e65f9dffb04efc3ad60125194c476d6b3"

Could you please share your version of that so we can see if there are fixes missing?

regards,

Koen