[yocto] [meta-virtualization][PATCH] libvirt: remove qemu from PACKAGECONFIG for mips n32 and n64

[kai.kang]

From: Kai Kang 

PACKAGECONFIG 'qemu' causes libvirt depends on package qemu. But qemu
is not compatible with mips n32 and n64. So remove 'qemu' from
PACKAGECONFIG for mips n32 and n64.

Signed-off-by: Kai Kang 
Signed-off-by: Mark Hatle 
---
 recipes-extended/libvirt/libvirt_4.7.0.bb | 4 
 1 file changed, 4 insertions(+)

diff --git a/recipes-extended/libvirt/libvirt_4.7.0.bb 
b/recipes-extended/libvirt/libvirt_4.7.0.bb
index 47275ae..a1175f5 100644
--- a/recipes-extended/libvirt/libvirt_4.7.0.bb
+++ b/recipes-extended/libvirt/libvirt_4.7.0.bb
@@ -186,6 +186,10 @@ PACKAGECONFIG ??= "qemu yajl uml openvz vmware vbox esx 
iproute2 lxc test \
${@bb.utils.contains('DISTRO_FEATURES', 'x11', 'polkit', 
'', d)} \
   "
 
+# qemu is NOT compatible with mips64
+PACKAGECONFIG_remove_mipsarchn32 = "qemu"
+PACKAGECONFIG_remove_mipsarchn64 = "qemu"
+
 # enable,disable,depends,rdepends
 #
 PACKAGECONFIG[qemu] = "--with-qemu,--without-qemu,qemu,"
-- 
2.19.0.rc2

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] YP 2.7 Planning

[Jolley, Stephen K]

No, that will be suggested and hopefully agreed on in the 11/6 Technical 
meeting, as well as the exact milestone dates.

Stephen

From: akuster808 [mailto:akuster...@gmail.com]
Sent: Monday, October 15, 2018 8:22 AM
To: Jolley, Stephen K ; yocto@yoctoproject.org; 
openembedded-c...@lists.openembedded.org
Subject: Re: [OE-core] YP 2.7 Planning


Stephen,

On 10/15/2018 08:05 AM, Jolley, Stephen K wrote:
All,

We have begun planning for YP 2.7.   In prior versions, items that we didn't 
have the bandwidth to do were assigned the target milestone of 2.99.  Since YP 
2.7 planning has just begun, I would like each of you to review the bugs and 
enhancements in YP 2.99 and determine if you will have the bandwidth to own any 
of them in YP 2.7.

Do we have the feature freeze date defined yet?

- armin


In addition to reviewing the bugs under your name, also review any under the 
unassigned name to see if you have both an interest and the time to own any of 
those in YP 2.7.

Link for bugs in YP 2.99 by owner: 
https://wiki.yoctoproject.org/wiki/Bug_Triage#2.99_Bugs_by_Owner
Link for enhancements in YP 2.99 by owner: 
https://wiki.yoctoproject.org/wiki/Bug_Triage#2.99_Enhancements_by_Owner

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*Cell:(208) 244-4460
* Email: 
stephen.k.jol...@intel.com




-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [Yocto][poky][meta] already-stripped ignore if set for any other package then INSANE_SKIP_${PN}

[Burton, Ross]

Ah yes, of course.  Stripping happens *before* package splitting, so
it doesn't make sense to have it set on PN-package1.  Just set it on
PN and it should work.

