Re: [yocto] Python module and build_ext args

Khem Raj wrote: > On Thu, Aug 24, 2017 at 9:42 PM, Craig McQueen > wrote: > > Khem Raj wrote: > > On Thu, Aug 24, 2017 at 6:48 PM Craig McQueen > > > > wrote: > > > > I wrote: > >> I'm trying to make a recipe for python3-uvloop, using

[linux-yocto] Kernel modules and vermagic

Hi, I am new to this dist-list and I am not sure if this is the right forum. My apologies beforehand if this is not the right list. Problem statement: I am evaluating Yocto for a project. We have a workflow where linux kernel is built from a local git repo separately from the root file

Re: [yocto] Problems running image in qemu (x86)

On 28/08/2017 20:25, Paul Eggleton wrote: On Tuesday, 29 August 2017 12:57:35 AM NZST Alex J Lennon wrote: On 28/08/2017 10:32, Paul Eggleton wrote: On Sunday, 27 August 2017 1:09:49 AM NZST Alex J Lennon wrote: I have just built against master though and am seeing screen corruption. e.g.

[yocto] [meta-mingw][PATCH] Fix Yocto Project compatible errors

Each of the recipes modified fail the YP compatible checking script because they modify the checksum of the package, even when the mingw32 SDK is not enabled. This is corrected by ensuring that each of the settings is only done when the mingw32 override is enabled. The PACKAGECONFIG options are

Re: [yocto] Problems running image in qemu (x86)

On Tuesday, 29 August 2017 12:57:35 AM NZST Alex J Lennon wrote: > On 28/08/2017 10:32, Paul Eggleton wrote: > > On Sunday, 27 August 2017 1:09:49 AM NZST Alex J Lennon wrote: > >> I have just built against master though and am seeing screen corruption. > >> > >> e.g.

Re: [yocto] How can I make it for rpi3

Hi Mohammed, You'd need to set MACHINE to "raspberrypi3" but for that to work I would assume you need to upgrade to current (latest stable at least) versions of all the layers. I don't have a Raspberry Pi 3 board so I can't really advise you further on that side of things. Cheers, Paul PS

[yocto] [meta-security][PATCH 2/2] linux-yocto: add 4.12 bbappends

Signed-off-by: Armin Kuster --- recipes-kernel/linux/linux-yocto-4.12/apparmor.cfg | 13 + recipes-kernel/linux/linux-yocto-4.12/smack-default-lsm.cfg | 2 ++ recipes-kernel/linux/linux-yocto-4.12/smack.cfg | 8

[yocto] [meta-security][PATCH 1/2] tripwire: update to 2.4.3.5

