On Wed, Dec 18, 2013 at 01:29:25AM +, Brad Litterell wrote:
Hi Paul,
Thanks for that tip. For my private packages I don't build directly from
git, but from a tarball (in turn created from my working directory) because I
want to be able to build the source I'm working on without
On 18 December 2013 07:50, wuteng wu wuten...@gmail.com wrote:
I built the Yocto 1.5 project for my SAMA5D34-EK board, i add the libxml2 by
IMAGE_INSTALL_append = libxml2, i got the image and programmed it into
NAND Flash of the board, but when i type python -c import libxml2 from the
hyper
Please don't take conversations off the list, so that others can help/learn.
On 18 December 2013 14:22, wuteng wu wuten...@gmail.com wrote:
I'm newbie to Yocto, could u tell me more details?
I found some info under the dir:
/home/teng/poky/meta/recipes-core/libxml/libxml2.inc as below:
I've been beating my head for a few days now, and would love a little
guidance. Acknowledging that there are multiple ways to skin the cat, my
immediate goal is to reduce the boot time, presumably using poky-tiny.
I have poky-tiny building for my hardware under dora.
I have it booting on
John,
What is your actual problem? You appended the tiny-init recipe and your
changes do or do not get put into the rootfs? If you could post your recipe
then folks can look at it.
As far as boot time is concerned, you need to distinguish boot loader and
kernel boot from user space. It looks as
Rudi,
From a first view, my problem is that my embedded Yocto-Linux device takes
too long from the application of power to the time that it is first able to
a) signal the user that the device is waking up and b) respond to events
from I/O (Ethernet and CAN). (40+ seconds prior to shifting to
[YOCTO #5676]
Signed-off-by: Saul Wold s...@linux.intel.com
---
documentation/profile-manual/profile-manual-usage.xml | 1 -
1 file changed, 1 deletion(-)
diff --git a/documentation/profile-manual/profile-manual-usage.xml
b/documentation/profile-manual/profile-manual-usage.xml
index
We are in need of enabling the CONFIG_I2C_KEMPLD for a build for our
Kontron (architecture is x86).
We have been using the Crownbay BSP. But of course I did a google search
and found patches in the Linux kernel for allowing i2c_kempld. Also these
patches were associated with Fish River Island
Hit the send too early. My questions are: What kernel versions and what
BSPs of Yocto support the CONFIG_I2C_KEMPLD? We are using Linux Kernel
3.8.4 but we found a link saying KEMPLD is supported in a Linux kernel
version as high as 3.1.2.
Anyone out there know about this? (see below for first
Hello all,
I have a few questions about the files in deploy/images.
When working with beagleboard I would see MLO u-boot and uImage. I would
copy these to DOS partition.
Now Working with ZedBoard I have been using the BOOT.bin, devicetree.dtb
and zImage. The BOOT.bin was created with xilinx FSBL
On 12/18/2013, 6:16 PM, Ravi Rao wrote:
Hi Bruce,
Thanks a lot for a very quick response. Please keep me in loop if
you find any thing about this issue. Also I was wondering if there is a
work around that I can use to get past this issue.
Doing a manual clone, putting it in a local
Hi All,
We have a custom Board which is based on mpc8349EMDS which is based on e300.
I got the Toolchain downloaded using poky-dora-10.0.0 project which
supports e300 core
Now when I cross compile Linux kernel ver 2.6.32 the system boots up and
works fine.
But when I cross compile Linux kernel
12 matches
Mail list logo
