On Wednesday 26 November 2014 07:42:02 peterengcomau...@adam.com.au wrote:
Thanks for your patience. I was successful in building the patch as
follows:
__
--- a/configure.ac2014-08-28 03:20:36.0 +0300
+++ b/configure.ac2014-11-25 23:22:45.129711196 +0300
@@
I have built an image using yocto dizzy 1.7 running on beaglebone using
systemd as init system and I noticed a misbehaviour while inserting
different removable storage device (sd cards /usb sticsk) using
vfat/ext3/ext4 FS that it does not correctly get mounted and the mount
points under
The one-size-fits-all solution is to use an unionfs, and a writable part in
RAM or mounted elsewhere, e.g. in flash (typically a tiny jffs2 partition).
It requires quite some scripting to get right, you have to boot the system and
then mount the overlay, the unionfs to join it with the
Hello, I am new to Yocto and trying to build an Image for Pandaboard using
this guy's guidelines :
http://maniacbug.wordpress.com/2012/08/03/pandayocto/
and encountered the following error when building. Here's my log :
NOTE: make -j 4
2 Making all in lib
3 make[1]: Entering directory
On 2014-11-26 07:51, Pavel Daniel wrote:
Hello, I am new to Yocto and trying to build an Image for Pandaboard using this
guy's guidelines :
http://maniacbug.wordpress.__com/2012/08/03/pandayocto/
http://maniacbug.wordpress.com/2012/08/03/pandayocto/
and encountered the following error when
On 2014-11-26 08:43, Pavel Daniel wrote:
I am running ubuntu 14.04LTS.
The reason i'm using poky denzil 7.0 it's the same that the tutorial states :
later versions of poky had issues building for pandaboard. Is there a later
version of poky that might
work on building for pandaboard ?.
Hi Mike,
It sounds like using volatiles is the opposite of what you want. Unless I miss
the point,
what you want is to have your root file system mounted read-only with only
select files being
writable, and persistent. Volatiles are by definition not persistent.
Volatiles may be a part of
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Jim Rafert
Sent: Wednesday, November 26, 2014 8:33 AM
To: Mike Looijmans; yocto@yoctoproject.org
Subject: Re: [yocto] Support for writable files with a read-only root
file
I have built an image using yocto dizzy 1.7 running on beaglebone using
systemd as init system and I noticed a misbehaviour while inserting
different removable storage device (sd cards /usb sticsk) using
vfat/ext3/ext4 FS that it does not correctly get mounted and the mount
points under
Syed,
Your problem sounds similar to a problem I had getting my own headers and
static library included in the SDK.
Check out this thread to see if it helps.
https://lists.yoctoproject.org/pipermail/yocto/2014-September/021678.html
Matt S.
--
This is the yocto-bsp 3.17 update, along with new mips64 support
addressing [YOCTO #5314].
This is currently gated on the qemu and yocto-bsp machines moving to
3.17, which is in turn still currently gated on [YOCTO #6810], but I'm
submitting what I have now for that eventuality and so that I can
Add 3.17 kernel support.
Signed-off-by: Tom Zanussi tom.zanu...@linux.intel.com
---
.../target/arch/arm/conf/machine/{{=machine}}.conf | 24 --
.../arm/recipes-kernel/linux/kernel-list.noinstall | 4 +-
...cto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend | 32 +
...tiny_3.17\:
mips64 support was recently added to the core BSPs; we should also
support it in yocto-bsp. [YOCTO #5314]
Signed-off-by: Tom Zanussi tom.zanu...@linux.intel.com
---
scripts/lib/bsp/help.py| 1 +
.../bsp/substrate/target/arch/mips64/.gitignore| 0
13 matches
Mail list logo