Ross
On Mon, 15 Oct 2018 at 08:18, Måns Zigher  wrote:
>
> Hi,
>
> Sorry I see now that there is a typo. What I mean is that in the default 
> package I am not suing INSANE_SKIP but for packag1 I need already-stripped
>
> INSANE_SKIP_${PN}-package1 = " \
> dev-so \
> already-stripped \
> "
>
> But I continuously get the error that they are already-stripped. So is it 
> supposed to work because I don't understand  the code in the package.bbclass 
> since it looks like it is only checking for already-stripped in ${PN} and not 
> ${PN}-package1?
>
> BR
> Måns Zigher
>
>
>
> Den fre 12 okt. 2018 kl 16:30 skrev Burton, Ross :
>>
>> On Thu, 11 Oct 2018 at 18:14, Måns Zigher  wrote:
>> > I have been struggling with a problem where I need to create a package in 
>> > a recipe and set already-stripped for that package. The package in 
>> > question is not the the default one so I am trying to set it by using
>> >
>> > INSANE_SKIP_${PN} += " \
>> > dev-so \
>> > already-stripped \
>> > "
>>
>> You say no the default one, but PN is "the default" one, so that's
>> probably why that doesn't work.
>>
>> Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] permissions when installing scripts

[Bas Mevissen]

cp --preserve=mode might prevent that.
However, I'm wondering why the +x gets lost in the first place. Normal 
GNU copy seems to copy that flag by default. Even when doing it as root 
using sudo.


Aren't we looking in the wrong place for the executable bit(s) to fall 
off?


-- Bas.


On 2018-10-15 20:53, Burton, Ross wrote:

cp -a will preserve ownership, which you don't want.

Ross
On Mon, 15 Oct 2018 at 19:45, Bas Mevissen  
wrote:




cp -a or --preserve(=) optionally combined with other 
options

does the trick. However, using install is the better solution.


-- Bas.

On 2018-10-15 14:35, Burton, Ross wrote:
> As you've discovered, cp doesn't preserve permissions.  Using install
> -m755 is the idiom.
>
> Ross
> On Mon, 15 Oct 2018 at 11:12, Belisko Marek 
> wrote:
>>
>> Hi,
>>
>> I have package which contains bunch of scripts (with +x flag for
>> user). When installed in do_install method (simply by copying them to
>> destination) they loose +x flag. I know copying directly is not best
>> approach but there exists better way how to keep scripts permissions
>> like in repo (except calling install -m 755 for all of them)? Thanks.
>>
>> BR,
>>
>> marek
>>
>> --
>> as simple and primitive as possible
>> -
>> Marek Belisko - OPEN-NANDRA
>> Freelance Developer
>>
>> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
>> Tel: +421 915 052 184
>> skype: marekwhite
>> twitter: #opennandra
>> web: http://open-nandra.com
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] permissions when installing scripts

[Belisko Marek]

Hi Bas,

On Mon, Oct 15, 2018 at 8:45 PM Bas Mevissen  wrote:
>
>
>
> cp -a or --preserve(=) optionally combined with other options
> does the trick. However, using install is the better solution.
But -p will keep current user and not root used when installed in
final rootfs (also QA report warnings about host contamination).
I think I'll stick with install ;). Thanks.
>
>
> -- Bas.
>
> On 2018-10-15 14:35, Burton, Ross wrote:
> > As you've discovered, cp doesn't preserve permissions.  Using install
> > -m755 is the idiom.
> >
> > Ross
> > On Mon, 15 Oct 2018 at 11:12, Belisko Marek 
> > wrote:
> >>
> >> Hi,
> >>
> >> I have package which contains bunch of scripts (with +x flag for
> >> user). When installed in do_install method (simply by copying them to
> >> destination) they loose +x flag. I know copying directly is not best
> >> approach but there exists better way how to keep scripts permissions
> >> like in repo (except calling install -m 755 for all of them)? Thanks.
> >>
> >> BR,
> >>
> >> marek
> >>
> >> --
> >> as simple and primitive as possible
> >> -
> >> Marek Belisko - OPEN-NANDRA
> >> Freelance Developer
> >>
> >> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
> >> Tel: +421 915 052 184
> >> skype: marekwhite
> >> twitter: #opennandra
> >> web: http://open-nandra.com
> >> --
> >> ___
> >> yocto mailing list
> >> yocto@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/yocto
>

