[yocto] [meta-rockchip][PATCH] qtbase: Add needed bbappend for rk3399 SOCs

[Khem Raj]

This ensures that DISTRO_FEATURES can translates correctly
for qtbate packageconfigs and we can get right platforms enabled

Signed-off-by: Khem Raj 
---
 conf/layer.conf  | 5 +
 .../qt5-layer/recipes-qt/qt5/qtbase_%.bbappend   | 9 +
 2 files changed, 14 insertions(+)
 create mode 100644 dynamic-layers/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend

diff --git a/conf/layer.conf b/conf/layer.conf
index b263b6f..f97fb69 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -16,3 +16,8 @@ BBFILE_PRIORITY_rockchip = "1"
 LAYERVERSION_rockchip = "1"
 LAYERSERIES_COMPAT_rockchip = "hardknott"
 LAYERDEPENDS_rockchip = "core meta-arm"
+
+BBFILES_DYNAMIC += " \
+qt5-layer:${LAYERDIR}/dynamic-layers/qt5-layer/*/*/*.bb \
+qt5-layer:${LAYERDIR}/dynamic-layers/qt5-layer/*/*/*.bbappend \
+"
diff --git a/dynamic-layers/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend 
b/dynamic-layers/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend
new file mode 100644
index 000..a977229
--- /dev/null
+++ b/dynamic-layers/qt5-layer/recipes-qt/qt5/qtbase_%.bbappend
@@ -0,0 +1,9 @@
+PACKAGECONFIG_GL_rk3399 = "${@bb.utils.contains('DISTRO_FEATURES', 'x11 
opengl', 'gl', \
+  bb.utils.contains('DISTRO_FEATURES', 'opengl', 
'eglfs gles2', \
+'', d), d)}"
+PACKAGECONFIG_GL_append_rk3399 = " kms gbm"
+
+PACKAGECONFIG_FONTS_rk3399 = "fontconfig"
+
+PACKAGECONFIG_append_rk3399 = " libinput examples tslib xkbcommon"
+PACKAGECONFIG_remove_rk3399 = "tests"
-- 
2.32.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53872): https://lists.yoctoproject.org/g/yocto/message/53872
Mute This Topic: https://lists.yoctoproject.org/mt/83547078/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] M+ & H bugs with Milestone Movements WW24

[Stephen Jolley]

All,

YP M+ or high bugs which moved to a new milestone in WW24 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  3362

Improve dependency analysis tools

richard.pur...@linuxfoundation.org

newco...@yoctoproject.org

Future

3.99

Thanks, 

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com  

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53871): https://lists.yoctoproject.org/g/yocto/message/53871
Mute This Topic: https://lists.yoctoproject.org/mt/83545557/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW23!

[Stephen Jolley]

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


randy.macl...@windriver.com

2


r...@burtonini.com

1


jpewhac...@gmail.com

1


liezhi.y...@windriver.com

1


richard.pur...@linuxfoundation.org

1


Grand Total

6

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53870): https://lists.yoctoproject.org/g/yocto/message/53870
Mute This Topic: https://lists.yoctoproject.org/mt/83545538/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 3.4

[Stephen Jolley]

All,

Below is the list as of top 50 bug owners as of the end of WW24 of who have
open medium or higher bugs and enhancements against YP 3.4.   There are 96
possible work days left until the final release candidates for YP 3.4 needs
to be released.


Who

Count


richard.pur...@linuxfoundation.org

32


r...@burtonini.com

31


michael.opdenac...@bootlin.com

22


david.re...@windriver.com

22


bruce.ashfi...@gmail.com

21


bluelightn...@bluelightning.org

12


akuster...@gmail.com

12


timothy.t.orl...@intel.com

11


trevor.gamb...@windriver.com

11


jpewhac...@gmail.com

11


sakib.sa...@windriver.com

10


kai.k...@windriver.com

9


randy.macl...@windriver.com

9


hongxu@windriver.com

6


qi.c...@windriver.com

6


mingli...@windriver.com

6


chee.yang@intel.com

5


raj.k...@gmail.com

5


tony.tascio...@windriver.com

5


yi.z...@windriver.com

4


alexandre.bell...@bootlin.com

3


mostthings...@gmail.com

3


yf...@uwaterloo.ca

2


ms...@mvista.com

2


pokyli...@reliableembeddedsystems.com

2


ydir...@free.fr

2


jae...@xilinx.com

2


alejan...@enedino.org

2


yoctoproj...@cookiesoft.de

1


naveen.kumar.sa...@intel.com

1


kerg...@gmail.com

1


martin.ja...@gmail.com

1


stacygaikov...@gmail.com

1


dl...@gmx.de

1


liezhi.y...@windriver.com

1


open.sou...@oleksandr-kravchuk.com

1


weave...@gmail.com

1


nicolas.deche...@linaro.org

1


kexin@windriver.com

1


mark.ha...@windriver.com

1


mister...@web.de

1


jon.ma...@arm.com

1


john.kaldas.e...@gmail.com

1


jeanmarie.lemeta...@gmail.com

1


devendra.tew...@gmail.com

1


aeh...@gmail.com

1


diego.sue...@arm.com

1


matthew...@posteo.net

1


thomas.per...@bootlin.com

1


saul.w...@windriver.com

1


douglas.ro...@taitradio.com

