[yocto] external layer Git workflow

Hello, I have a distro meta-layer on the top of poky and using few other layers such as meta-openembedded. Is there any recommended Git Workflow to keep it aligned with yocto/openembedded branching/release cycles ? Cheers Ayoub Zaki -- ___ yocto mailing

[yocto] Read-only rootfs update

Hi, We are using yocto to build a custom linux image for our BeagleBoneBlack based hardware. We are using a read-only root file system to prevent data lost if power supply is lost. Now we wan't to be able to update our device. If it is possiple we wan't to use apt/dpkg to do this update. We set up

Re: [yocto] Read-only rootfs update

Hi, * Ruben Schwarz [151124 10:58]: > We are using yocto to build a custom linux image for our BeagleBoneBlack > based hardware. We are using a read-only root file system to prevent data > lost if power supply is lost. > Now we wan't to be able to update our device. If it is possiple we wan't to

[yocto] Header files in /usr/include of rootfs

Hi there, I was trying to add some pre-built binaries and files by using a recipe. The recipe has something like this: SRC_URI = file://files … do_install() { install –d ${D} } FILES_${PN} = “/*” ALLOW_EMPTY_${PN} = “1” INSANE_SKIP_${PN} = “debug-files dev-so” The result was all the binarie

[yocto] Toolchain

hi, in my YOCTO project I seeking inspiration. Now I'm at a point where I am jumping from one to another error. So before I will proceed, could you please check my listing. Is it the right way, respectively correct direction?   My approach - working with poky/fido - downloaded and integrated met

Re: [yocto] Header files in /usr/include of rootfs

* Andy Hung(洪翊桓_Pegatron) [151124 11:35]: > I was trying to add some pre-built binaries and files by using a recipe. > The recipe has something like this: > SRC_URI = file://files > … > do_install() { > install –d ${D} > } What files are you installing? How does those look like? > FILES_${P

[yocto] Re: i.MX6DL Qt5.5 Image

Recipe alsa-utils-alsaconf only create config alsa, can be migrate the recipe fido to jethro: http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-multimedia/alsa/alsa-utils-alsaconf_1.0.28.bb?h=fido -- *Att,Cleiton Bueno* Blog | Linkedin

Re: [yocto] [OE-core] [oe] RFC: Reference updater filesystem

On 11/24/15 4:39 AM, Roman Khimov wrote: > В письме от 23 ноября 2015 15:41:28 пользователь Mariano Lopez написал: >> 1. Use a separate partition for the configuration. >>a. The pro of this method is the partition is not touched during the >> update. >>b. The con of this method is the confi

[yocto] Help with Opensips Recipe - QA run found fatal errors

Hello, I'm writing a recipe to a Sip proxy Opensips, but I'm having problems with QA Issues. In the First time I tried to use make install from Opensips Makefile I had problem with QA Issues, so I added all the folders to FILES_${PN} and FILES_${PN} but I still having problem. So I decided to st

[yocto] Weston Compositor on Yocto core-image-weston-beaglebone

Hi, Im trying to run the weston compositor on a beaglebone black with yocto core-image-weston. Its failing when trying to load the gl-renderer.so module. Please see below the terminal output. I've searched online but there’s not much available on this subject. Any advice would be appreciated. Th

Re: [yocto] [oe] RFC: Reference updater filesystem

On 11/24/2015 4:30 AM, Roman Khimov wrote: В письме от 23 ноября 2015 15:41:28 пользователь Mariano Lopez написал: 1. Use a separate partition for the configuration. a. The pro of this method is the partition is not touched during the update. b. The con of this method is the configurat

[yocto] [PSPLASH 1/2] psplash-fb.c: Fix BGR888 detection

Signed-off-by: Juro Bystricky --- psplash-fb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/psplash-fb.c b/psplash-fb.c index bd9cd9d..e71af8f 100644 --- a/psplash-fb.c +++ b/psplash-fb.c @@ -185,7 +185,7 @@ psplash_fb_new (int angle) fb->rgbmode = RGB888; } el

[yocto] [PSPLASH 0/2] Few fixes for psplash

These patches fix https://bugzilla.yoctoproject.org/show_bug.cgi?id=7236 Considering there was a bug in the BGR888 detection, it is probaly safe to assume it was never used. I modified handling of 24BPP modes somewhat as well, but did not test it. 2

