[yocto] How can I change the default ext4 or etx3 of the rootfs to ext2 or jffs2 in yocto build?

2018-01-11 Thread Nguyễn Thanh Vũ
I want to minimize the size of the image built in core-image-minimal. However, I have no idea how to change the local.conf file or recipe file. Can anyone help me? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/y

Re: [yocto] How can I change the default ext4 or etx3 of the rootfs to ext2 or jffs2 in yocto build?

2018-01-11 Thread John, Maxin
Hi, An easy way will be to refer Yocto documentation: http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html and for required rootfs changes, use IMAGE_FSTYPES: http://www.yoctoproject.org/docs/2.4/mega-manual/mega-manual.html#var-IMAGE_FSTYPES >From: yocto-boun...@yocto

[yocto] libgcc.a size

2018-01-11 Thread Mircea Gliga
Hello I just upgraded from krogoth to rocko, and noticed the resulting rootfs image increased significantly. What stands out is a big bump in size for /usr/lib/arm-poky-linux-gnueabi/7.2.0/libgcc.a from 5 MB in krogoth(gcc 5.3.0) to 25 MB in rocko. Can someone shed some light ? What can be do

Re: [yocto] [meta-oic] Question about Iotivity 1.3.0/1 and fixes status

2018-01-11 Thread Philippe Coval
On 11/01/18 02:30, Chanho Park wrote: > Hi Philippe, > Hi Chanho Park, HNY to you > I found you already prepared iotivity 1.3.0, 1.3.1 recipes and fixes > in your github tree[1]. Yes they are still under review, did you test them ? Maybe I should resend them, now. > I wonder why you don’t post

Re: [yocto] libgcc.a size

2018-01-11 Thread Zoran Stojsavljevic
> What stands out is a big bump in size for > /usr/lib/arm-poky-linux-gnueabi/7.2.0/libgcc.a from 5 MB in krogoth(gcc > 5.3.0) to 25 MB in rocko. Static library, probably compiled with -g (debug info included). You need to recompile libgcc excluding -g option... My best guess. Zoran On Thu, Ja

Re: [yocto] libgcc.a size

2018-01-11 Thread Mircea Gliga
Hi guys >libgcc.a is "out-f-the-box" in rocko 25MB, but why should it be integrated in rootfs ? I asked myself the same question. Not clear for me yet how and why it gets in the rootfs. Thanks and regards Mircea On 11/01/18 13:51, Stefano Babic wrote: Hi Zoran, Mircea, On 11/01/2018 11:

Re: [yocto] libgcc.a size

2018-01-11 Thread Stefano Babic
Hi Zoran, Mircea, On 11/01/2018 11:16, Zoran Stojsavljevic wrote: >> What stands out is a big bump in size for >> /usr/lib/arm-poky-linux-gnueabi/7.2.0/libgcc.a from 5 MB in krogoth(gcc >> 5.3.0) to 25 MB in rocko. > > Static library, probably compiled with -g (debug info included). You > need

Re: [yocto] libgcc.a size

2018-01-11 Thread Stefano Babic
Hi Mircea, On 11/01/2018 12:54, Mircea Gliga wrote: > Hi guys > >>libgcc.a is "out-f-the-box" in rocko 25MB, but why should it be > integrated in rootfs ? > > I asked myself the same question. Not clear for me yet how and why it > gets in the rootfs. It is not - I have not in my -rocko projects

Re: [yocto] fstab entry not mounting at boot-up

2018-01-11 Thread Mike Looijmans
On 05-01-18 20:43, Edward Wingate wrote: My system has a USB-SSD drive and I added this to my fstab: /dev/sda1 /mnt/driveauto defaults,nonempty 0 0 But it doesn't get mounted on start-up. I can use "mount -a" after start-up and it mounts successfully. Everything else in fstab gets mou

[yocto] [layerindex-web] Updating layers?

2018-01-11 Thread Steve Bedford
Hello! Is the layerindex not running the update script? I see end of September as last updates, and a bunch of branches in our layer (meta-timesys) were never picked up. Or is there another way for maintainers to add branches / trigger an update? Thanks, -- Steve Bedford Timesys Corporation -

Re: [yocto] Issues building Extensible SDK

2018-01-11 Thread Martin Siegumfeldt
Hi Robert, Thank you very much, adding the lines require conf/distro/include/yocto-uninative.inc INHERIT += "uninative" to the distro configuration enables the build to succeed. Br, Martin From: Robert Yang Sent: Thursday, January 11, 2018 6:45:29 AM To:

[yocto] [PATCH V2] beaglebone: Fix serial console device node