1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53869): https://lists.yoctoproject.org/g/yocto/message/53869
Mute This Topic: https://lists.yoctoproject.org/mt/83545483/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[Stephen Jolley]

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, 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 347
unassigned or newcomer 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 four different "priority" classes
right now, "3.2", "3.3, "3.99" and "Future", the more pressing/urgent issues
being in "3.2" and then "3.3".

 

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 (sjolley.yp...@gmail.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_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53868): https://lists.yoctoproject.org/g/yocto/message/53868
Mute This Topic: https://lists.yoctoproject.org/mt/83545473/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-java] icedtea7 fetching error

[Richard Leitner]

On Mon, Jun 14, 2021 at 09:29:05PM +0100, Richard Purdie wrote:
> On Mon, 2021-06-14 at 20:20 +, Richard Leitner - SKIDATA wrote:
> > On Thu, Jun 10, 2021 at 10:57:46AM +0200, Alexander Kanavin wrote:
> > > I have the tarball. I think we should toss it somewhere safe and update 
> > > the
> > > recipe, as it is unlikely the old mercurial repo is coming back.
> > > 
> > > Suggestions?
> > 
> > Sorry for the late reply, I was on vacation .
> > 
> > Nothing that comes to my mind directly. Do you know of any hosting
> > possibilites from YP or OE-Core?
> > 
> > @Richard: Sorry for putting you in that conversation without warning...
> > But maybe you may guide us in a direction where to host/mirror some "legacy"
> > meta-java source tarballs?
> 
> If someone points me at the tarballs I can probably sort something out with
> our source mirrors.

Thank you very much Richard!
The openjdk8 tarballs are now hosted at 
https://downloads.yoctoproject.org/mirror/sources/
with their local download names.

Unfortunately I currently don't have the time and resources to provide a
patch for fixing the URLs and adding the mirror.
So help is greatly appreciated!

regards;rl

> 
> Cheers,
> 
> Richard
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53866): https://lists.yoctoproject.org/g/yocto/message/53866
Mute This Topic: https://lists.yoctoproject.org/mt/83390307/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-java] icedtea7 fetching error

[Richard Leitner]

On Mon, Jun 14, 2021 at 09:29:05PM +0100, Richard Purdie wrote:
> On Mon, 2021-06-14 at 20:20 +, Richard Leitner - SKIDATA wrote:
> > On Thu, Jun 10, 2021 at 10:57:46AM +0200, Alexander Kanavin wrote:
> > > I have the tarball. I think we should toss it somewhere safe and update 
> > > the
> > > recipe, as it is unlikely the old mercurial repo is coming back.
> > > 
> > > Suggestions?
> > 
> > Sorry for the late reply, I was on vacation .
> > 
> > Nothing that comes to my mind directly. Do you know of any hosting
> > possibilites from YP or OE-Core?
> > 
> > @Richard: Sorry for putting you in that conversation without warning...
> > But maybe you may guide us in a direction where to host/mirror some "legacy"
> > meta-java source tarballs?
> 
> If someone points me at the tarballs I can probably sort something out with
> our source mirrors.

Thanks for that!

I'm currently uploading the tarballs and provide you the link as soon as
it's finished (sorry, really crappy uplink here )

It's about 1GiB with following files affected:

