Re: [linux-yocto] [linux-yocto-dev standard/xlnx-soc][PATCH 0/1] export the maximum and minimum voltage and temperature to userspace

Hi Michal, On 7/28/20 1:20 PM, Michal Simek wrote: On 27. 07. 20 10:53, quanyang.w...@windriver.com wrote: From: Quanyang Wang Hi Bruce and Michal, One of our customers want to use more xadc sysfs interfaces, so export the maximum and minimum voltage and temperature to userspace. Would

[yocto] OpenEmbedded Happy Hour July 29 9pm/2100 UTC

Just a reminder about our upcoming OpenEmbedded Happy Hour on July 29 for Oceania/Asia timezones @ 2100/9pm UTC (5pm EDT): https://www.openembedded.org/wiki/Calendar https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+July+29=20200729T21 -- Denys

[yocto] Yocto Technical Team Minutes, Engineering Sync, for July 28 2020

Yocto Technical Team Minutes, Engineering Sync, for July 28 2020 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are made to ensure the below is accurate and valid. However, errors sometimes happen. If any errors or

Re: [yocto] [prelink-cross] prelink-cross: Add SPDX-License-Identifier: GPL-2.0-or-later to source files

On 2020-07-21 10:14 a.m., Sathish V wrote: Signed-off-by: Sathish V --- gelf/gelf.c| 4 +++- gelf/gelf.h| 4 +++- gelfx/gelfx.h | 4 +++-n ... Thanks Sathish! Mark, did you miss this email? -- # Randy MacLeod # Wind River Linux -=-=-=-=-=-=-=-=-=-=-=- Links: You

Re: [yocto] How to enable preempt-rt in Yocto Zeus or Warrior?

Hello Scott, What I wanted to say here is that you do not change anything while building a YOCTO load. You'll get all the components in: .../tmp/deploy/images/$(PLATFORM) , namely: XYZ,rootfs.cpio.zx U-Boot zImage modules But you can build a rt-kernel very conventionally, using out of YOCTO

Re: [linux-yocto]: [kernel v5.4/standard/bcm-2xxx-rpi]: drivers: staging: vc04_services: remove the static keyword

In message: [linux-yocto]: [kernel v5.4/standard/bcm-2xxx-rpi]: drivers: staging: vc04_services: remove the static keyword on 28/07/2020 meng...@windriver.com wrote: > From: Limeng > > Hi Bruce, > > There are 3 kernel modules(bcm2835_v4l2, bcm2835_codec, > bcm2835_isp) to invoke finction

Re: [yocto] How to enable preempt-rt in Yocto Zeus or Warrior?

On Tue, Jul 28, 2020 at 10:26 AM Scott Whitney wrote: > Hi Bruce, > > > > I believe the recipe for building Variscite’s kernel is in > meta-variscite-imx/recipes-kernel/linux/linux-variscite_4.19.35.bb, which > does produce a booting U-Boot and Linux image. What would need to be > modified to

Re: [yocto] How to enable preempt-rt in Yocto Zeus or Warrior?

Hi Bruce, I believe the recipe for building Variscite’s kernel is in meta-variscite-imx/recipes-kernel/linux/linux-variscite_4.19.35.bb, which does produce a booting U-Boot and Linux image. What would need to be modified to enable the rt-linux kernel? The recipe is provided below. #

Re: [yocto] How to enable preempt-rt in Yocto Zeus or Warrior?

Hi Zoran, Thank you for responding. I confess I am still new to building Linux with Yocto, so some of your steps may seem obvious, but are a bit confusing to a 'newbie'. I am using normal Yocto instruction provided by Variscite to build our rootfs, U-Boot, and kernel. However, I am not

Re: [yocto] How to enable preempt-rt in Yocto Zeus or Warrior?

On Tue, Jul 28, 2020 at 8:45 AM Scott Whitney wrote: > Hi Bruce, > > > > Yes, we are using Linux built by Yocto, but where is the preferred > provider for the kernel set to linux-yocto-rt? > > > This is one of the nuances about OE/Yocto, it isn't about building the kernel with yocto, I was

Re: [yocto] How to enable preempt-rt in Yocto Zeus or Warrior?

Hello Scott, I have a bit of a different idea about the whole YOCTO process. Let me suggest something else, actually a hybrid combination of the YOCTO build system. You can do the whole process of YOCTO, but why do you not use components out of the YOCTO building process? For example, you can

Re: [yocto] How to enable preempt-rt in Yocto Zeus or Warrior?

