Re: [yocto] New error in 1.7
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 @@ -13,7 +13,7 @@ AG_GST_INIT dnl initialize automake -AM_INIT_AUTOMAKE([-Wno-portability 1.11 no-dist-gzip dist-xz tar-ustar]) +AM_INIT_AUTOMAKE([-Wno-portability 1.11 no-dist-gzip dist-xz tar-ustar foreign]) dnl define PACKAGE_VERSION_* variables AS_VERSION build proceeds past do_config but now fails at do_complie for the same module. The last part of the error is as follows: __ | In file included from /home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/ gstreamer1.0-plugins-hantro/1.0-r1/gst-hantro-g1-1.0/gst-libs/ext/g1/dwl/gst dwlallocator.c:31:0: /home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/ gstreamer1.0-plugins-hantro/1.0-r1/gst-hantro-g1-1.0/gst-libs/ext/g1/dwl/gst dwlallocator.h:36:28: fatal error: gstg1allocator.h: No such file or directory | #include gstg1allocator.h | ^ | | compilation terminated. | make[5]: *** [libgstdwlallocator_1.0_la-gstdwlallocator.lo] Error 1 | make[5]: Leaving directory `/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi /gstreamer1.0-plugins-hantro/1.0-r1/build/gst-libs/ext/g1/dwl' | make[4]: *** [all-recursive] Error 1 | make[4]: Leaving directory `/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi /gstreamer1.0-plugins-hantro/1.0-r1/build/gst-libs/ext/g1' | make[3]: *** [all-recursive] Error 1 | make[3]: Leaving directory `/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi /gstreamer1.0-plugins-hantro/1.0-r1/build/gst-libs/ext' | make[2]: *** [all-recursive] Error 1 | make[2]: Leaving directory `/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi /gstreamer1.0-plugins-hantro/1.0-r1/build/gst-libs' | make[1]: *** [all-recursive] Error 1 | make[1]: Leaving directory `/home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi /gstreamer1.0-plugins-hantro/1.0-r1/build' | make: *** [all] Error 2 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile (log file is located at /home/lachlan/poky/build-atmel/tmp/work/cortexa5t2hf-vfp-poky-linux-gnueabi/ gstreamer1.0-plugins-hantro/1.0-r1/temp/log.do_compile.3977) ERROR: Task 603 (/home/lachlan/poky/meta-atmel/recipes-multimedia/gstreamer1.0-plugins/gstre amer1.0-plugins-hantro_10.bb, do_compile) failed with exit code '1' _ Any ides on how to proceed? Maybe i go back to using poky 1.6.1 ? Well, you could - but a better alternative would be to debug the issue. Where would gstg1allocator.h be expected to be found? Googling for that file only turns up your post, which is not a good sign - is it perhaps a file that's included as part of gstreamer1.0-plugins-hantro ? You could try changing the gstreamer1.0-plugins-hantro recipe to inherit autotools-brokensep instead of autotools in case it's a separate build directory issue (since that was another change occurred in 1.7). Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] dizzy 1.7 udev automount misbehaviour
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 /run/media/$name stay empty. I debugged the automount script triggered by udev on insert/remove : /etc/udev/scripts/mount.sh and it seems that it's correctly running and mounting the media but somehow something is running after and unmounting the media device ! This behaviour was NOT observed with yocto daisy 1.6. Any help/hint is appreciated ! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Support for writable files with a read-only root file system
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 rootfs, and then
pivot it to make it the new root.
After that you get a root where you can modify any file, and even persist that
change (if you use a persistent overlay).
On 11/26/2014 08:51 AM, Matt Schuckmann wrote:
I've been investigating the support for read only root file systems and trying
to suss out how to support persistent writeable files in my image where the
root file system is read only, this seems like a very common thing for an
embedded Linux system to need but I'm not seeing the support for it.
I should note that I'm working off of the Dylan branch, I'm not sure if things
have changed in a newer branch.
So far I've had to read the code to figure out as much as I have, and I haven't
found any documentation for this, am I missing something?
It appears that my recipe(s) are supposed to install a volatiles file under
${D}${sysconfdir}/default/volatiles/ that lists out the volatile directories,
links and files that need to be created in the image.
For writeable persistent files I would presume that I should specify links that
point to some place on a write partition.
What I don't see is any sort of mechanism for setting up the default files on
that writeable partition, am I on my own for this or is there some other
recommended mechanism.
In my early research I found the MentorEmbedded/meta-ro-rootfs layer that had a
nifty way of specifying VOLATILE_BINDS to create a list of binds that should
occur at boot up and in the process creating the mounts if the target of the
bind didn't exist a copy was made from the read only location, this appears to
have provided a sort of default to go into the writeable location. Was this
functionality abandoned when support for ro-rootfs was brought into oe-core? If
so why?
A good example for the kind of writeable persistent file that I intend to have
is /etc/network/interfaces
How do I go about letting the init_ifupdown recipe install it normally and then
have another recipe or even the image configure it to be either a link or a
bind mount at another location while still preserving the default contents.
I hope I'm making sense here.
Thanks,
Matt S.
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax: (+31) (0) 499 33 69 70
E-mail: mike.looijm...@topic.nl
Website: www.topic.nl
Please consider the environment before printing this e-mail
Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Automake error when building core-image-sato
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 `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2/lib' 4 cd .. make am--refresh 5 make[2]: Entering directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 6 make[2]: Leaving directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 7 cd .. make am--refresh 8 make[2]: Entering directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 9 make[2]: Entering directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 10 make[2]: Leaving directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 11 make[2]: Leaving directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 12 Making all in Automake 13 make[2]: Entering directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2/lib/Automake' 14 cd ../.. make am--refresh 15 make[3]: Entering directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 16 make[3]: Leaving directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 17 cd ../.. make am--refresh 18 make[3]: Entering directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 19 make[3]: Entering directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 20 make[3]: Leaving directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 21 make[3]: Leaving directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 22 Making all in . 23 make[3]: Entering directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2/lib/Automake' 24 cd ../.. make am--refresh 25 make[4]: Entering directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 26 make[4]: Leaving directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 27 cd ../.. make am--refresh 28 make[4]: Entering directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 29 make[4]: Entering directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 30 make[4]: Leaving directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 31 make[4]: Leaving directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2' 32 rm -f Config.tmp Config.pm 33 in=`echo Config.pm | sed 's/\.[^.]*$//'`; sed -e 's,[@]APIVERSION[@],1.11,g' -e 's,[@]PACKAGE[@],automake,g' -e 's,[@]PACKAGE_BUGREPORT[@],bug-autom...@gnu.org,g' -e 's,[@]PERL[@],/usr/bin/perl,g' -e 's,[@]PERL_THREADS[@],1,g' -e 's,[@]SHELL[@],/bin/bash,g' -e 's,[@]VERSION[@],1.11.2,g' -e s,[@]configure_input[@],Generated from $in.in; do not edit by hand.,g -e 's,[@]datadir[@],/home/daniel/Karanka- ntfs3g/yocto/poky-denzil-7.0/p oky-denzil-7.0-build/tmp/sysroots/x86_64-linux/usr/share,g' ./Config.in Config.tmp 34 chmod +x Config.tmp 35 chmod a-w Config.tmp 36 mv -f Config.tmp Config.pm 37 make[3]: Leaving directory `/home/daniel/Karanka-ntfs3g/y octo/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64- linux/automake-native-1.11.2-r3/automake-1.11.2/lib/Automake' 38 Making all in tests 39 make[3]: Entering
Re: [yocto] Automake error when building core-image-sato
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 building. Here's my log : Some information about your build environment will help, in particular what is your build host? Also, you might try a newer version of Poky/Yocto. NOTE: make -j 4 2 Making all in lib 3 make[1]: Entering directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2/lib' 4 cd .. make am--refresh 5 make[2]: Entering directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 6 make[2]: Leaving directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 7 cd .. make am--refresh 8 make[2]: Entering directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 9 make[2]: Entering directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 10 make[2]: Leaving directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 11 make[2]: Leaving directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 12 Making all in Automake 13 make[2]: Entering directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2/lib/__Automake' 14 cd ../.. make am--refresh 15 make[3]: Entering directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 16 make[3]: Leaving directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 17 cd ../.. make am--refresh 18 make[3]: Entering directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 19 make[3]: Entering directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 20 make[3]: Leaving directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 21 make[3]: Leaving directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 22 Making all in . 23 make[3]: Entering directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2/lib/__Automake' 24 cd ../.. make am--refresh 25 make[4]: Entering directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 26 make[4]: Leaving directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 27 cd ../.. make am--refresh 28 make[4]: Entering directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 29 make[4]: Entering directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 30 make[4]: Leaving directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 31 make[4]: Leaving directory `/home/daniel/Karanka-ntfs3g/__yocto/poky-denzil-7.0/poky-__denzil-7.0-build/tmp/work/x86___64-linux/automake-native-1.11.__2-r3/automake-1.11.2' 32 rm -f Config.tmp Config.pm 33 in=`echo Config.pm | sed 's/\.[^.]*$//'`; sed -e 's,[@]APIVERSION[@],1.11,g' -e 's,[@]PACKAGE[@],automake,g' -e 's,[@]PACKAGE_BUGREPORT[@],bug__-autom...@gnu.org mailto:bug-autom...@gnu.org,g' -e 's,[@]PERL[@],/usr/bin/perl,g' -e 's ,[@]PERL_THREADS[@],1,g' -e 's,[@]SHELL[@],/bin/bash,g' -e 's,[@]VERSION[@],1.11.2,g' -e s,[@]configure_input[@],__Generated from $in.in http://in.in/; do not
Re: [yocto] Automake error when building core-image-sato
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 ?. Looking at those instructions, I think that any recent version should work. If you have problems, I'd suggest asking on the meta-ti mailing list meta...@yoctoproject.org n.b. please keep the discussion on the mailing list so that everyone benefits. On Wed, Nov 26, 2014 at 5:00 PM, Gary Thomas g...@mlbassoc.com mailto:g...@mlbassoc.com wrote: 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/ http://maniacbug.wordpress.com/2012/08/03/pandayocto/ and encountered the following error when building. Here's my log : Some information about your build environment will help, in particular what is your build host? Also, you might try a newer version of Poky/Yocto. NOTE: make -j 4 2 Making all in lib 3 make[1]: Entering directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2/lib' 4 cd .. make am--refresh 5 make[2]: Entering directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2' 6 make[2]: Leaving directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2' 7 cd .. make am--refresh 8 make[2]: Entering directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2' 9 make[2]: Entering directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2' 10 make[2]: Leaving directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2' 11 make[2]: Leaving directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2' 12 Making all in Automake 13 make[2]: Entering directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2/lib/Automake' 14 cd ../.. make am--refresh 15 make[3]: Entering directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2' 16 make[3]: Leaving directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2' 17 cd ../.. make am--refresh 18 make[3]: Entering directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2' 19 make[3]: Entering directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2' 20 make[3]: Leaving directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2' 21 make[3]: Leaving directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2' 22 Making all in . 23 make[3]: Entering directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2/lib/Automake' 24 cd ../.. make am--refresh 25 make[4]: Entering directory `/home/daniel/Karanka-ntfs3g/yocto/poky-denzil-7.0/poky-denzil-7.0-build/tmp/work/x86_64-linux/automake-native-1.__11.__2-r3/automake-1.11.2' 26 make[4]: Leaving directory
Re: [yocto] Support for writable files with a read-only root file system
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 your
solution for files that can be non-persistent, but can't be the whole solution.
If you can make a small number of entire directory hierarchies writable (like
/etc, /mnt), you can make
small partitions that are mounted by /etc/fstab. If you want to be more
selective, you need to have
a writable file system where the writable files will reside, with links in the
root file system that point
to them.
-Jim-
From: Mike Looijmans [mike.looijm...@topic.nl]
Sent: Wednesday, November 26, 2014 7:38 AM
To: yocto@yoctoproject.org
Subject: Re: [yocto] Support for writable files with a read-only root file
system
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 rootfs, and then
pivot it to make it the new root.
After that you get a root where you can modify any file, and even persist that
change (if you use a persistent overlay).
On 11/26/2014 08:51 AM, Matt Schuckmann wrote:
I've been investigating the support for read only root file systems and
trying to suss out how to support persistent writeable files in my image
where the root file system is read only, this seems like a very common thing
for an embedded Linux system to need but I'm not seeing the support for it.
I should note that I'm working off of the Dylan branch, I'm not sure if
things have changed in a newer branch.
So far I've had to read the code to figure out as much as I have, and I
haven't found any documentation for this, am I missing something?
It appears that my recipe(s) are supposed to install a volatiles file under
${D}${sysconfdir}/default/volatiles/ that lists out the volatile directories,
links and files that need to be created in the image.
For writeable persistent files I would presume that I should specify links
that point to some place on a write partition.
What I don't see is any sort of mechanism for setting up the default files on
that writeable partition, am I on my own for this or is there some other
recommended mechanism.
In my early research I found the MentorEmbedded/meta-ro-rootfs layer that had
a nifty way of specifying VOLATILE_BINDS to create a list of binds that
should occur at boot up and in the process creating the mounts if the target
of the bind didn't exist a copy was made from the read only location, this
appears to have provided a sort of default to go into the writeable location.
Was this functionality abandoned when support for ro-rootfs was brought into
oe-core? If so why?
A good example for the kind of writeable persistent file that I intend to
have is /etc/network/interfaces
How do I go about letting the init_ifupdown recipe install it normally and
then have another recipe or even the image configure it to be either a link
or a bind mount at another location while still preserving the default
contents.
I hope I'm making sense here.
Thanks,
Matt S.
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax: (+31) (0) 499 33 69 70
E-mail: mike.looijm...@topic.nl
Website: www.topic.nl
Please consider the environment before printing this e-mail
Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Support for writable files with a read-only root file system
-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 system
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 your solution for files that can be non-persistent, but
can't be the whole solution.
If you can make a small number of entire directory hierarchies writable
(like /etc, /mnt), you can make small partitions that are mounted by
/etc/fstab. If you want to be more selective, you need to have a
writable file system where the writable files will reside, with links
in the root file system that point to them.
Hi Jim,
Yes you are correct I want a small number of files into to reside in a
writeable partition with links in the root file system to point to them. I
guess I latched on to the volatiles mechanism because it seems close to meeting
my needs.
Making entire directory hierarchies like /etc writeable seems risky, things
that you never want changed could get changed. Furthermore it makes it harder
to deal with setting up default versions of files.
Is there really no mechanism for this type of thing in OE? It seems like such a
common thing for anybody creating a system with a ro root file system to need
or am I missing something.
If there is not such a mechanism then I will probably recreate the
VOLATILE_BINDS mechanism that was in the MentorEmbedded layer and maybe call it
PERSISTENT_BINDS or some such. I'm pretty new to OE so whatever I come up with
will be pretty rough but I'd be willing to share my solution if there was
interest.
Thanks,
Matt S.
-Jim-
From: Mike Looijmans [mike.looijm...@topic.nl]
Sent: Wednesday, November 26, 2014 7:38 AM
To: yocto@yoctoproject.org
Subject: Re: [yocto] Support for writable files with a read-only root
file system
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
rootfs, and then pivot it to make it the new root.
After that you get a root where you can modify any file, and even
persist that change (if you use a persistent overlay).
On 11/26/2014 08:51 AM, Matt Schuckmann wrote:
I've been investigating the support for read only root file systems
and trying to suss out how to support persistent writeable files in my
image where the root file system is read only, this seems like a very
common thing for an embedded Linux system to need but I'm not seeing
the support for it.
I should note that I'm working off of the Dylan branch, I'm not sure
if things have changed in a newer branch.
So far I've had to read the code to figure out as much as I have, and
I haven't found any documentation for this, am I missing something?
It appears that my recipe(s) are supposed to install a volatiles file
under ${D}${sysconfdir}/default/volatiles/ that lists out the volatile
directories, links and files that need to be created in the image.
For writeable persistent files I would presume that I should specify
links that point to some place on a write partition.
What I don't see is any sort of mechanism for setting up the default
files on that writeable partition, am I on my own for this or is there
some other recommended mechanism.
In my early research I found the MentorEmbedded/meta-ro-rootfs layer
that had a nifty way of specifying VOLATILE_BINDS to create a list of
binds that should occur at boot up and in the process creating the
mounts if the target of the bind didn't exist a copy was made from the
read only location, this appears to have provided a sort of default to
go into the writeable location. Was this functionality abandoned when
support for ro-rootfs was brought into oe-core? If so why?
A good example for the kind of writeable persistent file that I
intend
to have is /etc/network/interfaces How do I go about letting the
init_ifupdown recipe install it normally and then have another recipe
or even the image configure it to be either a link or a bind mount at
another location while still preserving the default contents.
I hope I'm making sense here.
Thanks,
Matt S.
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax: (+31) (0) 499
[yocto] dizzy 1.7 udev automount misbehaviour
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 /run/media/$name stay empty. I debugged the automount script triggered by udev on insert/remove : /etc/udev/scripts/mount.sh and it seems that it's correctly running and mounting the media but somehow something is running after and unmounting it and leaving the mount points empty ! This behaviour is NOT observed with yocto daisy 1.6. Any help/hint is appreciated ! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Headers missing in generated SDK
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. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH 0/2] yocto-bsp 3.17 updates
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
continue with further yocto-bsp work that needs to go on top if this.
The following changes since commit 0bc03af7ee6112fa0af0608b02f715ec8495e4ff:
maintainers.inc: update maintainers (2014-11-26 17:06:10 +)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib.git
tzanussi/yocto-bsp-3.17-master-updates
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=tzanussi/yocto-bsp-3.17-master-updates
Tom Zanussi (2):
yocto-bsp: Update templates to 3.17 kernel
yocto-bsp: Add mips64 support
scripts/lib/bsp/help.py| 1 +
.../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\: }} linux-yocto-tiny_3.17.bbappend | 32 +++
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 32 +++
.../recipes-kernel/linux/kernel-list.noinstall | 8 +--
.../arch/i386/conf/machine/{{=machine}}.conf | 20 +--
.../recipes-kernel/linux/kernel-list.noinstall | 4 +-
...cto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend | 32 +++
...tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend | 32 +++
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 32 +++
.../recipes-kernel/linux/kernel-list.noinstall | 4 +-
...cto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend | 32 +++
...tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend | 32 +++
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 32 +++
.../bsp/substrate/target/arch/mips64/.gitignore| 0
.../arch/mips64/conf/machine/{{=machine}}.conf | 38 +
.../recipes-kernel/linux/kernel-list.noinstall | 5 ++
.../{{=machine}}-preempt-rt.scc | 9 +++
.../{{=machine}}-standard.scc | 9 +++
.../{{=machine}}-tiny.scc | 9 +++
.../{{=machine}}-user-config.cfg | 0
.../{{=machine}}-user-features.scc| 0
.../{{=machine}}-user-patches.scc | 0
.../{{=machine}}.cfg | 65 ++
.../{{=machine}}.scc | 7 +++
...linux-yocto-dev\: }} linux-yocto-dev.bbappend | 25 +
...cto-rt_3.10\: }} linux-yocto-rt_3.10.bbappend | 32 +++
...cto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend | 32 +++
...tiny_3.10\: }} linux-yocto-tiny_3.10.bbappend | 32 +++
...tiny_3.14\: }} linux-yocto-tiny_3.14.bbappend | 32 +++
...tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend | 32 +++
...nux-yocto_3.10\: }} linux-yocto_3.10.bbappend | 32 +++
...nux-yocto_3.14\: }} linux-yocto_3.14.bbappend | 32 +++
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 32 +++
.../arch/powerpc/conf/machine/{{=machine}}.conf| 12
.../recipes-kernel/linux/kernel-list.noinstall | 4 +-
...cto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend | 32 +++
...tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend | 32 +++
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 32 +++
.../arch/qemu/conf/machine/{{=machine}}.conf | 6 +-
.../xserver-xf86-config/{{=machine}}/xorg.conf | 4 +-
.../recipes-kernel/linux/kernel-list.noinstall | 4 +-
.../{{=machine}}-standard.scc | 2 +
...linux-yocto-dev\: }} linux-yocto-dev.bbappend | 10 +++-
...cto-rt_3.10\: }} linux-yocto-rt_3.10.bbappend | 6 ++
...cto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend | 61
...tiny_3.10\: }} linux-yocto-tiny_3.10.bbappend | 6 ++
...-tiny_3.14\: }} linux-yocto-tiny_3.4.bbappend | 6 ++
...tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend | 61
...nux-yocto_3.10\: }} linux-yocto_3.10.bbappend | 10 +++-
...nux-yocto_3.14\: }} linux-yocto_3.14.bbappend | 10 +++-
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 61
.../arch/x86_64/conf/machine/{{=machine}}.conf | 10 +++-
.../recipes-kernel/linux/kernel-list.noinstall | 4 +-
...cto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend | 32 +++
...tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend | 32 +++
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 32 +++
59 files changed, 1200 insertions(+), 45 deletions(-)
create mode 100644
scripts/lib/bsp/substrate/target/arch/arm/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/arm/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-tiny_3.17\: }}
[yocto] [PATCH 1/2] yocto-bsp: Update templates to 3.17 kernel
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\: }} linux-yocto-tiny_3.17.bbappend | 32 +
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 32 +
.../recipes-kernel/linux/kernel-list.noinstall | 8 ++--
.../arch/i386/conf/machine/{{=machine}}.conf | 20 ++--
.../recipes-kernel/linux/kernel-list.noinstall | 4 +-
...cto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend | 32 +
...tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend | 32 +
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 32 +
.../recipes-kernel/linux/kernel-list.noinstall | 4 +-
...cto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend | 32 +
...tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend | 32 +
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 32 +
.../arch/powerpc/conf/machine/{{=machine}}.conf| 12 +
.../recipes-kernel/linux/kernel-list.noinstall | 4 +-
...cto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend | 32 +
...tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend | 32 +
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 32 +
.../recipes-kernel/linux/kernel-list.noinstall | 4 +-
...linux-yocto-dev\: }} linux-yocto-dev.bbappend | 4 +-
...cto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend | 55 ++
...tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend | 55 ++
...nux-yocto_3.10\: }} linux-yocto_3.10.bbappend | 4 +-
...nux-yocto_3.14\: }} linux-yocto_3.14.bbappend | 4 +-
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 55 ++
.../arch/x86_64/conf/machine/{{=machine}}.conf | 10 +++-
.../recipes-kernel/linux/kernel-list.noinstall | 4 +-
...cto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend | 32 +
...tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend | 32 +
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 32 +
32 files changed, 713 insertions(+), 42 deletions(-)
create mode 100644
scripts/lib/bsp/substrate/target/arch/arm/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/arm/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/arm/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto_3.17\: }} linux-yocto_3.17.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto_3.17\: }} linux-yocto_3.17.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto_3.17\: }} linux-yocto_3.17.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/powerpc/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/powerpc/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/powerpc/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto_3.17\: }} linux-yocto_3.17.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/qemu/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto_3.17\: }} linux-yocto_3.17.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/x86_64/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/x86_64/recipes-kernel/linux/{{ if
kernel_choice ==
[yocto] [PATCH 2/2] yocto-bsp: Add mips64 support
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
.../arch/mips64/conf/machine/{{=machine}}.conf | 38 +
.../recipes-kernel/linux/kernel-list.noinstall | 5 ++
.../{{=machine}}-preempt-rt.scc | 9 +++
.../{{=machine}}-standard.scc | 9 +++
.../{{=machine}}-tiny.scc | 9 +++
.../{{=machine}}-user-config.cfg | 0
.../{{=machine}}-user-features.scc| 0
.../{{=machine}}-user-patches.scc | 0
.../{{=machine}}.cfg | 65 ++
.../{{=machine}}.scc | 7 +++
...linux-yocto-dev\: }} linux-yocto-dev.bbappend | 25 +
...cto-rt_3.10\: }} linux-yocto-rt_3.10.bbappend | 32 +++
...cto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend | 32 +++
...tiny_3.10\: }} linux-yocto-tiny_3.10.bbappend | 32 +++
...tiny_3.14\: }} linux-yocto-tiny_3.14.bbappend | 32 +++
...tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend | 32 +++
...nux-yocto_3.10\: }} linux-yocto_3.10.bbappend | 32 +++
...nux-yocto_3.14\: }} linux-yocto_3.14.bbappend | 32 +++
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 32 +++
.../arch/qemu/conf/machine/{{=machine}}.conf | 6 +-
.../xserver-xf86-config/{{=machine}}/xorg.conf | 4 +-
.../{{=machine}}-standard.scc | 2 +
...linux-yocto-dev\: }} linux-yocto-dev.bbappend | 6 ++
...cto-rt_3.10\: }} linux-yocto-rt_3.10.bbappend | 6 ++
...cto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend | 6 ++
...tiny_3.10\: }} linux-yocto-tiny_3.10.bbappend | 6 ++
...-tiny_3.14\: }} linux-yocto-tiny_3.4.bbappend | 6 ++
...tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend | 6 ++
...nux-yocto_3.10\: }} linux-yocto_3.10.bbappend | 6 ++
...nux-yocto_3.14\: }} linux-yocto_3.14.bbappend | 6 ++
...nux-yocto_3.17\: }} linux-yocto_3.17.bbappend | 10 +++-
33 files changed, 489 insertions(+), 5 deletions(-)
create mode 100644 scripts/lib/bsp/substrate/target/arch/mips64/.gitignore
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/conf/machine/{{=machine}}.conf
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/kernel-list.noinstall
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice != \custom\: }} files/{{=machine}}-preempt-rt.scc
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice != \custom\: }} files/{{=machine}}-standard.scc
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice != \custom\: }} files/{{=machine}}-tiny.scc
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice != \custom\: }} files/{{=machine}}-user-config.cfg
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice != \custom\: }} files/{{=machine}}-user-features.scc
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice != \custom\: }} files/{{=machine}}-user-patches.scc
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice != \custom\: }} files/{{=machine}}.cfg
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice != \custom\: }} files/{{=machine}}.scc
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-dev\: }} linux-yocto-dev.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-rt_3.10\: }} linux-yocto-rt_3.10.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-rt_3.14\: }} linux-yocto-rt_3.14.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-tiny_3.10\: }} linux-yocto-tiny_3.10.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-tiny_3.14\: }} linux-yocto-tiny_3.14.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto-tiny_3.17\: }} linux-yocto-tiny_3.17.bbappend
create mode 100644
scripts/lib/bsp/substrate/target/arch/mips64/recipes-kernel/linux/{{ if
kernel_choice == \linux-yocto_3.10\: }} linux-yocto_3.10.bbappend
create mode 100644
