Re: [linux-yocto] [PATCH] intel-x86-32: Set CONFIG_NR_CPUS to 64 explicitly

2018-11-13 Thread Bruce Ashfield
On 2018-11-12 9:27 p.m., Hongzhi.Song wrote: Since 'CONFIG_NR_CPUS=256' was moved to intel-x86-64.cfg, seeing commit [11917e28727], we would better explicitly set CONFIG_NR_CPUS to 64 in intel-x86-32.cfg for a future re-org of the fragments. And the '64' is also the default value for

Re: [yocto] m4-native, zedboard, "Please port gnulib fseeko.c to your platform"

2018-11-13 Thread akuster808
Robert, On 11/13/18 12:28 PM, Robert P. J. Day wrote: > been away from YP for a few months, diving back in, want to build a > core-image-minimal for my zedboard, and i will first admit that i'm > using a non-approved distro (fully-updated fedora 29): > > "WARNING: Host distribution "fedora-29"

[yocto] m4-native, zedboard, "Please port gnulib fseeko.c to your platform"

2018-11-13 Thread Robert P. J. Day
been away from YP for a few months, diving back in, want to build a core-image-minimal for my zedboard, and i will first admit that i'm using a non-approved distro (fully-updated fedora 29): "WARNING: Host distribution "fedora-29" has not been validated with this version of the build system;

Re: [yocto] [OE-core] Yocto Project Status WW46’18

2018-11-13 Thread Richard Purdie
On Tue, 2018-11-13 at 19:59 +, Peter Kjellerstedt wrote: > From the updates below: > > Patches for the thud point release are queuing on the branch. > > On what branch? The thud-next branch is behind the thud branch, and > the master-next branch contains a lot of recipe updates that do

Re: [yocto] Yocto Project Status WW46’18

2018-11-13 Thread Peter Kjellerstedt
>From the updates below: * Patches for the thud point release are queuing on the branch. On what branch? The thud-next branch is behind the thud branch, and the master-next branch contains a lot of recipe updates that do not seem suitable for Thud. //Peter From:

Re: [yocto] wic creates invalid image

2018-11-13 Thread Dimitris Tassopoulos
Hi Alex, If you don't want the extended partitions you need to create a gpt partition, you can do this by adding this to your wks file. bootloader --ptable gpt Regards, Dimitris On Tue, 13 Nov 2018, 20:23 Alex Kiernan On Tue, Nov 13, 2018 at 7:13 PM Donal Morrissey > wrote: > > > > Hi

Re: [yocto] wic creates invalid image

2018-11-13 Thread Alex Kiernan
On Tue, Nov 13, 2018 at 7:13 PM Donal Morrissey wrote: > > Hi There, > I have a problem with an image being created by wic. If I add more than 4 > partition definitions to the wks file, the generated image will include an > additional partition with no Fstype, and spanning the full length of

[yocto] wic creates invalid image

2018-11-13 Thread Donal Morrissey
Hi There, I have a problem with an image being created by wic. If I add more than 4 partition definitions to the wks file, the generated image will include an additional partition with no Fstype, and spanning the full length of the additional partitions. Take the following wks file: part

[yocto] Invitation: Yocto Project Technical Team Meeting @ Monthly from 8am to 9am on the fourth Tuesday (PST) (yocto@yoctoproject.org)

2018-11-13 Thread theyoctoproject
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Los_Angeles X-LIC-LOCATION:America/Los_Angeles BEGIN:DAYLIGHT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT DTSTART:19700308T02

[yocto] Yocto Project Status WW46’18

2018-11-13 Thread Jolley, Stephen K
Current Dev Position: YP 2.6 M4 is in preparing for release. Next Deadline: YP 2.6 M4 Release Target was Oct. 26, 2018 SWAT Team Rotation: · SWAT lead is currently: Armin · SWAT team rotation: Armin -> Paul on Nov. 16, 2018 · SWAT team rotation: Paul -> Ross on Nov.

Re: [yocto] yocto x64-linux with bootia32.efi

2018-11-13 Thread Knoppix
By the way I hope someone will fix this. On Tue, Nov 13, 2018 at 5:38 PM Knoppix wrote: > Thanks a lot.  > > > On Tue, Nov 13, 2018 at 10:42 AM Dimitris Tassopoulos > wrote: > >> That's great news! >> Glad to help. It's frustrating some times, but I hope that also someone >> else may come

Re: [yocto] yocto x64-linux with bootia32.efi

2018-11-13 Thread Knoppix
Thanks a lot.  On Tue, Nov 13, 2018 at 10:42 AM Dimitris Tassopoulos wrote: > That's great news! > Glad to help. It's frustrating some times, but I hope that also someone > else may come with a better solution. > > Regarding secureboot, I guess that if you use the same keys, then there >

Re: [yocto] meta-mingw: unable to run executables on Windows

2018-11-13 Thread Samuli Piippo
On Tue, 13 Nov 2018 at 12:17, Burton, Ross wrote: > > On Tue, 13 Nov 2018 at 09:57, Samuli Piippo wrote: > > I've just upgraded poky and meta-mingw layers from sumo to thud and as a > > result a lot of the executables in the toolchain no longer run correctly on > > Windows. > > > > I've built

Re: [yocto] Set linux capabilities on binary on a recipe in meta-oe layer

2018-11-13 Thread Uwe Geuder
On Mon, Nov 12, 2018 at 3:09 PM Markus W markus4dev-at-gmail.com wrote: > > Thanks Uwe! > > I tried the global approach by adding the following to my local.conf file: > > ROOTFS_POSTPROCESS_COMMAND += "my_setcap_function" > > my_setcap_function() { > setcap cap_net_raw+eip

Re: [linux-yocto] [PATCH] of: Fix of_populate_phandle_cache compilation error

2018-11-13 Thread Bruce Ashfield
On 2018-11-12 10:45 p.m., He Zhe wrote: On 2018/11/13 04:17, Bruce Ashfield wrote: On 2018-11-12 4:49 a.m., He Zhe wrote: On 2018/11/6 00:05, Bruce Ashfield wrote: On 11/2/18 4:42 AM, He Zhe wrote: When merging tag 'v4.18.10' into v4.18/standard/base, 05a9931 "of: fix phandle cache

[yocto] lib32-glibc headers populated instead glibc headers in the SDK toolchain - yocto 2.2.2

2018-11-13 Thread ravi chandran
Hi all, I am working in one project where both lib32 & lib64 need to be supported. Hence, lib32-glibc & glibc both are there in yocto build. In the final toolchain, after running "bitbake -c populate-sdk", it is randomly, lib32-glibc headers are getting populated instead of glibc headers. Ex:

Re: [yocto] meta-mingw: unable to run executables on Windows

2018-11-13 Thread Burton, Ross
On Tue, 13 Nov 2018 at 09:57, Samuli Piippo wrote: > I've just upgraded poky and meta-mingw layers from sumo to thud and as a > result a lot of the executables in the toolchain no longer run correctly on > Windows. > > I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From that, gcc/g++

[yocto] meta-mingw: unable to run executables on Windows

2018-11-13 Thread Samuli Piippo
Hi, I've just upgraded poky and meta-mingw layers from sumo to thud and as a result a lot of the executables in the toolchain no longer run correctly on Windows. I've built meta-toolchain for SDKMACHINE=x86_64-mingw32. From that, gcc/g++ work fine on Windows 10, but ar, as, objdumb, and others

Re: [yocto] [meta-intel] fb: switching to inteldrmfb from efi vga

2018-11-13 Thread Mittal, Anuj
On Tue, 2018-11-13 at 12:30 +0300, Knoppix wrote: > yocto and meta-intel: 2.5.1/sumo > kernel=linux-yocto-4.15.18 > machine=intel-corei7-64 > distro=poky > > the problem is: > when I boot the system it comes to this message and frozees: " fb: > switching to amdgpudrmfb from efi vga" This error

[yocto] fb: switching to inteldrmfb from efi vga

2018-11-13 Thread Knoppix
yocto and meta-intel: 2.5.1/sumo kernel=linux-yocto-4.15.18 machine=intel-corei7-64 distro=poky the problem is: when I boot the system it comes to this message and frozees: " fb: switching to amdgpudrmfb from efi vga" I searched a lot, there is a workaround to solve problem (add nomodeset to

[linux-yocto] [PATCH] kmemleak: Turn kmemleak_lock to raw spinlock on RT

2018-11-13 Thread zhe.he
From: He Zhe See https://lore.kernel.org/patchwork/patch/1011368/ for upstream status. kmemleak_lock, as a rwlock on RT, can possibly be held in atomic context and causes the follow BUG. BUG: scheduling while atomic: migration/15/132/0x0002 Modules linked in: iTCO_wdt iTCO_vendor_support

[yocto] Building multiple U-Boot binaries (with different patch sets)

2018-11-13 Thread Andrei Faur
Hello, My scenario is the following: I have two sets of U-Boot patches and I want to create two separate images, each one containing a U-Boot built with one of the patch sets. Everything else in the two images (kernel, rootfs) is the same. I am using Yocto Rocko. Searching this list and various