openjdk8-242-corba-aarch64-shenandoah-jdk8u242-b07.tar.bz2
openjdk8-242-corba-jdk8u242-ga-aarch32-200120.tar.bz2
openjdk8-242-corba-jdk8u242-ga.tar.bz2
openjdk8-242-hotspot-aarch64-shenandoah-jdk8u242-b07.tar.bz2
openjdk8-242-hotspot-jdk8u242-ga-aarch32-200120.tar.bz2
openjdk8-242-hotspot-jdk8u242-ga.tar.bz2
openjdk8-242-jaxp-aarch64-shenandoah-jdk8u242-b07.tar.bz2
openjdk8-242-jaxp-jdk8u242-ga-aarch32-200120.tar.bz2
openjdk8-242-jaxp-jdk8u242-ga.tar.bz2
openjdk8-242-jaxws-aarch64-shenandoah-jdk8u242-b07.tar.bz2
openjdk8-242-jaxws-jdk8u242-ga-aarch32-200120.tar.bz2
openjdk8-242-jaxws-jdk8u242-ga.tar.bz2
openjdk8-242-jdk8u-aarch64-shenandoah-jdk8u242-b07.tar.bz2
openjdk8-242-jdk8u-jdk8u242-ga-aarch32-200120.tar.bz2
openjdk8-242-jdk8u-jdk8u242-ga.tar.bz2
openjdk8-242-jdk-aarch64-shenandoah-jdk8u242-b07.tar.bz2
openjdk8-242-jdk-jdk8u242-ga-aarch32-200120.tar.bz2
openjdk8-242-jdk-jdk8u242-ga.tar.bz2
openjdk8-242-langtools-aarch64-shenandoah-jdk8u242-b07.tar.bz2
openjdk8-242-langtools-jdk8u242-ga-aarch32-200120.tar.bz2
openjdk8-242-langtools-jdk8u242-ga.tar.bz2
openjdk8-242-nashorn-aarch64-shenandoah-jdk8u242-b07.tar.bz2
openjdk8-242-nashorn-jdk8u242-ga-aarch32-200120.tar.bz2
openjdk8-242-nashorn-jdk8u242-ga.tar.bz2
openjdk8-252-corba-aarch64-shenandoah-jdk8u252-b09.tar.bz2
openjdk8-252-corba-jdk8u252-ga-aarch32-20200415.tar.bz2
openjdk8-252-corba-jdk8u252-ga.tar.bz2
openjdk8-252-hotspot-aarch64-shenandoah-jdk8u252-b09.tar.bz2
openjdk8-252-hotspot-jdk8u252-ga-aarch32-20200415.tar.bz2
openjdk8-252-hotspot-jdk8u252-ga.tar.bz2
openjdk8-252-jaxp-aarch64-shenandoah-jdk8u252-b09.tar.bz2
openjdk8-252-jaxp-jdk8u252-ga-aarch32-20200415.tar.bz2
openjdk8-252-jaxp-jdk8u252-ga.tar.bz2
openjdk8-252-jaxws-aarch64-shenandoah-jdk8u252-b09.tar.bz2
openjdk8-252-jaxws-jdk8u252-ga-aarch32-20200415.tar.bz2
openjdk8-252-jaxws-jdk8u252-ga.tar.bz2
openjdk8-252-jdk8u-aarch64-shenandoah-jdk8u252-b09.tar.bz2
openjdk8-252-jdk8u-jdk8u252-ga-aarch32-20200415.tar.bz2
openjdk8-252-jdk8u-jdk8u252-ga.tar.bz2
openjdk8-252-jdk-aarch64-shenandoah-jdk8u252-b09.tar.bz2
openjdk8-252-jdk-jdk8u252-ga-aarch32-20200415.tar.bz2
openjdk8-252-jdk-jdk8u252-ga.tar.bz2
openjdk8-252-langtools-aarch64-shenandoah-jdk8u252-b09.tar.bz2
openjdk8-252-langtools-jdk8u252-ga-aarch32-20200415.tar.bz2
openjdk8-252-langtools-jdk8u252-ga.tar.bz2
openjdk8-252-nashorn-aarch64-shenandoah-jdk8u252-b09.tar.bz2
openjdk8-252-nashorn-jdk8u252-ga-aarch32-20200415.tar.bz2
openjdk8-252-nashorn-jdk8u252-ga.tar.bz2
openjdk8-265-corba-jdk8u265-ga-aarch32-20200729.tar.bz2
openjdk8-265-corba-jdk8u265-ga.tar.bz2
openjdk8-265-hotspot-jdk8u265-ga-aarch32-20200729.tar.bz2
openjdk8-265-hotspot-jdk8u265-ga.tar.bz2
openjdk8-265-jaxp-jdk8u265-ga-aarch32-20200729.tar.bz2
openjdk8-265-jaxp-jdk8u265-ga.tar.bz2
openjdk8-265-jaxws-jdk8u265-ga-aarch32-20200729.tar.bz2
openjdk8-265-jaxws-jdk8u265-ga.tar.bz2
openjdk8-265-jdk8u-jdk8u265-ga-aarch32-20200729.tar.bz2
openjdk8-265-jdk8u-jdk8u265-ga.tar.bz2
openjdk8-265-jdk-jdk8u265-ga-aarch32-20200729.tar.bz2
openjdk8-265-jdk-jdk8u265-ga.tar.bz2
openjdk8-265-langtools-jdk8u265-ga-aarch32-20200729.tar.bz2
openjdk8-265-langtools-jdk8u265-ga.tar.bz2
openjdk8-265-nashorn-jdk8u265-ga-aarch32-20200729.tar.bz2
openjdk8-265-nashorn-jdk8u265-ga.tar.bz2
openjdk8-272-corba-aarch64-shenandoah-jdk8u272-b10.tar.bz2
openjdk8-272-corba-jdk8u272-b09-aarch32-20200929.tar.bz2
openjdk8-272-corba-jdk8u272-ga.tar.bz2
openjdk8-272-hotspot-aarch64-shenandoah-jdk8u272-b10.tar.bz2
openjdk8-272-hotspot-jdk8u272-b09-aarch32-20200929.tar.bz2
openjdk8-272-hotspot-jdk8u272-ga.tar.bz2
openjdk8-272-jaxp-aarch64-shenandoah-jdk8u272-b10.tar.bz2
openjdk8-272-jaxp-jdk8u272-b09-aarch32-20200929.tar.bz2
openjdk8-272-jaxp-jdk8u272-ga.tar.bz2
openjdk8-272-jaxws-aarch64-shenandoah-jdk8u272-b10.tar.bz2
openjdk8-272-jaxws-jdk8u272-b09-aarch32-20200929.tar.bz2
openjdk8-272-jaxws-jdk8u272-ga.tar.bz2
openjdk8-272-jdk8u-aarch64-shenandoah-jdk8u272-b10.tar.bz2

Re: [yocto] [meta-java] icedtea7 fetching error

[Richard Purdie]

On Mon, 2021-06-14 at 20:20 +, Richard Leitner - SKIDATA wrote:
> On Thu, Jun 10, 2021 at 10:57:46AM +0200, Alexander Kanavin wrote:
> > I have the tarball. I think we should toss it somewhere safe and update the
> > recipe, as it is unlikely the old mercurial repo is coming back.
> > 
> > Suggestions?
> 
> Sorry for the late reply, I was on vacation .
> 
> Nothing that comes to my mind directly. Do you know of any hosting
> possibilites from YP or OE-Core?
> 
> @Richard: Sorry for putting you in that conversation without warning...
> But maybe you may guide us in a direction where to host/mirror some "legacy"
> meta-java source tarballs?

If someone points me at the tarballs I can probably sort something out with
our source mirrors.

Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53864): https://lists.yoctoproject.org/g/yocto/message/53864
Mute This Topic: https://lists.yoctoproject.org/mt/83390307/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-java] icedtea7 fetching error

[Richard Leitner]

On Thu, Jun 10, 2021 at 10:57:46AM +0200, Alexander Kanavin wrote:
> I have the tarball. I think we should toss it somewhere safe and update the
> recipe, as it is unlikely the old mercurial repo is coming back.
> 
> Suggestions?