[yocto] [PSPLASH 2/2] psplash-fb.c: Fix some endian issues

The routine psplash_fb_plot_pixel implicitly assumed little endian format when plotting pixels in RGB888 or BGR888 modes. Signed-off-by: Juro Bystricky --- psplash-fb.c | 29 + 1 file changed, 25 insertions(+), 4 deletions(-) diff --git a/psplash-fb.c b/psplash-fb.c

Re: [yocto] [PSPLASH 0/2] Few fixes for psplash

On 24 November 2015 at 16:39, Juro Bystricky wrote: > These patches fix https://bugzilla.yoctoproject.org/show_bug.cgi?id=7236 > Considering there was a bug in the BGR888 detection, it is probaly safe to > assume it was never used. I modified handling of 24BPP modes somewhat as > well, > but did

Re: [yocto] [OE-core] [oe] RFC: Reference updater filesystem

On 11/24/2015 7:47 AM, Mark Hatle wrote: On 11/24/15 4:39 AM, Roman Khimov wrote: В письме от 23 ноября 2015 15:41:28 пользователь Mariano Lopez написал: 1. Use a separate partition for the configuration. a. The pro of this method is the partition is not touched during the update. b.

Re: [yocto] [OE-core] [oe] RFC: Reference updater filesystem

On 11/24/15 11:02 AM, Lopez, Mariano wrote: > > > On 11/24/2015 7:47 AM, Mark Hatle wrote: >> On 11/24/15 4:39 AM, Roman Khimov wrote: >>> В письме от 23 ноября 2015 15:41:28 пользователь Mariano Lopez написал: 1. Use a separate partition for the configuration. a. The pro of this me

Re: [yocto] [OE-core] RFC: Reference updater filesystem

On 11/24/2015 1:32 AM, Randy Witt wrote: On Mon, Nov 23, 2015 at 1:41 PM, Mariano Lopez mailto:mariano.lo...@linux.intel.com>> wrote: There has been interest in an image based software updater in Yocto Project. The proposed solution for a image based updater is to use Stefano Ba

Re: [yocto] [PSPLASH 0/2] Few fixes for psplash

Thanks. I’ll mark the bug 7236 as resolved/fixed. Juro From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Tuesday, November 24, 2015 8:58 AM To: Bystricky, Juro Cc: yocto@yoctoproject.org; Juro Bystricky Subject: Re: [yocto] [PSPLASH 0/2] Few fixes for psplash On 24 November 2015 at 16:39,

Re: [yocto] [OE-core] RFC: Reference updater filesystem

On 11/24/2015 12:06 AM, Anders Darander wrote: * Mariano Lopez [151123 22:41]: There has been interest in an image based software updater in Yocto Project. Ok. Sure, it might be nice with something that can be shared, instead off everyone's building our own solutions. The idea is to integ

Re: [yocto] [PSPLASH 0/2] Few fixes for psplash

On 24 November 2015 at 18:39, Bystricky, Juro wrote: > Thanks. I’ll mark the bug 7236 as resolved/fixed. > > The recipe needs updating first, just bumping the srcrev will do nicely. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.y

[yocto] Cross-compiling python fails with new custom tuning

All, I added a new machine definition with tuning parameters for haswell microarchitectures (basically just duplicated corei7 but tuned it for haswell). This seems to work correctly, but failed when running do_install for python toward the end of the build process. I am running with the Yocto 2.0

Re: [yocto] Cross-compiling python fails with new custom tuning

My guess is that there is a bug in the python integration where it's not realizing the host and target are different systems, so it's trying to run a target program on your host. Your host isn't haswell, so... Illegal Instruction -- and the system stops. The alternative would be something is runn

Re: [yocto] [meta-intel] "Crazy" Xorg memory usage after upgrading from Daisy to Fido

Hi Vincent, I may have made some progress. The undesirable memory usage within Xorg isn’t there if I create an xorg.conf file containing: Section “Device” Identifier “Intel Video” Driver “intel” Option “TearFree” “true" EndSection So it looks as if I need to enable “TearFree”. I didn’t ne

Re: [yocto] [meta-intel] "Crazy" Xorg memory usage after upgrading from Daisy to Fido

Hi Chris, Sorry for the lateness in reply, was too busy with other things. Good to hear that. Xorg.conf is basically to force load particular intended driver (in this case X11 SNA Driver). This is something that that we do not get when we bit-bake for a yocto image; mainly because users from