Re: [yocto] Layer index not updated

[Andreas Müller]

On Tue, Jan 9, 2018 at 4:54 AM, Paul Eggleton  wrote:

> On Tuesday, 9 January 2018 1:14:05 AM NZDT Andreas Müller wrote:
> > > Ping?
>
> Still broken (sorry about that!) but Michael and I will be working
> together on
> it tomorrow.
>
> Cheers,
> Paul
>
> Just saw list was updated. Thanks a lot!

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

Re: [yocto] yocto Digest, Vol 88, Issue 32

[Mathew K Tharakan]

Hi,

I'm using iMX6ULL evk. I would like to change direction and value of some
gpios. How to do that?? Could you help me in this, since I'm completely new
to BSP.

Thanks and Regards

Mathew K Tharakan

On Thu, Jan 11, 2018 at 5:28 PM,  wrote:

> Send yocto mailing list submissions to
> yocto@yoctoproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/yocto
> or, via email, send a message with subject or body 'help' to
> yocto-requ...@yoctoproject.org
>
> You can reach the person managing the list at
> yocto-ow...@yoctoproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of yocto digest..."
>
>
> Today's Topics:
>
>1. How can I change the default ext4 or etx3 of the rootfs to
>   ext2 or jffs2 in yocto build? (Nguy?n Thanh V?)
>2. Re: How can I change the default ext4 or etx3 of the rootfs
>   to ext2 or jffs2 in yocto build? (John, Maxin)
>3. libgcc.a size (Mircea Gliga)
>4. Re: [meta-oic] Question about Iotivity 1.3.0/1 and fixes
>   status (Philippe Coval)
>5. Re: libgcc.a size (Zoran Stojsavljevic)
>6. Re: libgcc.a size (Mircea Gliga)
>7. Re: libgcc.a size (Stefano Babic)
>
>
> --
>
> Message: 1
> Date: Thu, 11 Jan 2018 15:05:06 +0700
> From: Nguy?n Thanh V?  
> To: yocto@yoctoproject.org
> Subject: [yocto] How can I change the default ext4 or etx3 of the
> rootfs to ext2 or jffs2 in yocto build?
> Message-ID:
>  gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I want to minimize the size of the image built in core-image-minimal.
> However, I have no idea how to change the local.conf file or recipe file.
> Can anyone help me?
> -- next part --
> An HTML attachment was scrubbed...
> URL:  attachments/20180111/2808d656/attachment-0001.html>
>
> --
>
> Message: 2
> Date: Thu, 11 Jan 2018 08:23:26 +
> From: "John, Maxin" 
> To: "ngthanh.v...@gmail.com" ,
> "yocto@yoctoproject.org" 
> Subject: Re: [yocto] How can I change the default ext4 or etx3 of the
> rootfs to ext2 or jffs2 in yocto build?
> Message-ID:
> <61c0517ead808b429a1de2dd9164d40032668...@irsmsx103.ger.
> corp.intel.com>
>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> An easy way will be to refer Yocto documentation:
> http://www.yoctoproject.org/docs/current/yocto-project-qs/
> yocto-project-qs.html
>
> and for required rootfs changes, use IMAGE_FSTYPES:
> http://www.yoctoproject.org/docs/2.4/mega-manual/mega-
> manual.html#var-IMAGE_FSTYPES
>
> >From: yocto-boun...@yoctoproject.org [mailto:yocto-bounces@
> yoctoproject.org] On Behalf Of Nguy?n Thanh Vu
> >Sent: Thursday, January 11, 2018 10:05 AM
> >To: yocto@yoctoproject.org
> >Subject: [yocto] How can I change the default ext4 or etx3 of the rootfs
> to ext2 or jffs2 in yocto build?
>
> >I want to minimize the size of the image built in core-image-minimal.
> However, I have no idea how to change the >local.conf file or recipe file.
> Can anyone help me?
>
> Best Regards,
> Maxin
>
> -- next part --
> An HTML attachment was scrubbed...
> URL:  attachments/20180111/0cb5fe97/attachment-0001.html>
>
> --
>
> Message: 3
> Date: Thu, 11 Jan 2018 11:04:46 +0200
> From: Mircea Gliga 
> To: Yocto Project 
> Subject: [yocto] libgcc.a size
> Message-ID: 
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hello
>
> I just upgraded from krogoth to rocko, and noticed the resulting rootfs
> image increased significantly.
> What stands out is a big bump in size for
> /usr/lib/arm-poky-linux-gnueabi/7.2.0/libgcc.a from 5 MB in krogoth(gcc
> 5.3.0) to 25 MB in rocko.
> Can someone shed some light ? What can be done ?
>
> Thanks
>
>
>
> --
>
> Message: 4
> Date: Thu, 11 Jan 2018 10:39:00 +0100
> From: Philippe Coval 
> To: yocto@yoctoproject.org
> Cc: "iotivity-...@lists.iotivity.org"
> ,  "Maloor, Kishen"
> 
> Subject: Re: [yocto] [meta-oic] Question about Iotivity 1.3.0/1 and
> fixes   status
> Message-ID: <952a174d-ae9f-e82f-3294-1d9490cf8...@osg.samsung.com>
> Content-Type: text/plain; charset=utf-8
>
>
> On 11/01/18 02:30, Chanho Park wrote:
> > Hi Philippe,
> >
> Hi Chanho Park, HNY to you
> > I found you already prepared iotivity 1.3.0, 1.3.1 recipes and fixes
> > in your github tree[1].
>
> Yes they are still under review, did you test them ?
>
> Maybe I should resend them, now.
>
> > I wonder why you don?t post them in the meta-oic.
>
> Well I shared patches to list couple of time:
>
> https://lists.yoctoproject.org/pipermail/yocto/2017-June/036896.html
> https://lists.yoctoproject.org/pipermail/yocto/2017-September/037829.htm