Sorry for the late reply, I was on vacation .

Nothing that comes to my mind directly. Do you know of any hosting
possibilites from YP or OE-Core?

@Richard: Sorry for putting you in that conversation without warning...
But maybe you may guide us in a direction where to host/mirror some "legacy"
meta-java source tarballs?

regards;rl

> 
> Alex
> 
> On Tue, 8 Jun 2021 at 08:10,  wrote:
> 
> > Hello,
> >
> >
> > I am trying to build something that relies on meta-java, but it fails on
> > do_fetch for the icedtea7 recipe:
> >
> > --2021-06-07 17:24:33--  
> > http://icedtea.classpath.org/hg/release/icedtea7-forest-2.1/archive/f89009ada191.tar.bz2
> > Resolving icedtea.classpath.org (icedtea.classpath.org)... 172.104.137.120
> > Connecting to icedtea.classpath.org 
> > (icedtea.classpath.org)|172.104.137.120|:80... connected.
> > HTTP request sent, awaiting response... 404 Not Found
> > 2021-06-07 16:21:05 ERROR 404: Not Found.
> >
> > ERROR: icedtea7-native-2.1.3-r1.0 do_fetch: Fetcher failure for URL: 
> > 'http://icedtea.classpath.org/hg/release/icedtea7-forest-2.1/archive/f89009ada191.tar.bz2;name=openjdk;unpack=false;downloadfilename=openjdk-f89009ada191.tar.bz2'.
> >  Unable to fetch URL from any source.
> >
> >
> > Following this link, seems like the webserver is down. Do you know any
> > mirror that I can use in the meantime?
> >
> > Thanks,
> > George
> >
> > 
> >
> >
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53863): https://lists.yoctoproject.org/g/yocto/message/53863
Mute This Topic: https://lists.yoctoproject.org/mt/83390307/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-rockchip][PATCH v2] Rock64: add machine

[Trevor Woerner]

Hi Yann,

Thanks for the contribution!

On Mon 2021-05-31 @ 04:00:58 PM, yann.dir...@blade-group.com wrote:
> From: Yann Dirson 
> 
> This is a RK3328 board from Pine64.
> Board details at https://wiki.pine64.org/wiki/ROCK64.
> 
> Default image is built to boot from SD-card.  Building an image for
> eMMC requires to set RK_BOOT_DEVICE="mmcblk0".
> 
> Signed-off-by: Yann Dirson 
> ---
> 
> This is just basic initial support without a kernel BSP.  As is the
> board boots with a serial console.
> 
> Note I had to create the SoC definition for rk3328, and rather than
> setting serial at 115200 there just to have the board definition
> override it with rockchip-standard 150 I've set the latter right
> in rk3328.inc.

Sounds good. I prefer the rockchip default of 1,500,000 anyway.

> 
> Changes in v2:
> - include Ayufan's patch for mmc aliases so presence of eMMC won't
> prevent booting from SD
> 
>  conf/machine/include/rk3328.inc   | 25 
>  conf/machine/rock64.conf  | 30 +++
>  ...an-dtsi-rk3328-add-mmc0-mmc1-aliases.patch | 27 +
>  recipes-kernel/linux/linux-yocto%.bbappend|  6 
>  4 files changed, 88 insertions(+)
>  create mode 100644 conf/machine/include/rk3328.inc
>  create mode 100644 conf/machine/rock64.conf
>  create mode 100644 
> recipes-kernel/linux/files/0001-ayufan-dtsi-rk3328-add-mmc0-mmc1-aliases.patch
> 
> diff --git a/conf/machine/include/rk3328.inc b/conf/machine/include/rk3328.inc
> new file mode 100644
> index 000..7d67627
> --- /dev/null
> +++ b/conf/machine/include/rk3328.inc
> @@ -0,0 +1,25 @@
> +# Copyright (C) 2020 Garmin Ltd. or its subsidaries

Odd that you'd be assigning the copyright to Garmin ;-)

> +# Released under the MIT license (see COPYING.MIT for the terms)
> +
> +SOC_FAMILY = "rk3328"
> +
> +DEFAULTTUNE ?= "cortexa53-crypto"
> +
> +require conf/machine/include/soc-family.inc
> +require conf/machine/include/tune-cortexa53.inc
> +require conf/machine/include/rockchip-defaults.inc
> +
> +KBUILD_DEFCONFIG ?= "defconfig"
> +KERNEL_CLASSES = "kernel-fitimage"
> +KERNEL_IMAGETYPE = "fitImage"
> +
> +TFA_PLATFORM = "rk3328"
> +TFA_BUILD_TARGET = "bl31"
> +
> +UBOOT_SUFFIX ?= "itb"
> +UBOOT_ENTRYPOINT ?= "0x0600"
> +
> +SERIAL_CONSOLES = "150;ttyS2"
> +
> +PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot"
> +SPL_BINARY ?= "idbloader.img"
> diff --git a/conf/machine/rock64.conf b/conf/machine/rock64.conf
> new file mode 100644
> index 000..38bc9fa
> --- /dev/null
> +++ b/conf/machine/rock64.conf
> @@ -0,0 +1,30 @@
> +# Copyright (C) 2021 Blade SAS

Can you also specify an OSS-friendly licence too?

