Re: [yocto] ICECC build failures?

Thank you for your comment. So they are. I will try to mask them one by one then. From: Peter Bergin Sent: Friday, July 1, 2016 1:05 PM To: Takashi Matsuzawa; yocto@yoctoproject.org Subject: Re: [yocto] ICECC build failures? Hi, On

Re: [yocto] Shorter build time?

Hmm, thank you for your comments. So, they may be talking about single-thread nature within a python program, and as for bitbake python tasks they should be working in parallel. There seems to be PyPy, Stackless Python, etc. but I am not sure they can be tried 'in-place' to see if they work

Re: [yocto] customizing system configuration files in my image

Usually I do it by adding bbappend of corresponding packages to override original files, the interfaces is provided by init-ifupdown, the inittab is provided by sysvinit-inittab. An example: http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/tree/recipes-core/init-ifupdown Best Regards,

Re: [yocto] [Recipe reporting system] Upgradable recipe name list

On 07/01/2016 04:31 PM, recipe-rep...@yoctoproject.org wrote: > This mail was sent out by Recipe reporting system. > > This message list those recipes which need to be upgraded. If maintainers > believe some of them needn't to upgrade at this time, they can fill > RECIPE_NO_UPDATE_REASON in

[yocto] [Recipe reporting system] Upgradable recipe name list

This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade at this time, they can fill RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder until newer upstream version

[yocto] [Recipe reporting system] Upgradable recipe name list

This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade at this time, they can fill RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder until newer upstream version

Re: [yocto] Shorter build time?

So we have full parallelism :) 2016-07-01 14:01 GMT-03:00 Burton, Ross : > > On 1 July 2016 at 17:37, Daniel. wrote: >> >> I read that python can't execute multiple threads simultaneously, but >> that wouldn't be a problem if each python task is

Re: [yocto] Shorter build time?

On 1 July 2016 at 17:37, Daniel. wrote: > I read that python can't execute multiple threads simultaneously, but > that wouldn't be a problem if each python task is executed at its own > interpreter instance (process). This last statement is what I don't > really know, some

Re: [yocto] Shorter build time?

Hi Takashi, I read that python can't execute multiple threads simultaneously, but that wouldn't be a problem if each python task is executed at its own interpreter instance (process). This last statement is what I don't really know, some experts on Yocto's internals may clarify that, maybe :)

Re: [yocto] [yocto-autobuilder][PATCH] bin/release_scripts/release.py: Add some basic logging

On Wed, 2016-06-29 at 16:08 -0700, Graydon, Tracy wrote: > This patch adds some basic logging to help find failure point should > the script > barf due to lost ssh session, etc. Without it, finding where to > resume is not > particularly entertaining. > > Signed-off-by: Graydon, Tracy

Re: [yocto] setcap using recipe

On 1 July 2016 at 15:03, Mathieu Allard wrote: > I think that the main issue here is that the pkg_postinst function runs > its action at the rootfs creation time, and not on the target as advised by > Ross. > Yes, as I said in the first suggestion you'll need to

[yocto] Yocto Project Status WW27

Current Dev Position: YP 2.2 M2 Next Deadline: YP 2.2 M2 cut off would be: 7/18/16 SWAT team rotation: Armin -> Bill (https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team) Key Status/Updates: * QA test report for 2.2 M1 is looking reasonable. There are some issues in toaster,

Re: [yocto] Failed to cross compile kernel with Yocto toolchain

Thanks a lot for your comments, Daniel. Can somebody please shed light on how to fix the issue in Yocto recipes? Best Regards, Zhenhua > -Original Message- > From: Daniel. [mailto:danielhi...@gmail.com] > Sent: Friday, July 01, 2016 4:48 AM > To: Zhenhua Luo >

Re: [yocto] Xorg failing with SEGV after Krogoth update

On Thu, Jun 30, 2016 at 10:24 PM, Allan Chandler wrote: > We recently did (attempted? ) an upgrade of our Yocto embedded build system > from Fido to Krogoth and, other than one rather massive issue, it all went > well. > > > > The massive issue is the fact that X11 is

[linux-yocto] [PATCH 7/7] usb: typec: Use strtobool instead of kstrtobool for 4.4 kernel

Upstream-Status: Inappropriate [other] Type C support has been backported from kernel 4.7-rc which does not need this change. Type C support has been backported from 4.7 kernel which has kstrtobool function to convert string to bool. In 4.4 kernel, we have

[linux-yocto] [PATCH 4/7] acpi/pmic: modify the pen function signature to take bit field