2018-01-11 Thread Marek Vasut
The serial console on BBB is now on /dev/ttyS0 , not /dev/ttyO0, which comes from legacy omap-serial driver. Support both options using SERIAL_CONSOLES. For details of the change to /dev/ttyS0, see Linux kernel commit 61929cf0169d91366fd3f30d6ee60681b037bc19 Author: Sebastian Andrzej Siewior Date

Re: [yocto] [PATCH] beaglebone: Fix serial console device node

2018-01-11 Thread Marek Vasut
On 01/08/2018 12:28 PM, Martin Hundebøll wrote: > Hi Marek, > > On 2018-01-07 17:16, Marek Vasut wrote: >> The serial console on BBB is on /dev/ttyS0 , not /dev/ttyO0 . >> This changed again, so fix this. >> >> Signed-off-by: Marek Vasut >> Cc: Joshua Lock >> Cc: Richard Purdie >> --- >>   meta

[yocto] applying patches depending on the image's name

2018-01-11 Thread Vadim Intelegator
Hello, I have several images (image-a.bb and image-b.bb) in a yocto layer and want to apply different patches to the kernel depending on the current image name. How can that be done? Thank you in advance. -- Vadim signature.asc Description: PGP signature -- _

[yocto] Recipe for JNI Wrapper (libusb4java)

2018-01-11 Thread Nathan Roberts
I'm trying to create a recipe for libusb4Java ( https://github.com/usb4java/libusb4java/). I have the following recipe SUMMARY = "Native library support for usb4java" HOMEPAGE = "http://usb4java.org"; BUGTRACKER = "https://github.com/usb4java/libusb4java/issues"; SECTION = "libs" DEPENDS = "libus

Re: [yocto] applying patches depending on the image's name

2018-01-11 Thread Burton, Ross
No, because images are built from packages, and the packages have already been built by the time the image is considered. Using master you can build two different kernels in the same build and have different kernels in different images. Ross On 9 January 2018 at 15:54, Vadim Intelegator < v.inte

Re: [yocto] Issues building Extensible SDK

2018-01-11 Thread Khem Raj
On Thu, Jan 11, 2018 at 12:56 AM, Martin Siegumfeldt wrote: > Hi Robert, > > > Thank you very much, adding the lines > > > require conf/distro/include/yocto-uninative.inc > INHERIT += "uninative" > > to the distro configuration enables the build to succeed. > I thought uninative was optional. Is

[yocto] wic error during creating sdimg

2018-01-11 Thread Belisko Marek
Hi, below error is from wic when creating SD image. I have no clue where error can be. I'm portin mender to orangepi and already asked for support but seems nobody really understand what is going on. Any help appreciated. error log: DEBUG: Executing python function set_image_size DEBUG: Python f

Re: [yocto] wic error during creating sdimg

2018-01-11 Thread Belisko Marek
Hi, seems to be caused by empty IMAGE_BOOT_FILES. When added to machine.conf everything works as expected. Sorry for noise. On Thu, Jan 11, 2018 at 8:45 PM, Belisko Marek wrote: > Hi, > > below error is from wic when creating SD image. I have no clue where > error can be. I'm portin mender to or

[yocto] [ANNOUNCEMENT] Yocto Project 2.3.3 (pyro 17.0.3) Released

2018-01-11 Thread Tracy Graydon
Hello, The latest release of the Yocto Project 2.3.3 (pyro-17.0.3) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.3.3/poky-pyro-17.0.3.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.3.3/poky-pyro-17.0.3.tar.bz2 A gpg signed version of these rel

[yocto] [ANNOUNCEMENT] Yocto Project 2.4.1 (rocko-18.0.1) Released

2018-01-11 Thread Tracy Graydon
Hello, The latest release of the Yocto Project 2.4.1 (rocko-18.0.1) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4.1/poky-rocko-18.0.1.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4.1/poky-rocko-18.0.1.tar.bz2 A gpg signed version of these

Re: [yocto] [meta-oic] Question about Iotivity 1.3.0/1 and fixes status

2018-01-11 Thread Chanho Park
Hi Philippe, On Thu, 11 Jan 2018 at 7:11 PM Philippe Coval < philippe.co...@osg.samsung.com> wrote: > > On 11/01/18 02:30, Chanho Park wrote: > > Hi Philippe, > > > Hi Chanho Park, HNY to you Wish you the same. > > I found you already prepared iotivity 1.3.0, 1.3.1 recipes and fixes > > in yo

[yocto] yocto test framework: problem with bitbake image -c testexport

2018-01-11 Thread Heiko Schocher
Hello all, I just tried to use the yocto testframework as described in [1]. Base is http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=rocko&id=759b36a8de86bfe5355880a76077af47e156701d As I want to start the tests manually with having the tests exported (with the goal to fully automate all