> +
> +#@TYPE: Machine
> +#@NAME: Rock64
> +#@DESCRIPTION: Rock64 RK3328 board from Pine64
> +
> +require include/rk3328.inc
> +
> +MACHINE_FEATURES += "usbhost serial"
> +
> +UBOOT_MACHINE = "rock64-rk3328_defconfig"
> +KERNEL_DEVICETREE = "rockchip/rk3328-rock64.dtb"
> +
> +# set to mmcblk0 for booting from optional eMMC
> +RK_BOOT_DEVICE ?= "mmcblk1"
> +
> +WKS_FILE ?= "rock-pi-4.wks"

Personally I'd prefer to see a rock64 wic file which includes an rk3328
default, even if it is a copy of the rock-pi-4 layout.

> +IMAGE_FSTYPES += "wic wic.bmap"
> +
> +WKS_FILE_DEPENDS ?= " \
> +mtools-native \
> +dosfstools-native \
> +virtual/bootloader \
> +virtual/kernel \
> +"
> +IMAGE_BOOT_FILES ?= "\
> +${KERNEL_IMAGETYPE} \
> +"
> +
> +KBUILD_DEFCONFIG = "defconfig"
> diff --git 
> a/recipes-kernel/linux/files/0001-ayufan-dtsi-rk3328-add-mmc0-mmc1-aliases.patch
>  
> b/recipes-kernel/linux/files/0001-ayufan-dtsi-rk3328-add-mmc0-mmc1-aliases.patch
> new file mode 100644
> index 000..1ad3b9e
> --- /dev/null
> +++ 
> b/recipes-kernel/linux/files/0001-ayufan-dtsi-rk3328-add-mmc0-mmc1-aliases.patch
> @@ -0,0 +1,27 @@
> +From f10cfe01f753348d346374008b8e8f5f26ed94ab Mon Sep 17 00:00:00 2001
> +From: Kamil Trzcinski 
> +Date: Mon, 28 Aug 2017 11:24:37 +0200
> +Subject: [PATCH] ayufan: dtsi: rk3328: add mmc0/mmc1 aliases
> +Upstream-Status: Pending 
> [https://github.com/ayufan-rock64/linux-mainline-kernel/commit/f10cfe01f753348d346374008b8e8f5f26ed94ab]
> +
> +Change-Id: I82a5394df8a505f7d1496393621c1198895c88b0
> +---
> + arch/arm64/boot/dts/rockchip/rk3328.dtsi | 2 ++
> + 1 file changed, 2 insertions(+)
> +
> +diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi 
> b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> +index 0afed15bc7ff..800f1c796882 100644
> +--- a/arch/arm64/boot/dts/rockchip/rk3328.dtsi
>  b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> +@@ -27,6 +27,8 @@
> + i2c1 = 
> + i2c2 = 
> + i2c3 = 
> ++mmc0 = 
> ++mmc1 = 
> + ethernet0 = 
> + ethernet1 = 
> + };
> +-- 
> +2.30.2
> +
> diff --git a/recipes-kernel/linux/linux-yocto%.bbappend 
> b/recipes-kernel/linux/linux-yocto%.bbappend
> index 7702e3f..3789c72 100644
> --- a/recipes-kernel/linux/linux-yocto%.bbappend

Re: [yocto] thoughts on YP-friendly developer laptop?

[Adrian Bunk]

On Mon, Jun 14, 2021 at 07:58:19AM -0400, Robert P. J. Day wrote:
> 
>   starting to think about a new laptop that will, among other things,
> do lots of OE/YP builds, and i'll start with this as the basis for a
> few questions about hard drives:
> 
> https://www.dell.com/en-ca/shop/gaming-laptops/g15-ryzen-edition-gaming-laptop/spd/g-series-15-5515-laptop/ng155515_sb_ps25e
> 
> while an SSD would be delightful, i'm concerned about how doing
> frequent 40-50G builds would wear out an SSD. so i was considering
> looking for something with a fast regular HD for the actual build
> directories, but room to put in an M.2 NVMe that would hold fairly
> static content, like the OS itself, all the layers, a local source
> mirror and so on.
> 
> am i overthinking this? anyone have a laptop setup that is smokin'
> fast (yeah, 8 core AMD ryzen :-),

When using a laptop with only 16 GB RAM to build with 8 or 16 threads,
on what drive will the heavily used large swap partition be?

gcc loves to use > 2 GB RAM for non-trivial C++ code,
with 16 threads I'd recommend 64 GB RAM.

> and a dual drive layout that seems
> to work well with lots and lots of OE builds?

Ask for the specs of the SSD and do the math.

E.g. 150 TBW / 50 GB/build = 3000 builds

If you are building from scratch so often that the resulting number
is a worry, I'd rather buy 128 GB RAM and use a tmpfs instead of
creating a spinning rust bottleneck.

> rday

cu
Adrian

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53861): https://lists.yoctoproject.org/g/yocto/message/53861
Mute This Topic: https://lists.yoctoproject.org/mt/83528013/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] thoughts on YP-friendly developer laptop?

[Jack Mitchell]

- Ryzen based for core count
- No dedicated GPU as more wattage available for CPU + less heat for cpu
boosting
- Dual NVMe slots, or at least on-board emmc + NVMe slot, hold tmp in
NVMe, replace if it dies. Probably not going to be an issue, I have a
1TB NVMe drive which I've been doing multiple daily builds on for 2
years which is still at 99% health.

For a decent manufacturer? Dell aren't recommended at the moment as the
QA due to pandemic conditions is lacking and machines are arriving
broken. HP do some decent Ryzen based laptops, as do Lenovo. For a wild
card you can also check out System76 but they're just OEM rebrands.

Good luck, it's a minefield out there.

Regards,
Jack