Signed-off-by: Armin Kuster --- .../tripwire/{tripwire_2.4.3.1.bb => tripwire_2.4.3.5.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename recipes-security/tripwire/{tripwire_2.4.3.1.bb => tripwire_2.4.3.5.bb} (96%) diff --git

Re: [yocto] Perforce fetcher ignores module and label

Hi Andrew, Thanks for looking at this. See my recipe below. I've left the bits related to systemd service but I don't think they matter for this. I'm using an old implementation of Perforce (2010) in case this matters. I've tried going back to the old perforce.py fetcher but I get a license

[yocto] Yocto Project Status WW35’17

Current Dev Position: YP 2.4 M3 Next Deadline: YP 2.4 M3 (In QA) SWAT team rotation: Paul -> Todor on Aug. 25, 2017. SWAT team rotation: Todor -> Tracy on Aug. 18, 2017. https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: ·We’ve reached feature

Re: [linux-yocto] [PATCH] common-pc-wifi: fix warning

On 08/28/2017 10:20 AM, Saul Wold wrote: On Mon, 2017-08-28 at 09:18 -0400, Bruce Ashfield wrote: On 08/25/2017 12:53 PM, Saul Wold wrote: This fixes the warning: Config: CONFIG_BRCMFMAC_PROTO_MSGBUF From: .../tmp/work-shared/intel-corei7-64/kernel-source/.kernel-

Re: [yocto] Perforce fetcher ignores module and label

Hi Katu, On 08/28 08:56, Katu Txakur wrote: > 2017-08-11 13:52 GMT+01:00 Andrew Bradford : > On 08/11 11:34, Katu Txakur wrote: > > > 2017-08-07 12:17 GMT+01:00 Andrew Bradford > >: > > > > On 08/02 10:28, Paul Eggleton wrote: > > > > >

Re: [linux-yocto] [kernel-cache][PATCH 0/4] intel-common: networking configuration changes

On 08/28/2017 04:01 AM, Mikko Ylinen wrote: Hi Bruce, On 25/08/17 16:00, Mikko Ylinen wrote: Patches 3 and 4 would need an OK from Saul first. All patches are valid for yocto-4.9+ and 3 also for 4.4. This should say: "All patches are valid for yocto-4.9+ and _4_ also for 4.4. (i.e.,

Re: [linux-yocto] [PATCH] common-pc-wifi: fix warning

On 08/25/2017 12:53 PM, Saul Wold wrote: This fixes the warning: Config: CONFIG_BRCMFMAC_PROTO_MSGBUF From: .../tmp/work-shared/intel-corei7-64/kernel-source/.kernel-meta/configs/standard/intel/bsp/common-pc/common-pc-wifi.cfg Requested value: CONFIG_BRCMFMAC_PROTO_MSGBUF=y Actual value:

Re: [yocto] Problems running image in qemu (x86)

On 28/08/2017 10:32, Paul Eggleton wrote: > Hi Alex, > > On Sunday, 27 August 2017 1:09:49 AM NZST Alex J Lennon wrote: >> I'm bringing the Mono build up to date in the meta-mono layer and ran >> into a problem with my testing. >> >> I generally target QEMU, e.g. qemux86, build a core-image-sato

Re: [linux-yocto] [Resend v4.12 PATCH 1/2] fs: yaffs2: replace CURRENT_TIME by other appropriate apis

On 08/27/2017 10:53 PM, Kevin Hao wrote: The macro CURRENT_TIME has already been deleted by commit bfe1c566453a ("time: delete CURRENT_TIME_SEC and CURRENT_TIME"). So we need to replace all the uses of CURRENT_TIME by current_time() for filesystem times, and ktime_get_* function for others.

[yocto] iMX6UL dtsi SAI1

Hi there, I'm developing a device based on iMX6UL and I need to enabled SAI1 with MCLK as output (generated internally). I define SAI1 and iomuxc as follows above and I can see in .../pinctrl-maps file that those pins have been asigned to SAI1. But I can't get this signals in the

Re: [yocto] Problems running image in qemu (x86)

Hi Alex, On Sunday, 27 August 2017 1:09:49 AM NZST Alex J Lennon wrote: > I'm bringing the Mono build up to date in the meta-mono layer and ran > into a problem with my testing. > > I generally target QEMU, e.g. qemux86, build a core-image-sato based > Mono test image and run up with 'runqemu

Re: [yocto] do_fetch error

Hi Mohammed, On Monday, 28 August 2017 8:41:51 PM NZST mohammed aqdam wrote: > I was build image for rpi3 using yocto, but the image which i build > was not supporting camera(picamera),so after googling for a while i found > this link > >

[yocto] do_fetch error

Hello there, I was build image for rpi3 using yocto, but the image which i build was not supporting camera(picamera),so after googling for a while i found this link https://github.com/pauldotknopf/raspberry-pi-camera-source now while building, i'm getting the following message...

Re: [linux-yocto] [kernel-cache][PATCH 0/4] intel-common: networking configuration changes

Hi Bruce, On 25/08/17 16:00, Mikko Ylinen wrote: Patches 3 and 4 would need an OK from Saul first. All patches are valid for yocto-4.9+ and 3 also for 4.4. This should say: "All patches are valid for yocto-4.9+ and _4_ also for 4.4. (i.e., intel-common: disable ixgbe modules) -- Mikko

Re: [yocto] Perforce fetcher ignores module and label

Hi Andrew Thanks for your reply and sorry for the delay on this. I was on holidays too. 2017-08-11 13:52 GMT+01:00 Andrew Bradford : > Hi Katu, > > I added back the yocto ml on CC, could you please keep this conversation > on-list? > > Sure, sorry about that. On