Hi Bruce, Yes, we are using Linux built by Yocto, but where is the preferred provider for the kernel set to linux-yocto-rt? Thanks for your help Scott D. Whitney [cid:image003.png@01D664BB.52107300] s...@inea.com| T: 781-801-1152| F: 781-801-1108|

[yocto] Building extensible SDK

The eSDK looks interesting, but the documentation does not say anything about how to build it. Am I missing something about how to obtain the eSDK? Regards Kjeld Flarup DEIF R - Platform Software From: Khem Raj Sent: Friday, July 10, 2020 02:38 To:

[linux-yocto]: [kernel v5.4/standard/bcm-2xxx-rpi]: drivers: staging: vc04_services: remove the static keyword

From: Limeng Hi Bruce, There are 3 kernel modules(bcm2835_v4l2, bcm2835_codec, bcm2835_isp) to invoke finction vchiq_mmal_init(). In this function, there is static pointer variable vchi_instance pointing a region of memory. Because the 3 kernel modules are loaded without dependency, there is no

[linux-yocto] [PATCH] drivers: staging: vc04_services: remove the static keyword

From: Limeng There are 3 kernel modules(bcm2835_v4l2, bcm2835_codec, bcm2835_isp) to invoke finction vchiq_mmal_init(). In this function, there is static pointer variable vchi_instance pointing a region of memory. Because the 3 kernel modules are loaded without dependency, there is no fixed

[linux-yocto] [PATCH] drivers: staging: vc04_services: remove the useless static keyword

From: Limeng There are 3 kernel modules(bcm2835_v4l2, bcm2835_codec, bcm2835_isp) to invoke finction vchiq_mmal_init(). In this function, there is static pointer variable vchi_instance pointing a region of memory. Because the 3 kernel modules are loaded without dependency, there is no fixed

[linux-yocto] [linux-yocto-dev]: [kernel standard/bcm-2xxx-rpi]: drivers: staging: vc04_services: remove the useless static keyword

From: Limeng Hi Bruce, There are 3 kernel modules(bcm2835_v4l2, bcm2835_codec, bcm2835_isp) to invoke finction vchiq_mmal_init(). In this function, there is static pointer variable vchi_instance pointing a region of memory. Because the 3 kernel modules are loaded without dependency, there is no

[yocto] [meta-selinux][PATCH 2/2] net-tools: drop patch

The netstat-selinux-support.patch has been merged upstream. So drop it. Signed-off-by: Yi Zhao --- .../files/netstat-selinux-support.patch | 244 -- .../net-tools/net-tools_selinux.inc | 4 - 2 files changed, 248 deletions(-) delete mode 100644

[yocto] [meta-selinux][PATCH 1/2] selinux-*.bb: fix typos

Fixes: ${PN}_RDEPENDS -> RDEPENDS_${PN} Signed-off-by: Yi Zhao --- recipes-security/selinux/selinux-autorelabel_0.1.bb | 2 +- recipes-security/selinux/selinux-init_0.1.bb| 2 +- recipes-security/selinux/selinux-labeldev_0.1.bb| 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)

Re: [yocto] Remove connman package from yocto sdk.

Hi, On Tue, Jul 28, 2020 at 09:02:45AM +0200, Josef Holzmayr-Khosh Amoz wrote: > Howdy! > > Am Di., 28. Juli 2020 um 07:19 Uhr schrieb NIKHIL PATIL > : > > > > hi, > > Still we ar facing same issue , > > If anyone know, please help. > > > > On Fri, Jul 24, 2020 at 6:14 PM NIKHIL PATIL

Re: [yocto] Remove connman package from yocto sdk.

Howdy! Am Di., 28. Juli 2020 um 07:19 Uhr schrieb NIKHIL PATIL : > > hi, > Still we ar facing same issue , > If anyone know, please help. > > On Fri, Jul 24, 2020 at 6:14 PM NIKHIL PATIL wrote: >> >> Hi team, >> We want to use NetworkManager to access internet using LTE module >>

Re: [yocto] #toolchain #yocto #devtool #linux

Howdy! Am Di., 28. Juli 2020 um 07:09 Uhr schrieb : > > Hi, > I am trying to build a yocto demo-coreip-cli image for my custom RISC-V SOC > which only supports imafd instructions. For the compilation of cross > toolchain that is used by Bitbake, I tried changing cross-binutils.inc recipe > and

Re: [yocto] [meta-java] icedtea7-native fails to build with error: cc1plus: all warnings being treated as errors

Hi Robert, Thanks for the tip, it seems to have worked and I've gotten past the compilation step. Unfortunately, now the build seems to be failing the do_package_rpm task with the following error: Exception: bb.process.ExecutionError: Execution of