On 14/06/2021 12:58, Robert P. J. Day wrote:
> 
>   starting to think about a new laptop that will, among other things,
> do lots of OE/YP builds, and i'll start with this as the basis for a
> few questions about hard drives:
> 
> https://www.dell.com/en-ca/shop/gaming-laptops/g15-ryzen-edition-gaming-laptop/spd/g-series-15-5515-laptop/ng155515_sb_ps25e
> 
> while an SSD would be delightful, i'm concerned about how doing
> frequent 40-50G builds would wear out an SSD. so i was considering
> looking for something with a fast regular HD for the actual build
> directories, but room to put in an M.2 NVMe that would hold fairly
> static content, like the OS itself, all the layers, a local source
> mirror and so on.
> 
>   am i overthinking this? anyone have a laptop setup that is smokin'
> fast (yeah, 8 core AMD ryzen :-), and a dual drive layout that seems
> to work well with lots and lots of OE builds?
> 
> rday
> 
> 
> 
> 
> 

-- 
Jack Mitchell, Consultant
https://www.tuxable.co.uk

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53860): https://lists.yoctoproject.org/g/yocto/message/53860
Mute This Topic: https://lists.yoctoproject.org/mt/83528013/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] thoughts on YP-friendly developer laptop?

[Robert P. J. Day]

  starting to think about a new laptop that will, among other things,
do lots of OE/YP builds, and i'll start with this as the basis for a
few questions about hard drives:

https://www.dell.com/en-ca/shop/gaming-laptops/g15-ryzen-edition-gaming-laptop/spd/g-series-15-5515-laptop/ng155515_sb_ps25e

while an SSD would be delightful, i'm concerned about how doing
frequent 40-50G builds would wear out an SSD. so i was considering
looking for something with a fast regular HD for the actual build
directories, but room to put in an M.2 NVMe that would hold fairly
static content, like the OS itself, all the layers, a local source
mirror and so on.

  am i overthinking this? anyone have a laptop setup that is smokin'
fast (yeah, 8 core AMD ryzen :-), and a dual drive layout that seems
to work well with lots and lots of OE builds?

rday

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53859): https://lists.yoctoproject.org/g/yocto/message/53859
Mute This Topic: https://lists.yoctoproject.org/mt/83528013/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] QEMU Size Increase from Yocto Thud to Zeus

[Zoran]

> Yes, look at the PACKAGECONFIGs and setting QEMU_TARGETS.

Does it mean that with the local.conf line:

# enable,disable,depends,rdepends
#
PACKAGECONFIG[qemu] = "--with-qemu,--without-qemu,qemu,"

The QEMU is completely removed (this is all that needs to be done, or...)?

Thank you,
Zee
___

On Mon, Jun 14, 2021 at 12:14 PM Ross Burton  wrote:
>
> Yes, look at the PACKAGECONFIGs and setting QEMU_TARGETS.
>
> Ross
>
> On Mon, 14 Jun 2021 at 09:04, Aashik Aswin  wrote:
> >
> > Thanks for the clarification, yes I am installing QEMU in my image. Is 
> > there some way that we can disable the additional architectures and 
> > streamline the size ?
> >
> > Thanks
> >
> > On Fri, Jun 11, 2021 at 8:48 PM Ross Burton  wrote:
> >>
> >> Are you installing qemu into your image though?
> >>
> >> Qemu did get larger as it is built with more architectures enabled,
> >> but unless you're installing it in your image it won't make a
> >> difference.
> >>
> >> Ross
> >>
> >> On Fri, 11 Jun 2021 at 11:40, Aashik Aswin  
> >> wrote:
> >> >
> >> > Hi Experts,
> >> >
> >> > I am upgrading my Linux from Yocto Thud to Zeus (5.4 Kernel) . After 
> >> > building I could see a significant increase in the size of the image.
> >> > On checking with buildhistory enabled, I could see that qemu has nearly 
> >> > doubled in size.
> >> >
> >> > Thud (4.19) - 223084  KiB qemu
> >> > Zeus (5.4) - 474757  KiB qemu
> >> >
> >> > Is this size increase expected or are there some additional configs that 
> >> > might have been added as a part of the upgrade ?
> >> >
> >> > Appreciate your help.
> >> >
> >> > TIA,
> >> > Aashik
> >> >
> >> >
> >> >
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53858): https://lists.yoctoproject.org/g/yocto/message/53858
Mute This Topic: https://lists.yoctoproject.org/mt/83465520/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] QEMU Size Increase from Yocto Thud to Zeus

[Ross Burton]

Yes, look at the PACKAGECONFIGs and setting QEMU_TARGETS.

Ross

On Mon, 14 Jun 2021 at 09:04, Aashik Aswin  wrote:
>
> Thanks for the clarification, yes I am installing QEMU in my image. Is there 
> some way that we can disable the additional architectures and streamline the 
> size ?
>
> Thanks
>
> On Fri, Jun 11, 2021 at 8:48 PM Ross Burton  wrote:
>>
>> Are you installing qemu into your image though?
>>
>> Qemu did get larger as it is built with more architectures enabled,
>> but unless you're installing it in your image it won't make a
>> difference.
>>
>> Ross
>>
>> On Fri, 11 Jun 2021 at 11:40, Aashik Aswin  wrote:
>> >
>> > Hi Experts,
>> >
>> > I am upgrading my Linux from Yocto Thud to Zeus (5.4 Kernel) . After 
>> > building I could see a significant increase in the size of the image.
>> > On checking with buildhistory enabled, I could see that qemu has nearly 
>> > doubled in size.
>> >
>> > Thud (4.19) - 223084  KiB qemu
>> > Zeus (5.4) - 474757  KiB qemu
>> >
>> > Is this size increase expected or are there some additional configs that 
>> > might have been added as a part of the upgrade ?
>> >
>> > Appreciate your help.
>> >
>> > TIA,
>> > Aashik
>> >
>> > 
>> >

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53857): https://lists.yoctoproject.org/g/yocto/message/53857
Mute This Topic: https://lists.yoctoproject.org/mt/83465520/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-java] icedtea7 fetching error