From: Bin Gao Upstream-Status: Submitted [https://patchwork.kernel.org/patch/9196245/] This patch was submitted by Bin Gao. Issue description: On some pmics, the policy enable for thermal alerts refers to different bit fields of the same registers,

[linux-yocto] [PATCH 2/7] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY

Upstream-Status: Submitted [https://lkml.org/lkml/2016/6/29/350] This patch was submitted by Heikki Krogerus on lkml.org. This adds driver for the USB Type-C PHY on Intel WhiskeyCove PMIC which is available on some of the Intel Broxton SoC based platforms.

[linux-yocto] [PATCH 0/7] USB Type C backport on linux-yocto-4.4 bxt-rebase branch

This patch set backports USB Type C support on linux-yocto-4.4 from kernel version 4.7-rc. These patches have been submitted upstream and the approval is in progress, hence may not be final. The patches have been rebased on bxt-rebase branch. Bin Gao (2): acpi/pmic: modify the pen function

Re: [yocto] Failed to cross compile kernel with Yocto toolchain

you can try to set HOSTCC=/usr/bin/gcc along when you call make may be via EXTRA_OEMAKE, problem you have is that kernel is expecting gcc to be used for host utilties and ccache has overrides for gcc which may not be working in all situations. Ideally you should just uninstall ccache from your

Re: [yocto] setcap using recipe

Hmmm I see, Well, I didn't note that. And yeah, that command should be ran at first boot, (that feature saved my life a bunch of times :) ) Regards, 2016-07-01 11:03 GMT-03:00 Mathieu Allard : > Hello, > > I think that the main issue here is that the pkg_postinst

Re: [yocto] setcap using recipe

Hello, I think that the main issue here is that the pkg_postinst function runs its action at the rootfs creation time, and not on the target as advised by Ross. The chapter 5.3.16, "post-installation scripts" in the mega-manual offers some detailed explanations on how to make it run after the

Re: [yocto] setcap using recipe

Does your target filesystem support it? ubifs doesn't :( http://www.linux-mtd.infradead.org/doc/ubifs.html#L_xattr 2016-07-01 9:53 GMT-03:00 Kumar, Shrawan : > Hello Ross, > > > > None of the approach is working . I have attached the recipe where I am > trying to

[yocto] [meta-selinux] Regarding "systemd" support with refpolicy-minimum v20151208

Hi, Using refpolicy-minimum v20151208 with systemd as init manager, I am facing few issues during enforcing mode, 1. systemd service status check, start & stop 2. auditd logfile error, so it is mixing with the boot log. 3. also other avc denials related to tmpfs & other types etc.. setup

Re: [yocto] customizing system configuration files in my image

After that you can create a image recipe and inherit from that .bbclass. If you don't want to create a .bbclass you can use this same aproach directly on your image recipe :) Regards, 2016-07-01 10:16 GMT-03:00 Daniel. : > Hi Ottavio, > > There is more than way to do it.

[yocto] [meta-selinux][PATCH] README: update with systemd & virtual/refpolicy details

From: Shrikant Bobade add init manager user guidelines and examples for using refpolicy with perticular version and type. Signed-off-by: Shrikant Bobade --- README | 27 +-- 1 file changed, 25 insertions(+), 2

Re: [yocto] customizing system configuration files in my image

Hi Ottavio, There is more than way to do it. In your case I would use ROOTFS_POSTPROCESS_COMMAND to modify files prior the creation of the rootfs. You may: - Create a .bbclass for your image inheriting core-image for example. - Create a shell function to do some sed magic. - Setup that function

Re: [yocto] setcap using recipe

Hello Ross, None of the approach is working . I have attached the recipe where I am trying to execute postinst . It builds successfully , But when I run getcap on the target , does not return the set capabilities. Help will be highly appreciated . Regards Shrawan From: Burton, Ross

[linux-yocto] [PATCH 4/5] drivers/usb: Make Axxia USB Use Coherent Memory for DMA

From: John Jacques Even with 'dma-coherent' in the device tree USB node, the XHCI driver creates devices without copying the 'archdata' structure, where the dma_coherent field is defined. To handle this, set the dma_coherent field in all devices that are created by the

[linux-yocto] [PATCH 5/5] drivers/net: Disable Pause Frames in the Axxia Network Interface

From: John Jacques Signed-off-by: John Jacques --- drivers/net/ethernet/intel/axxia/nemac.c | 17 ++--- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/drivers/net/ethernet/intel/axxia/nemac.c

[linux-yocto] [PATCH 2/5] board/axxia: SPI Updates for Victoria

From: John Jacques Change the max frequency and add the backup serial flash. Signed-off-by: John Jacques --- arch/arm64/boot/dts/intel/axm5616-victoria.dts | 44 +- 1 file changed, 43 insertions(+), 1 deletion(-) diff

[linux-yocto] [PATCH 1/5] axxia: PCI Updates for 5600 Hardware

From: John Jacques Signed-off-by: John Jacques --- arch/arm64/boot/dts/intel/axm5616-victoria.dts | 5 drivers/pci/host/pcie-axxia.c | 36 +- 2 files changed, 29 insertions(+), 12 deletions(-) diff

[linux-yocto] [PATCH 0/5] Intel Axxia updates to linux-yocto-4.1

Hello Bruce! This series of patches brings improvements for USB, PCI AND NETWORK drivers and add some features in Victoria board Device Tree. NOTE: All the following patches are for both axxia branches: standard/axxia/base and standard/preempt-rt/axxia/base, Axxia internal tag: 1.33 Thank

[yocto] Toaster fail to luanch bitbake

Hi: After setup toaster I can't finish build progress with bitbake. some ERROR log into : /opt/yocto/poky/build-toaster-4/toaster_ui.log ERROR: can't set event mask: None Is this ERROR come with Environment variant? Thanks. Richard Zhang signature.asc Description:

[yocto] customizing system configuration files in my image

Hello, I would like to customize an image I am developing based on core image minimal. Particularly, I'd like to customize the files /etc/network/interfaces and /etc/inittab . What should I do achieve that? Thank you Ottavio -- [Videotec Logo] Ottavio Campana

Re: [yocto] Per image customizations

In data lunedì 27 giugno 2016 16:11:30, Paul Eggleton ha scritto: > On Mon, 06 Jun 2016 15:27:17 Diego wrote: > > Hi Oleksandr, > > > > In data venerdì 3 giugno 2016 20:56:32, Oleksandr Poznyak ha scritto: > > > I found that that’s an issue with rpm packages. I didn't expect there > > > might > >

Re: [yocto] [meta-raspberrypi] Disable kernel option via fragment Rpi3

Hi Jonathan, Am 25.06.2016 um 06:44 schrieb Jonathan Haws: I've tried adding kernel configuration fragments to disable this option, but with no luck. Kernel config fragments are currently not supported in meta-raspberrypi. There is a patch for this here: