Re: [yocto] Halt problem

Shutdown is supposed to terminate all processes/threads so it's probably not about the watchdog daemon. It sounds more like the classic distro was disabling the hardware watchdog during shutdown and your new distro doesn't do that. Try comparing the kernel watchdog drivers in the two distros

Re: [yocto] PROVIDES problem building u-boot variants

> On 15 January 2018 at 20:01 Andre McCurdy wrote: > > > On Mon, Jan 15, 2018 at 7:12 AM, wrote: > > Let's see if I can explain this well... > > > > I created a recipe to build a u-boot variant (for prod'n programming) - > > "u-boot-PLATFORM-mfg-sec.bb" - which has : > > > > require

Re: [yocto] Remove libjpeg.so (default built even in core-image-minimal) from the rootfs when build yocto

2018-01-16 05:28 skrev Nguyễn Thanh Vũ: > I have statically linked the libjpeg of my own to the exe file, so I do not need the libjpeg.so default built in the /lib of rootfs. How can I modify or specify in the local.conf file so that I can remove that component? It takes quite a lot of space.

Re: [yocto] [poky] Fwd: How to make the os-release package work with local walltime instead of GMT?

On Thu, Jan 11, 2018 at 12:26 AM, Robert Yang wrote: > BUILD_ID = "${@time.strftime('%Y-%m-%d %H:%M:%S',time.localtime())}" > Brilliant! Why isn't this the default? -- ___ yocto mailing list yocto@yoctoproject.org

[yocto] Remove libjpeg.so (default built even in core-image-minimal) from the rootfs when build yocto

I have statically linked the libjpeg of my own to the exe file, so I do not need the libjpeg.so default built in the /lib of rootfs. How can I modify or specify in the local.conf file so that I can remove that component? It takes quite a lot of space. Thank you. --

Re: [yocto] OpenEmbedded developer meeting Sunday before ELC in Portland

On 01/15/2018 10:57 PM, Tom King wrote: > What time...a number of us are headed up from SCaLE sunday morning to ELC... > > its only about 2.5hrs to get there but early will leave a number of us late. We know. It is painful. YP Dev Day is the Thursday after, and I suspect we would lose people

Re: [yocto] OpenEmbedded developer meeting Sunday before ELC in Portland

What time...a number of us are headed up from SCaLE sunday morning to ELC... its only about 2.5hrs to get there but early will leave a number of us late. T On Mon, Jan 15, 2018 at 3:41 PM, Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > > March 11, 2108, Portland > > I guess, by

Re: [yocto] Specifying MACHINE when setting up build environment

On 01/14/2018 01:07 AM, colin.helliw...@ln-systems.com wrote: > Is there a way to specify what MACHINE is put into local.conf when first > setting up the build directory with oe-init-build-env? > I have my own TEMPLATECONF which I use, but I'd like to be able to set the > MACHINE on the command

Re: [yocto] [layerindex-web][PATCH 0/5] update.py: performance improve and 2 fixes

Hi Paul, Sorry, this is the cover letter, I should reply to this one just now. // Robert On 01/03/2018 01:42 PM, Robert Yang wrote: Hi Paul, This email contains two parts: - The first 2 are bug fixes - The other 3 are performance improvements, I have 124 layers, the "update.py -b " needs

Re: [yocto] [layerindex-web][PATCH 1/5] utils.py: fix remove obsolete dependencies

Hi Paul, Do you have any comments, please ? // Robert On 01/03/2018 01:42 PM, Robert Yang wrote: The obsolete dependency is the one which is in database but not in conf/layer.conf anymore. The old code had a problem for newly created layerbranch, the new layerbranch has no dependencies, so no

Re: [yocto] OpenEmbedded developer meeting Sunday before ELC in Portland

> March 11, 2108, Portland I guess, by this date yocto community will experience release 24.7 or similar... If?! ;-) Zoran ___ On Mon, Jan 15, 2018 at 11:30 PM, Philip Balister wrote: > We are setting up an OpenEmbedded developer meeting on the Sunday before > ELC.

[yocto] OpenEmbedded developer meeting Sunday before ELC in Portland

We are setting up an OpenEmbedded developer meeting on the Sunday before ELC. More information to follow, I just wanted to make sure everyone had the date before making ELC travel arrangements. March 11, 2108, Portland Philip -- ___ yocto mailing list

Re: [yocto] PROVIDES problem building u-boot variants

On Mon, Jan 15, 2018 at 7:12 AM, wrote: > Let's see if I can explain this well... > > I created a recipe to build a u-boot variant (for prod'n programming) - > "u-boot-PLATFORM-mfg-sec.bb" - which has : > > require u-boot-PLATFORM.inc > UBOOT_MACHINE =

[yocto] Yocto SDK: how to rebuild *.dtb? (fatal error: dt-bindings/gpio/gpio.h: No such file or directory)

I installed yocto SDK for my beaglebone black. But when I try to rebuild am335x-boneblack.dtb, I got error: "arch/arm/boot/dts/am33xx.dtsi:11:10: fatal error: dt-bindings/gpio/gpio.h: No such file or directory" Any hint? Thanks! Jerry -- ___ yocto

[yocto] Error do_compile libepoxy

Hello, I am trying to build libepoxy but the do_compile tasks breaks. I found following error messages in the logs: arm-poky-linux-gnueabi-gcc -march=armv6 -mfpu=vfp -mfloat-abi=hard -mtune=arm1176jzf-s -mfpu=vfp

[yocto] Halt problem

Hi y'all, I ran into a problem using shutdown -h (or halt) on an openembedded-core (yocto) distro running on the Atmel at91sam9g45. We used to run an openembedded-classic (angström) based OS with kernel version 2.6.35.14+. Here, halting the system would cause it to shutdown without

Re: [yocto] conf/machine/ in my custom layer doesn't get parsed

Hi Anuj, On Mon, Jan 15, 2018 at 5:47 PM, Anuj Mittal wrote: > I hope that this machine name, colibri-imx6, isn't being used in some > other included layer as well ... > > meta-freescale-3rdparty/conf/machine/colibri-imx6.conf? Can you try > changing the name? > You are a

[yocto] PROVIDES problem building u-boot variants

Let's see if I can explain this well... I created a recipe to build a u-boot variant (for prod'n programming) - "u-boot-PLATFORM-mfg-sec.bb" - which has : require u-boot-PLATFORM.inc UBOOT_MACHINE = "tx6s-8035_mfg_sec_config" SRC_URI += "file://tx6s-8035_mfg_sec_defconfig" And 'bitbake

Re: [yocto] Specifying MACHINE when setting up build environment

> On 13 January 2018 at 18:52 Jan Siegmund wrote: > > > Hi, > > Am 13.01.2018 um 18:07 schrieb colin.helliw...@ln-systems.com: > > Is there a way to specify what MACHINE is put into local.conf when first > > setting up the build directory with oe-init-build-env? > > I have my own TEMPLATECONF

Re: [yocto] conf/machine/ in my custom layer doesn't get parsed

On 01/15/2018 09:13 PM, Isaac Nickaein wrote: > Hi Anuj, > > On Mon, Jan 15, 2018 at 4:00 PM, Mittal, Anuj wrote: >> Have you defined BBPATH in your layer.conf correctly? > > > I guess so. Here is relevant lines in layer.conf for BBPATH: > > # We have a conf and classes

Re: [yocto] conf/machine/ in my custom layer doesn't get parsed

Hi Anuj, On Mon, Jan 15, 2018 at 4:00 PM, Mittal, Anuj wrote: > Have you defined BBPATH in your layer.conf correctly? I guess so. Here is relevant lines in layer.conf for BBPATH: # We have a conf and classes directory, add to BBPATH BBPATH .= ":${LAYERDIR}" # We have

Re: [yocto] conf/machine/ in my custom layer doesn't get parsed

On Mon, Jan 15, 2018 at 4:00 PM, Mittal, Anuj wrote: > > Have you defined BBPATH in your layer.conf correctly? Hi Anuj, I guess so. Here is relevant lines in layer.conf for BBPATH: # We have a conf and classes directory, add to BBPATH BBPATH .= ":${LAYERDIR}" # We have

Re: [yocto] meta-ti layer failed with Daisy

Hi Satya, > I am building the core-image-minimal for Daisy with meta-ti layer included in > bblayers.conf file after removing meta-yocto-bsp layer. I am getting the > error shown below, This is a very old version. Please update to one of the latest supported releases. >

Re: [yocto] conf/machine/ in my custom layer doesn't get parsed

Hi Issac, > I've created a custom meta layer over poky rocko and added it to > bblayer.conf. I've > also set the appropriate MACHINE value in > conf/local.conf: > > MACHINE = "colibri-imx6" > > There is a machine specific conf file in this meta layer, but it doesn't get > parsed. This > file

[yocto] conf/machine/ in my custom layer doesn't get parsed

Hi, I've created a custom meta layer over poky rocko and added it to bblayer.conf. I've also set the appropriate MACHINE value in conf/local.conf: MACHINE = "colibri-imx6" There is a machine specific conf file in this meta layer, but it doesn't get parsed. This file is located at

[yocto] Moving all meta-* directories inside a parent directory like "layers"

Hi, I've clone the Poky on rocko branch from http://git.yoctoproject.org/git/poky By default, it gives a directory structure in which all meta-* layers are scattered inside the root directory. A more clean approach is to move all meta-* directories in a dedicated directory for layers e.g.

Re: [yocto] GPIO configuration in imx6ull

Hi, Are you aware of pin-muxing subject? You can change GPIO settings in U-boot with gpio_* functions. You can change them in DTS with gpio-edm driver from Wandboard kernel ( https://github.com/wandboard-org/linux/blob/4.1-2.0.x-imx/drivers/input/keyboard/gpio_edm.c ) You can also change them in

Re: [yocto] [OE-core] liblzma: Memory allocation failed on do_package_rpm

On 01/15/2018 08:20 AM, Manjukumar Harthikote Matha wrote: All, Has anybody seen this error? Finished binary package job, result 0, filename (null) error: create archive failed: cpio: write failed - Cannot allocate memory error: liblzma: Memory allocation failederror: liblzma: Memory

[yocto] meta-ti layer failed with Daisy

Dear All, I am building the core-image-minimal for Daisy with meta-ti layer included in bblayers.conf file after removing meta-yocto-bsp layer. I am getting the error shown below, [Satya]~/Yocto-Daisy-Labs/poky/build bitbake core-image-minimal Loading cache: 100%