[marvin . franke]

Hello,

you can use wildebeest's mirror:

ICEDTEA_HG_URL = "http://icedtea.wildebeest.org/hg/release/${ICEDTEA_PREFIX};

Marvin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53856): https://lists.yoctoproject.org/g/yocto/message/53856
Mute This Topic: https://lists.yoctoproject.org/mt/83390307/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-zephyr][PATCH v2 1/2] zephyr-kernel: Add OpenThread add module to build

[Stefan Schmidt]

Hello.

On 11.06.21 03:26, Saini, Naveen Kumar wrote:




-Original Message-
From: yocto@lists.yoctoproject.org  On
Behalf Of Stefan Schmidt
Sent: Thursday, June 10, 2021 4:28 PM
To: yocto@lists.yoctoproject.org
Cc: Stefan Schmidt ; Stefan Schmidt

Subject: [yocto] [meta-zephyr][PATCH v2 1/2] zephyr-kernel: Add
OpenThread add module to build

From: Stefan Schmidt 

OpenThread support in Zephyr is realised as an external module. Make sure
we pull it in and have it available for applications to use it.

Signed-off-by: Stefan Schmidt 
---
  recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc| 1 +
  recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc | 1 +
  recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc   | 1 +
  3 files changed, 3 insertions(+)

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
index 330fe59..35c4106 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
@@ -29,6 +29,7 @@ ZEPHYR_MODULES_append_arm =
"\;${S}/modules/cmsis"
  ZEPHYR_MODULES_append_nordic = "\;${S}/modules/hal/nordic"
  ZEPHYR_MODULES_append_stm32 = "\;${S}/modules/hal/stm32"
  ZEPHYR_MODULES_append_openamp = "\;${S}/modules/lib/open-
amp\;${S}/modules/hal/libmetal"
+ZEPHYR_MODULES_append_openthread =
"\;${S}/modules/lib/openthread"


This is not required. It already listed in required sample recipe. Please 
remove it.


Fixed.



  EXTRA_OECMAKE_append = " -DZEPHYR_MODULES=${ZEPHYR_MODULES}"

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc
b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc
index 8475b5b..4910db2 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc
@@ -4,6 +4,7 @@ SRCREV_cmsis =
"c3bd2094f92d574377f7af2aec147ae181aa5f8e"
  SRCREV_nordic = "574493fe29c79140df4827ab5d4a23df79d03681"
  SRCREV_stm32 = "f8ff8d25aa0a9e65948040c7b47ec67f3fa300df"
  SRCREV_open-amp = "6010f0523cbc75f551d9256cf782f173177acdef"
+SRCREV_openthread = "385e19da1ae15f27872c2543b97276a42f102ead"
  SRCREV_libmetal = "39d049d4ae68e6f6d595fce7de1dcfc1024fb4eb"
  SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
  SRCREV_mbedtls = "5765cb7f75a9973ae9232d438e361a9d7bbc49e7"
diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc b/recipes-
kernel/zephyr-kernel/zephyr-kernel-src.inc
index 5e43583..4937a77 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
@@ -15,6 +15,7 @@ SRC_URI = "\
  git://github.com/zephyrproject-
rtos/hal_stm32.git;protocol=https;destsuffix=git/modules/hal/stm32;name=
stm32 \
  git://github.com/zephyrproject-
rtos/mbedtls.git;protocol=https;destsuffix=git/modules/lib/mbedtls;name=
mbedtls \
  git://github.com/zephyrproject-rtos/open-
amp.git;protocol=https;destsuffix=git/modules/lib/open-amp;name=open-
amp \
+
+ git://github.com/zephyrproject-rtos/openthread.git;protocol=https;bran
+ ch=zephyr;destsuffix=git/modules/lib/openthread;name=openthread \
  git://github.com/zephyrproject-



It  would cause build failure with v2.5.0. So add SRCREV_openthread in 
zephyr-kernel-src-2.5.0.inc too.


Indeed, I did not test with 2.5. Thanks for spotting. Fixed.

I send a v3 now.

regards
Stefan Schmidt

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53855): https://lists.yoctoproject.org/g/yocto/message/53855
Mute This Topic: https://lists.yoctoproject.org/mt/83440062/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-zephyr][PATCH v3 1/2] zephyr-kernel: Add OpenThread add module to build

[Stefan Schmidt]

From: Stefan Schmidt 

OpenThread support in Zephyr is realised as an external module. Make
sure we pull it in and have it available for applications to use it.

Signed-off-by: Stefan Schmidt 
---
 recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc | 1 +
 recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc | 1 +
 recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc   | 1 +
 3 files changed, 3 insertions(+)

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc 
b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
index 545197f..9cdc721 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.5.0.inc
@@ -4,6 +4,7 @@ SRCREV_cmsis = "c3bd2094f92d574377f7af2aec147ae181aa5f8e"
 SRCREV_nordic = "f3434da6446380fcdd426dbe2866af21d0d549b6"
 SRCREV_stm32 = "cc8731dba4fd9c57d7fe8ea6149828b89c2bd635"
 SRCREV_open-amp = "de1b85a13032a2de1d8b6695ae5f800b613e739d"
