On 26.09.2014 15:17, TakkTakk wrote:
ok, I removed uEnv.txt, pressed the boot switch.
Starting kernel ... and hang.
why - Image Name: Linux-3.14.0-yocto-standard ?
I don't have a solution to your problem, but I can at least assure to
you that you are not alone ;)
I'm facing the same
On 29/06/14 07:33, Christian Ege wrote:
Hi Andreas,
I created recipes for two out-of-tree kernel modules written by myself
in Yocto. I added these two modules in the machine config to
MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS or even
MACHINE_ESSENTIAL_EXTRA_RDEPENDS.
Have you used the name of
Hi all,
I created recipes for two out-of-tree kernel modules written by myself
in Yocto. I added these two modules in the machine config to
MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS or even
MACHINE_ESSENTIAL_EXTRA_RDEPENDS.
The modules build fine if I build them as targets with bitbake. The
right
Hi all,
I'm currently trying to add a few python packages to my image for which
I need Python 3.3 because a few of them depend on asyncio. These
packages (asyncio itself, websockets and django) are installed with the
usual distribute setup.py scripts either using setuptools or distribute.
Now
On 07/05/14 21:37, Bruce Ashfield wrote:
So you can either patch it into the kernel, or do a bbappend with
that copies it into the source tree
(linux/arch/arm/boot/dts/mydevicetree.dts).
Thx! That worked fine.
For reference, this is what I added:
do_install_prepend() {
cp
Hi Yocto Community,
I'm currently trying to build a custom image for a beaglebone black for
which I need to enable the can-controllers on the SoC. I managed to
create an overlay which already deals with building a few tools for CAN
communication, I created a kernel config snippet for linux-yocto
