Yes I install this package, But I think that the problem is that the binary firmware at "/lib/udev" doesn't come with the build. Some one know how to build the binary firmware at "/lib/udev"

Hi it was my type, I couldnt copy and paste so I type it myself on ------------------------------layer.conf:------------------------------ # We have a conf and classes directory, add to BBPATH BBPATH

Hi Andre, You may want to send the content for layer.conf and bblayers.conf. However, you may have a typo if you copied and pasted the error

Hello, I'm getting this error when I run hob, Error Unable to parse /home/andre/fsl-community-bsd/sources/meta-fsl-arm-extra/conf/layer.conf:Failture expanding variable BBPATH, expression was

Hi Gary, What settings in particular? The xsettings-daemon will be overriding gtkrc with values from GConf, so if you're trying to tweak some settings then that will take priority. Other values are

Hi Pierre, <pierre.ficheux@...> wrote: Thank you, that works great on master. This must be new-ish, the bitbake from my gumstix build (HEAD at 846b7c, or roughly Oct 11, 2012) doesn't

$ bitbake -g core-image-minimal result in pn-buildlist. -- Pierre FICHEUX -/- CTO OWI, France -\- pierre.ficheux@... http://ingenierie.openwide.fr

You need to add the modules to IMAGE_INSTALL via their individual package name, or if you just want all modules, use the virtual package "kernel-modules" You can also get it in the image via

Hi everyone, I've looked at Tim's cheat sheet and Robert's FAQ but I can't seem to figure out if there is a simple way to get bitbake to list the packages that will be included in the build of a

I need to use the uio-pci-generic kernel module, but I don’t know how to make it available in my image. Yocto 1.3, core-image-minimal, did ‘bitbake linux-yocto –c menuconfig’ and added

I'd like to be able to control the Sato theme on my system, with a softer approach than editing the "gtk-sato-engine" package. I tried putting updated settings in /home/root/.gtkrc-2.0 but they don't

No, the value is in the accelerated graphics and the effort would be to keep that going - nobody cares about the non-accelerated (or that I've heard anyway). I didn't realize there were already ports

Would that mean only non-accelerated graphics? I remember someone on this list a while back saying they had seen it ported to (I think) 3.2 under a main-stream distro. What would that involve? Is it

I'll do my best to keep 1.3 going until Valley View then! :) Ross

Not me ;-) One of the main reasons I moved 'here' was because we needed the graphics performance. Chris Tapp opensource@... www.keylevel.com

Alternatively there's the fully open source but non-accelerated graphics drivers. This would let the BSP survive, but is anyone (Chris, I'm looking at you here!) using CDT in a situation where

It probably wouldn't take much to bring it back - basically the pvr graphics driver, which I assume is one of the most important features of this BSP for users, is stuck at kernel version 3.0. If

Have you looked at linux-firmware package? rtl8192* should be well supported. By default, firmware files go into /lib/firmware -- Denys

It appears that there will be a 2-day training session following the conference as well (Sat-Sun): See http://events.linuxfoundation.org/events/embedded-linux-conference/schedule: [Add-On] Building