+SRCREV_openthread = "385e19da1ae15f27872c2543b97276a42f102ead"
 SRCREV_libmetal = "9d4ee2c3cfd5f49861939447990f3b7d7bf9bf94"
 SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
 SRCREV_mbedtls = "24d84ecff195fb15c889d9046e44e4804d626c67"
diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc 
b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc
index 8475b5b..4910db2 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.0.inc
@@ -4,6 +4,7 @@ SRCREV_cmsis = "c3bd2094f92d574377f7af2aec147ae181aa5f8e"
 SRCREV_nordic = "574493fe29c79140df4827ab5d4a23df79d03681"
 SRCREV_stm32 = "f8ff8d25aa0a9e65948040c7b47ec67f3fa300df"
 SRCREV_open-amp = "6010f0523cbc75f551d9256cf782f173177acdef"
+SRCREV_openthread = "385e19da1ae15f27872c2543b97276a42f102ead"
 SRCREV_libmetal = "39d049d4ae68e6f6d595fce7de1dcfc1024fb4eb"
 SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
 SRCREV_mbedtls = "5765cb7f75a9973ae9232d438e361a9d7bbc49e7"
diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc 
b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
index d65cc06..fb62cae 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
@@ -15,6 +15,7 @@ SRC_URI = "\
 
git://github.com/zephyrproject-rtos/hal_stm32.git;protocol=https;destsuffix=git/modules/hal/stm32;name=stm32
 \
 
git://github.com/zephyrproject-rtos/mbedtls.git;protocol=https;destsuffix=git/modules/lib/mbedtls;name=mbedtls
 \
 
git://github.com/zephyrproject-rtos/open-amp.git;protocol=https;destsuffix=git/modules/lib/open-amp;name=open-amp
 \
+
git://github.com/zephyrproject-rtos/openthread.git;protocol=https;branch=zephyr;destsuffix=git/modules/lib/openthread;name=openthread
 \
 
git://github.com/zephyrproject-rtos/libmetal.git;protocol=https;destsuffix=git/modules/hal/libmetal;name=libmetal
 \
 
git://github.com/zephyrproject-rtos/tinycrypt.git;protocol=https;destsuffix=git/modules/crypto/tinycrypt;name=tinycrypt
 \
 file://0001-cmake-add-yocto-toolchain.patch \
-- 
2.31.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53853): https://lists.yoctoproject.org/g/yocto/message/53853
Mute This Topic: https://lists.yoctoproject.org/mt/83525948/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-zephyr][PATCH v3 2/2] zephyr-openthread-echo-client: Add new echo-client variant for OpenThread

[Stefan Schmidt]

From: Stefan Schmidt 

Similar to the normal echo-client example it demonstrates socket usage,
but in this variant we enable the OpenThread config overlay and add the
needed module to the build.

Signed-off-by: Stefan Schmidt 
---
 .../zephyr-kernel/zephyr-openthread-echo-client.bb| 8 
 1 file changed, 8 insertions(+)
 create mode 100644 
recipes-kernel/zephyr-kernel/zephyr-openthread-echo-client.bb

diff --git a/recipes-kernel/zephyr-kernel/zephyr-openthread-echo-client.bb 
b/recipes-kernel/zephyr-kernel/zephyr-openthread-echo-client.bb
new file mode 100644
index 000..c985df2
--- /dev/null
+++ b/recipes-kernel/zephyr-kernel/zephyr-openthread-echo-client.bb
@@ -0,0 +1,8 @@
+include zephyr-sample.inc
+
+ZEPHYR_SRC_DIR = "${S}/samples/net/sockets/echo_client"
+
+ZEPHYR_MODULES_append = "\;${S}/modules/lib/mbedtls"
+ZEPHYR_MODULES_append = "\;${S}/modules/lib/openthread"
+
+EXTRA_OECMAKE += "-DOVERLAY_CONFIG=overlay-ot.conf"
-- 
2.31.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53854): https://lists.yoctoproject.org/g/yocto/message/53854
Mute This Topic: https://lists.yoctoproject.org/mt/83525950/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] QEMU Size Increase from Yocto Thud to Zeus

[Aashik Aswin]

Thanks for the clarification, yes I am installing QEMU in my image. Is
there some way that we can disable the additional architectures and
streamline the size ?

Thanks

On Fri, Jun 11, 2021 at 8:48 PM Ross Burton  wrote:

> Are you installing qemu into your image though?
>
> Qemu did get larger as it is built with more architectures enabled,
> but unless you're installing it in your image it won't make a
> difference.
>
> Ross
>
> On Fri, 11 Jun 2021 at 11:40, Aashik Aswin 
> wrote:
> >
> > Hi Experts,
> >
> > I am upgrading my Linux from Yocto Thud to Zeus (5.4 Kernel) . After
> building I could see a significant increase in the size of the image.
> > On checking with buildhistory enabled, I could see that qemu has nearly
> doubled in size.
> >
> > Thud (4.19) - 223084  KiB qemu
> > Zeus (5.4) - 474757  KiB qemu
> >
> > Is this size increase expected or are there some additional configs that
> might have been added as a part of the upgrade ?
> >
> > Appreciate your help.
> >
> > TIA,
> > Aashik
> >
> > 
> >
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53852): https://lists.yoctoproject.org/g/yocto/message/53852
Mute This Topic: https://lists.yoctoproject.org/mt/83465520/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-