BR,

marek

-- 
as simple and primitive as possible
-
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] permissions when installing scripts

[Burton, Ross]

cp -a will preserve ownership, which you don't want.

Ross
On Mon, 15 Oct 2018 at 19:45, Bas Mevissen  wrote:
>
>
>
> cp -a or --preserve(=) optionally combined with other options
> does the trick. However, using install is the better solution.
>
>
> -- Bas.
>
> On 2018-10-15 14:35, Burton, Ross wrote:
> > As you've discovered, cp doesn't preserve permissions.  Using install
> > -m755 is the idiom.
> >
> > Ross
> > On Mon, 15 Oct 2018 at 11:12, Belisko Marek 
> > wrote:
> >>
> >> Hi,
> >>
> >> I have package which contains bunch of scripts (with +x flag for
> >> user). When installed in do_install method (simply by copying them to
> >> destination) they loose +x flag. I know copying directly is not best
> >> approach but there exists better way how to keep scripts permissions
> >> like in repo (except calling install -m 755 for all of them)? Thanks.
> >>
> >> BR,
> >>
> >> marek
> >>
> >> --
> >> as simple and primitive as possible
> >> -
> >> Marek Belisko - OPEN-NANDRA
> >> Freelance Developer
> >>
> >> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
> >> Tel: +421 915 052 184
> >> skype: marekwhite
> >> twitter: #opennandra
> >> web: http://open-nandra.com
> >> --
> >> ___
> >> yocto mailing list
> >> yocto@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] permissions when installing scripts

[Bas Mevissen]

cp -a or --preserve(=) optionally combined with other options 
does the trick. However, using install is the better solution.



-- Bas.

On 2018-10-15 14:35, Burton, Ross wrote:

As you've discovered, cp doesn't preserve permissions.  Using install
-m755 is the idiom.

Ross
On Mon, 15 Oct 2018 at 11:12, Belisko Marek  
wrote:


Hi,

I have package which contains bunch of scripts (with +x flag for
user). When installed in do_install method (simply by copying them to
destination) they loose +x flag. I know copying directly is not best
approach but there exists better way how to keep scripts permissions
like in repo (except calling install -m 755 for all of them)? Thanks.

BR,

marek

--
as simple and primitive as possible
-
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Add python2 as native package in openembedded sdk

[Burton, Ross]

Add nativesdk-python-core and nativesdk-python-modules to
TOOLCHAIN_HOST_TASK (using _append).

Ross
On Mon, 15 Oct 2018 at 17:30, Alberto Eusebi  wrote:
>
> Hello,
> I need to cross compile python2 packages using openembedded sdk. The sdk
> resulting package contains only python 3.5.3 (in older version it contains
> python 2.7.3 as well).
>   
> _
>   # ls -l sysroots/x86_64-angstromsdk-linux/usr/bin/python*
> lrwxrwxrwx 1 root root9 Oct 11 21:39 python3 -> python3.5*
> -rwxr-xr-x 1 root root  267 Oct 11 21:39 python3.5*
> lrwxrwxrwx 1 root root   17 Oct 11 21:39 python3.5-config -> 
> python3.5m-config*
> -rwxr-xr-x 2 root root  15K Oct 11 21:39 python3.5m*
> -rwxr-xr-x 1 root root 3.3K Oct 11 21:39 python3.5m-config*
> -rwxr-xr-x 2 root root  15K Oct 11 21:39 python3.5.real*
> lrwxrwxrwx 1 root root   16 Oct 11 21:39 python3-config -> 
> python3.5-config*__
>   
> _
>
>
> Is there a way to add also this native python version to my sdk?
>
> Thanks.
>
> --
> Albeus
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] populate_sdk fails when multilib enabled

[Mohammad, Jamal M]

Hi Guys,

I am having customized Apollo Lake Board.

Using generic meta-intel layer with MACHINE=intel-corei7-64, Branch = sumo

We wanted to support 32-bit libraries, so added multilib in local.conf

require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"


IMAGE_INSTALL_append = " openssh dpkg gnutls lib32-glibc lib32-libgcc 
lib32-libstdc++ lib32-gnutls lib32-freetype lib32-libx11 lib32-ncurses 
lib32-dpkg lsof cronie logrotate lib32-libxml2 screen mg eudev libudev s"
EXTRA_IMAGE_FEATURES ?= " ssh-server-openssh debug-tweaks tools-debug "

When I ran the following command: bitbake -c populate_sdk core-image-minimal, 
it fails with the following..


Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
lib32-packagegroup-core-standalone-sdk-target : Depends: 
lib32-glibc-gconv-cp1252 but it is not installable
 Depends: 
lib32-glibc-gconv-ibm850 but it is not installable
 Depends: 
lib32-glibc-gconv-iso8859-1 but it is not installable
 Depends: 
lib32-glibc-gconv-iso8859-15 but it is not installable
 Depends: 
lib32-glibc-localedata-i18n but it is not installable
 Depends: lib32-libatomic-dev 
but it is not installable
 Depends: lib32-libatomic1 but 
it is not installable
 Depends: lib32-libc6 but it is 
not installable
 Depends: lib32-libc6-dbg but 
it is not installable
 Depends: lib32-libc6-dev but 
it is not installable
 Depends: lib32-libc6-thread-db 
but it is not installable
 Depends: lib32-libc6-utils but 
it is not installable
 Depends: lib32-libgcc-s-dev 
but it is not installable
 Depends: lib32-libgcc1 but it 
is not installable
 Depends: lib32-libsegfault but 
it is not installable
 Depends: lib32-libstdc++-dev 
but it is not installable
 Depends: lib32-libstdc++6 but 
it is not installable
 Recommends: lib32-libssp-dev 
but it is not installable
 Recommends: lib32-libssp0 but 
it is not installable
E: Unable to correct problems, you have held broken packages.

Please help me in resolving this problem.. Appreciate your efforts and time.

Thanks and Regards,
Jamal
NCR Corporation

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Add python2 as native package in openembedded sdk

[Alberto Eusebi]

Hello,
I need to cross compile python2 packages using openembedded sdk. The sdk
resulting package contains only python 3.5.3 (in older version it contains
python 2.7.3 as well).
  
_
  # ls -l sysroots/x86_64-angstromsdk-linux/usr/bin/python*
lrwxrwxrwx 1 root root9 Oct 11 21:39 python3 -> python3.5*
-rwxr-xr-x 1 root root  267 Oct 11 21:39 python3.5*
lrwxrwxrwx 1 root root   17 Oct 11 21:39 python3.5-config -> 
python3.5m-config*
-rwxr-xr-x 2 root root  15K Oct 11 21:39 python3.5m*
-rwxr-xr-x 1 root root 3.3K Oct 11 21:39 python3.5m-config*
-rwxr-xr-x 2 root root  15K Oct 11 21:39 python3.5.real*
lrwxrwxrwx 1 root root   16 Oct 11 21:39 python3-config -> 
python3.5-config*__
  
_


Is there a way to add also this native python version to my sdk?

Thanks.

--
Albeus
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] YP 2.7 Planning

[akuster808]

Stephen,


On 10/15/2018 08:05 AM, Jolley, Stephen K wrote:
>
> All,
>
>  
>
> We have begun planning for YP 2.7.   In prior versions, items that we
> didn’t have the bandwidth to do were assigned the target milestone of
> 2.99.  Since YP 2.7 planning has just begun, I would like each of you
> to review the bugs and enhancements in YP 2.99 and determine if you
> will have the bandwidth to own any of them in YP 2.7.
>

Do we have the feature freeze date defined yet?