[yocto] pseudo: symbolic links in pseudo

[Pavlina Varekova]

Hello,

I have an issue getting pseudo working with symbolic links. Pseudo does not
see files linked by "ln -s" in jail. (It emits warning: No such file or 
directory)


How to reproduce it:

# mkdir -p /dir1/jail
# cd /dir1/jail
# ln -s /bin/ls ./ls4
# ls -la
total 140
drwxr-xr-x. 2 root root   4096 Jan 12 03:37 .
drwxr-xr-x. 3 root root   4096 Jan 12 03:37 ..
lrwxrwxrwx. 1 root root  7 Jan 12 03:37 ls4 -> /bin/ls
# /pseudorepo/bin/pseudo  -r "/dir1/jail" -P /pseudorepo/
bash-4.3# /ls4
bash: /ls4: No such file or directory


If the binary is copied, pseudo works correctly.
Interesting is that if the jail directory is directly in /root/ (/root/any_
one_dir) then files linked by ln -s are seen by pseudo in jail correctly. 
If the jail is e.g. /home/tester (or some more nested dir), then ln -s does
not work correctly.

Is this pseudo behavior intentional? Is there any classic approach to move /
dev/urandom file into the jail without root permissions, for pseudo?

Best regards
Pavlina Moravcova Varekova-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] COMPATIBLE_MACHINE not honored in native extended recipes

[Paulo Neves]

Hello I am having a problem where I want a recipe, along with its
-native version to only be available when allowed by compatible
machine.

In the non native case, COMPATIBLE_MACHINE is correctly honored. But
in the -native version the COMPATIBLE_MACHINE is not honored because
in the native.bbclass there is:

MACHINEOVERRIDES = ""

This change was introduced in d09e6d883042e5d094cd08d829327c4bbbfae135.
While the explanation provided by the commit is accurate for specific
case mentioned it also breaks the COMPATIBLE_MACHINE mechanism which
relies on the MACHINEOVERRIDES variable.

Further evidence that this was not intended is that the exception text is false:

ERROR: Nothing PROVIDES 'x-filter-native'
x-filter-native was skipped: incompatible with machine m1 (not in
COMPATIBLE_MACHINE)

And the x-filter-native'.bb recipe header contains:

COMPATIBLE_MACHINE = "^m1$"


So the exception uses ${MACHINE} to report that a ${MACHINEOVERRIDE}
was not matched with the COMPATIBLE_MACHINE, which is a false
statement.

My solution is very simple and does not break the fix that
d09e6d883042e5d094cd08d829327c4bbbfae135 did:
From 8b78c81dc1d21bc23aeb1387c201e090f031a14a Mon Sep 17 00:00:00 2001
From: Paulo Neves 
Date: Fri, 12 Jan 2018 15:58:39 +0100
Subject: [PATCH 1/1] Fix COMPATIBLE_MACHINE for -native recipe variants.

Hello I am having a problem where I want a recipe, along
with its -native version to only be available when allowed
by compatible machine.

In the non native case, COMPATIBLE_MACHINE is correctly
honored. But in the -native version the COMPATIBLE_MACHINE
is not honored because in the native.bbclass there is:

MACHINEOVERRIDES = ""

This change was introduced in
d09e6d883042e5d094cd08d829327c4bbbfae135.
While the explanation provided by the commit is accurate for
specific case mentioned it also breaks the
COMPATIBLE_MACHINE mechanism which relies on the
MACHINEOVERRIDES variable.

Further evidence that this was not intended is that the
exception text is false:

ERROR: Nothing PROVIDES 'x-filter-native'
x-filter-native was skipped: incompatible with machine m1
(not in COMPATIBLE_MACHINE)

And the x-filter-native'.bb recipe header contains:

COMPATIBLE_MACHINE = "^m1$"

So the exception uses ${MACHINE} to report that a
${MACHINEOVERRIDE} was not matched with the
COMPATIBLE_MACHINE, which is a false statement.

This fix attempts to correct the issue with minimal
changes.

Change-Id: If5085e4e92550b8154033dd56149eb4e358ef266
---
 meta/classes/base.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index c3c2669939c6f0b9080727378a26a324072d7e51..b4051102d0eccfb576d8b76f6f47ce8cd763af55 100644
--- a/meta/classes/base.bbclass
+++ b/meta/classes/base.bbclass
@@ -473,7 +473,7 @@ python () {
 need_machine = d.getVar('COMPATIBLE_MACHINE', True)
 if need_machine:
 import re
-compat_machines = (d.getVar('MACHINEOVERRIDES', True) or "").split(":")
+compat_machines = (d.getVar('MACHINEOVERRIDES', True) or d.getVar('MACHINE', True)).split(":")
 for m in compat_machines:
 if re.match(need_machine, m):
 break
-- 
2.6.2

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

Re: [yocto] COMPATIBLE_MACHINE not honored in native extended recipes

[akuster808]

On 01/12/2018 07:14 AM, Paulo Neves wrote:
> Hello I am having a problem where I want a recipe, along with its
> -native version to only be available when allowed by compatible
> machine.

 This change should go to the openembedded-core mailing list with a
particular subject line format.

please try:
git send-email -1 -M --to  openembedded-c...@lists.openembedded.org
--subject-prefix=PATCH

Thanks for the fix.

Regards,
Armin

> In the non native case, COMPATIBLE_MACHINE is correctly honored. But
> in the -native version the COMPATIBLE_MACHINE is not honored because
> in the native.bbclass there is:
>
> MACHINEOVERRIDES = ""
>
> This change was introduced in d09e6d883042e5d094cd08d829327c4bbbfae135.
> While the explanation provided by the commit is accurate for specific
> case mentioned it also breaks the COMPATIBLE_MACHINE mechanism which
> relies on the MACHINEOVERRIDES variable.
>
> Further evidence that this was not intended is that the exception text is 
> false:
>
> ERROR: Nothing PROVIDES 'x-filter-native'
> x-filter-native was skipped: incompatible with machine m1 (not in
> COMPATIBLE_MACHINE)
>
> And the x-filter-native'.bb recipe header contains:
>
> COMPATIBLE_MACHINE = "^m1$"
>
>
> So the exception uses ${MACHINE} to report that a ${MACHINEOVERRIDE}
> was not matched with the COMPATIBLE_MACHINE, which is a false
> statement.
>
> My solution is very simple and does not break the fix that
> d09e6d883042e5d094cd08d829327c4bbbfae135 did:
>
>

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

Re: [yocto] What is the procedure for creating a board support package?

[Stephen Lawrence]

Hi Peter,

As Petter said your MACHINE variable might not be set correctly.

As an aside the Yocto Project used to maintain a BSP tutorial alongside the 
documentation. I've not looked at it for some versions but if that is still 
true you might find that useful in your education. An online search should turn 
it up.

Cheers

Steve

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Peter Spierenburg
Sent: 09 January 2018 18:39
To: yocto@yoctoproject.org
Subject: [yocto] What is the procedure for creating a board support package?

I'm trying to follow the instructions at:

http://www.yoctoproject.org/docs/current/bsp-guide/bsp-guide.html#creating-a-new-bsp-layer-using-the-yocto-bsp-script

I followed the prompts exactly as specified (although the SMP support prompt 
did not appear), and I chose the default 4.12 kernel (presumably the guide is 
slightly out of date).

I included the generated bsp in bblayers.conf as indicated.

I invoked:
bitbake core-image-minimal
However, the resulting build was intel based, and not arm as one might expect 
since I asked for ARM when prompted by the yocto-bsp script.
Is there a more hands-on document that I could be following?
Peter.

This communication, including any attached documentation, is intended only for 
the person or entity to which it is addressed, and may contain confidential, 
personal, and/or privileged information. Any unauthorized disclosure, copying, 
or taking action on the contents is strictly prohibited. If you have received 
this message in error, please contact us immediately so we may correct our 
records. Please then delete or destroy the original transmission and any 
subsequent reply. Thank you. 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] GPIO configuration in imx6ull

[Mathew K Tharakan]

Hi,

I'm using iMX6ULL evk. I would like to change direction and value of some
gpios. How to do that?? Could you help me in this, since I'm completely new
to BSP.

Thanks and Regards
Mathew. K. Tharakan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Reg: SPI enabling in imx6ull

[Mathew K Tharakan]

Hi,

I'm unable found spidev in /dev, I have done necessary changes in .dts
file. I'm working with iMX6ULL evk

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