- armin
>
>  
>
> In addition to reviewing the bugs under your name, also review any
> under the unassigned name to see if you have both an interest and the
> time to own any of those in YP 2.7.
>
>  
>
> Link for bugs in YP 2.99 by owner:
> https://wiki.yoctoproject.org/wiki/Bug_Triage#2.99_Bugs_by_Owner
>
> Link for enhancements in YP 2.99 by owner:
> https://wiki.yoctoproject.org/wiki/Bug_Triage#2.99_Enhancements_by_Owner
>
>  
>
> Thanks,
>
>  
>
> */Stephen K. Jolley/**//*
>
> *Yocto Project Program Manager*
>
> *INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124 *
>
> (    *Cell*:    (208) 244-4460
>
> * *Email*: _stephen.k.jolley@intel.com_
>
>  
>
>
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] YP 2.7 Planning

[Jolley, Stephen K]

All,

We have begun planning for YP 2.7.   In prior versions, items that we didn't 
have the bandwidth to do were assigned the target milestone of 2.99.  Since YP 
2.7 planning has just begun, I would like each of you to review the bugs and 
enhancements in YP 2.99 and determine if you will have the bandwidth to own any 
of them in YP 2.7.

In addition to reviewing the bugs under your name, also review any under the 
unassigned name to see if you have both an interest and the time to own any of 
those in YP 2.7.

Link for bugs in YP 2.99 by owner: 
https://wiki.yoctoproject.org/wiki/Bug_Triage#2.99_Bugs_by_Owner
Link for enhancements in YP 2.99 by owner: 
https://wiki.yoctoproject.org/wiki/Bug_Triage#2.99_Enhancements_by_Owner

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Unassigned Bugs - Help Needed

[Jolley, Stephen K]

All,



The triage team meets weekly and does its best to handle the bugs reported into 
the bugzilla. The number of people attending that meeting has fallen, as have 
the number of people available to help fix bugs. One of the things we hear 
users report is they don't know how to help. We (the triage team) are therefore 
going to start reporting out the currently 303 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out 
with these.



Bugs are split into two types, "true bugs" where things don't work as they 
should and "enhancements" which are features we'd want to add to the system.



There are also roughly five different "priority" classes right now, "2.6", 
"2.7", "2.8", "2.99" and "Future", the more pressing/urgent issues being in 
"2.6" and then "2.7".



Please review this link and if a bug is something you would be able to help 
with either take ownership of the bug, or send me 
(stephen.k.jol...@intel.com) an e-mail with 
the bug number you would like and I will assign it to you (please make sure you 
have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [linux-yocto] : [yocto-4.18]: intel-socfpga: kernel patches

[Bruce Ashfield]

On 10/12/2018 07:03 PM, Li, Meng wrote:

Hi Bruce,

My pull request have been at the end of this email thread.
The head part of pull request as below.
I push these patches into https://github.com/limeng-linux/linux-yocto-4.18.git, 
on branch v4.18/standard/intel-socfpga. A public repo.
Can you access them?
Or I need to send pull request with other style?

  The following changes since commit 0cdc8564c61958a39704d97e008120bd7c762f60:
  
 Merge tag 'v4.18.9' into v4.18/standard/base (2018-09-21 11:13:02  -0400)
  
  are available in the git repository at:
  
 https://github.com/limeng-linux/linux-yocto-4.18.git   v4.18/standard/intel-socfpga


I had updated to 4.18.14, so I rebased and merged this into the branch.
It is now pushed to the server.

Bruce

  
  for you to fetch changes up to a0fe17724f45667d757cdf29d20030ff21ca1491:
  
 spi-nor: add support for mx25u51245g (2018-10-10 00:31:57 -0700)


thanks ,
Limeng



-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Friday, October 12, 2018 10:36 PM
To: Li, Meng
Cc: linux-yocto@yoctoproject.org
Subject: Re: [linux-yocto]: [yocto-4.18]: intel-socfpga: kernel patches

On 10/10/2018 09:49 PM, meng...@windriver.com wrote:

From: Limeng 


Hi Bruce,

I am working on BSP intel-socfpga.

Could you please help to create branch "v4.18/standard/intel-socfpga" in

linux-yocto kernel?

And then merge these kernel patches into this branch.


I created the branch, but the patches never came through. Is there
somewhere you can stage them, and then send a pull request ?

Bruce



I verify these patches on Intel-PSG stratix10 development board.
Boot up log as below:

Starting kernel ...

Booting Linux on physical CPU 0x00 [0x410fd034]
Linux version 4.18.9-yoctodev-standard (oe-user@oe-host) (gcc version

8.2.0 (GCC)) #1 SMP PREEMPT Sat Sep 29 10:47:46 UTC 2018

Machine model: SoCFPGA Stratix 10 SoCDK
earlycon: uart0 at MMIO32 0xffc02000 (options '115200n8')
bootconsole [uart0] enabled
efi: Getting EFI parameters from FDT:
efi: UEFI not found.
Reserved memory: created DMA memory pool at 0x,

size 16 MiB

OF: reserved mem: initialized node svcbuffer@0, compatible id shared-

dma-pool

cma: Reserved 16 MiB at 0x7e80
psci: probing for conduit method from DT.
psci: PSCIv65535.65535 detected in firmware.
psci: Using standard PSCI v0.2 function IDs
psci: MIGRATE_INFO_TYPE not supported.
psci: SMC Calling Convention v1.0
random: get_random_bytes called from start_kernel+0x9c/0x458 with

crng_init=0

percpu: Embedded 23 pages/cpu @(ptrval) s53784 r8192 d32232

u94208

Detected VIPT I-cache on CPU0
CPU features: enabling workaround for ARM erratum 845719
CPU features: detected: Kernel page table isolation (KPTI)
Built 1 zonelists, mobility grouping on.  Total pages: 512064
Kernel command line: console=ttyS0,115200n8 earlycon root=/dev/nfs rw

no_console_suspend rootwait
nfsroot=128.224.162.206:/home/wrsadmin/Project/Native/nfsroot/intel-
stratix10-1018,v3,p

Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Memory: 2011824K/2080768K available (9276K kernel code, 1060K rwdata,

4192K rodata, 960K init, 649K bss, 52560K reserved, 16384K cma-reserved)

SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
ftrace: allocating 31531 entries in 124 pages
Preemptible hierarchical RCU implementation.
  Tasks RCU enabled.
NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
GIC: Using split EOI/Deactivate mode
arch_timer: cp15 timer(s) running at 400.00MHz (phys).
clocksource: arch_sys_counter: mask: 0xff max_cycles:

0x5c4093a7d1, max_idle_ns: 440795210635 ns

sched_clock: 56 bits at 400MHz, resolution 2ns, wraps every

4398046511103ns

Console: colour dummy device 80x25
Calibrating delay loop (skipped), value calculated using timer frequency..

800.00 BogoMIPS (lpj=160)

pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes)
ASID allocator initialised with 32768 entries
Hierarchical SRCU implementation.
EFI services will not be available.
smp: Bringing up secondary CPUs ...
Detected VIPT I-cache on CPU1
CPU1: Booted secondary processor 0x01 [0x410fd034]
Detected VIPT I-cache on CPU2
CPU2: Booted secondary processor 0x02 [0x410fd034]
Detected VIPT I-cache on CPU3
CPU3: Booted secondary processor 0x03 [0x410fd034]
smp: Brought up 1 node, 4 CPUs
SMP: Total of 4 processors activated.
CPU features: detected: 32-bit EL0 Support
CPU: All CPU(s) started at EL2
alternatives: patching kernel code
devtmpfs: initialized
clocksource: jiffies: mask: 0x max_cycles: 0x, max_idle_ns:

764504178510 ns

futex hash table entries: 1024 (order: 4, 65536 bytes)
xor: measuring software checksum speed
 8regs :  1967.000 

[yocto] yocto raspberrypi showing default splash instead of raspberrypi splash

[sanjay chopra]

I tried to build rpi-basic-image and core-image-base ( rpi-basic-image.bb
suggest to build core-image-base because rpi-basic-image is deprecated) for
raspberry pi zero wifi. I am able to build and boot these images. But these
images shows yocto splash instead of raspberry pi splash.

Please find attached build id and local.conf.

Is there something I missed ? Do I need to add some more parameter in
local.conf ( i tried SPLASH = "psplash-raspberrypi")?

-- 

*RegardsSanjay*
raspberrypi0-wifi: rpi-basic-image configured for poky 2.5.1

Build Configuration:
BB_VERSION   = "1.38.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "arm-poky-linux-gnueabi"
MACHINE  = "raspberrypi0-wifi"
DISTRO   = "poky"
DISTRO_VERSION   = "2.5.1"
TUNE_FEATURES= "arm armv6 vfp arm1176jzfs callconvention-hard"
TARGET_FPU   = "hard"
meta 
meta-poky= "sumo:3b8dc3a88e28546100a6b0b2f2cc37f44e619371"
meta-oe  
meta-multimedia  
meta-python  
meta-networking  = "sumo:2bb21ef27c4b0c9d52d30b3b2c5a0160fd02b966"
meta-raspberrypi = "sumo:2d40b21bc8a9ef7f329ed0ad410f8d227b97"



local.conf
Description: Binary data
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] permissions when installing scripts

[Burton, Ross]

As you've discovered, cp doesn't preserve permissions.  Using install
-m755 is the idiom.

Ross
On Mon, 15 Oct 2018 at 11:12, Belisko Marek  wrote:
>
> Hi,
>
> I have package which contains bunch of scripts (with +x flag for
> user). When installed in do_install method (simply by copying them to
> destination) they loose +x flag. I know copying directly is not best
> approach but there exists better way how to keep scripts permissions
> like in repo (except calling install -m 755 for all of them)? Thanks.
>
> BR,
>
> marek
>
> --
> as simple and primitive as possible
> -
> Marek Belisko - OPEN-NANDRA
> Freelance Developer
>
> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
> Tel: +421 915 052 184
> skype: marekwhite
> twitter: #opennandra
> web: http://open-nandra.com
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] permissions when installing scripts

[Belisko Marek]

Hi,

I have package which contains bunch of scripts (with +x flag for
user). When installed in do_install method (simply by copying them to
destination) they loose +x flag. I know copying directly is not best
approach but there exists better way how to keep scripts permissions
like in repo (except calling install -m 755 for all of them)? Thanks.

BR,

marek

-- 
as simple and primitive as possible
-
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [Yocto][poky][meta] already-stripped ignore if set for any other package then INSANE_SKIP_${PN}

[Måns Zigher]

Hi,

Sorry I see now that there is a typo. What I mean is that in the default
package I am not suing INSANE_SKIP but for packag1 I need already-stripped

INSANE_SKIP_${PN}-package1 = " \
dev-so \
already-stripped \
"

But I continuously get the error that they are already-stripped. So is it
supposed to work because I don't understand  the code in the
package.bbclass since it looks like it is only checking for
already-stripped in ${PN} and not ${PN}-package1?

BR
Måns Zigher



Den fre 12 okt. 2018 kl 16:30 skrev Burton, Ross :

> On Thu, 11 Oct 2018 at 18:14, Måns Zigher  wrote:
> > I have been struggling with a problem where I need to create a package
> in a recipe and set already-stripped for that package. The package in
> question is not the the default one so I am trying to set it by using
> >
> > INSANE_SKIP_${PN} += " \
> > dev-so \
> > already-stripped \
> > "
>
> You say no the default one, but PN is "the default" one, so that's
> probably why that doesn't work.
>
> Ross
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto