Re: [yocto] How to define and build device tree in Yocto?

[Gabriele Zampieri]

Hi all,

Bas' defconfig trick (do_set_custom_defconfig) is already implemented by
Yocto itself: just add a file called defconfig to SRC_URI and the system
will apply it for you  (you can read kernel_do_configure in kernel.bbclass)
. For more information check
https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#changing-the-configuration

> how did you do the defconfig usually?

The link I put above asks this question too.

>> # The first patch simply appends my custom DTS to the list of DTD files
in the Makefile

and

>> I usually don't need to make large modifications to the kernel source,
>> so I don't need to clone the kernel, but use the default kernel for the
>> SoC with some patches.

How do you generate that patches?

I know that the kernel repo is huge, but having a local kernel tree can be
very useful and allows you to do all the patchworks easily. It also speeds
up the test if you are planning to upgrade some part of it.

Best regards,
Gabriele

Il giorno mar 7 mag 2019 alle ore 02:14 JH  ha
scritto:

> Hi Bas and Gabriele,
>
> Thank you so much for you advice.
>
> > My usual way of doing it is as follows:
> >
> > I usually don't need to make large modifications to the kernel source,
> > so I don't need to clone the kernel, but use the default kernel for the
> > SoC with some patches.
>
> So do I.
>
> > I use a platform support layer and add a .bbappend file for the (arm)
> > kernel to add a custom dts and .config files, together with some small
> > patches:
> >
> > *** File meta-/recipes-kernel/linux/linux-_%.bbappend:
> >
> > THISAPPENDFILESDIR := "${THISDIR}/files"
> > FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> >
> > require linux-set-custom-defconfig.inc
> > require linux-add-custom-dts.inc
> >
> > # The first patch simply appends my custom DTS to the list of DTD files
> > in the Makefile
> > SRC_URI += \
> >  "file://add-custom-dts.patch \
> >   file://some_other.patch \
> >   file://another_driver_patch.patch \
> >  "
> >
> > *** File meta-/recipes-kernel/linux/linux-add-custom-dts.inc
> >
> > do_add_platform_dts() {
> >   cp -f "${THISAPPENDFILESDIR}/custom.dts" \
> >  "${WORKDIR}/git/arch/arm/boot/dts"
> > }
>
> That is exactly I am looking for the proper location of the dts files,
> thank you so much.
>
> > addtask add_platform_dts before do_preconfigure after do_patch
> >
> > *** File
> > meta-/recipes-kernel/linux/linux-set-custom-defconfig.inc
> >
> > do_set_custom_defconfig() {
> >  cp -f "${THISAPPENDFILESDIR}/defconfig" "${WORKDIR}/defconfig"
> > }
> >
> > addtask set_custom_defconfig before do_preconfigure after do_patch
>
> Good advice, I missed that one, how did you do the defconfig usually?
> Compile it in kernel source like using following command?
>
> make ARCH=arm imx_v6_v7_defconfig
>
> > It is maybe a bit complex, but it saves cloning the kernel for the sake
> > of just adding a single DTS with defconfig and a few patches.
>
> That is procedure I was looking for.
>
> > Hope this helps,
>
> Great helps, thank you so much.
>
> - jupiter
>
> > Bas.
> >
> --
> ___
> 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] How to define and build device tree in Yocto?

[JH]

Hi Bas and Gabriele,

Thank you so much for you advice.

> My usual way of doing it is as follows:
>
> I usually don't need to make large modifications to the kernel source,
> so I don't need to clone the kernel, but use the default kernel for the
> SoC with some patches.

So do I.

> I use a platform support layer and add a .bbappend file for the (arm)
> kernel to add a custom dts and .config files, together with some small
> patches:
>
> *** File meta-/recipes-kernel/linux/linux-_%.bbappend:
>
> THISAPPENDFILESDIR := "${THISDIR}/files"
> FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>
> require linux-set-custom-defconfig.inc
> require linux-add-custom-dts.inc
>
> # The first patch simply appends my custom DTS to the list of DTD files
> in the Makefile
> SRC_URI += \
>  "file://add-custom-dts.patch \
>   file://some_other.patch \
>   file://another_driver_patch.patch \
>  "
>
> *** File meta-/recipes-kernel/linux/linux-add-custom-dts.inc
>
> do_add_platform_dts() {
>   cp -f "${THISAPPENDFILESDIR}/custom.dts" \
>  "${WORKDIR}/git/arch/arm/boot/dts"
> }

That is exactly I am looking for the proper location of the dts files,
thank you so much.

> addtask add_platform_dts before do_preconfigure after do_patch
>
> *** File
> meta-/recipes-kernel/linux/linux-set-custom-defconfig.inc
>
> do_set_custom_defconfig() {
>  cp -f "${THISAPPENDFILESDIR}/defconfig" "${WORKDIR}/defconfig"
> }
>
> addtask set_custom_defconfig before do_preconfigure after do_patch

Good advice, I missed that one, how did you do the defconfig usually?
Compile it in kernel source like using following command?

make ARCH=arm imx_v6_v7_defconfig

> It is maybe a bit complex, but it saves cloning the kernel for the sake
> of just adding a single DTS with defconfig and a few patches.

That is procedure I was looking for.

> Hope this helps,

Great helps, thank you so much.

- jupiter

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

Re: [yocto] yocto sumo - upgrading gcc from 7.3 to 8.3 fails - C compiler cannot create executables

[Burton, Ross]

On Mon, 6 May 2019 at 17:28, Eric Grunt  wrote:
> | configure: error: C compiler cannot create executables
> | See `config.log' for more details

I suggest reading config.log for more details.

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

Re: [yocto] xilinx Zynq zedboard gnuradio

[Philip Balister]

On 05/06/2019 05:11 AM, Nitesh Guinde wrote:
> The following links were used to bitbake the image
> 
> https://github.com/balister/oe-gnuradio-manifest
> 
> https://wiki.gnuradio.org/index.php/Zynq

Note the line saying this page is obsolete. That page is around to
document gnuradio and zynq accelerators from several years ago.
Unfortunately, no one has carried on that work, at least publicly.

https://github.com/balister/sdr-build

is what I work with now for assembling images, but I haven't done
anything with the zc702 lately. Things should basically still though. In
meta-sdr master, the gnuradio recipe builds from teh master branch, this
is where I've been making sure the code builds and sometimes managing
runtime testing, although usually on a Beagle X15.

Philip


> 
> On Mon, May 6, 2019 at 2:40 PM Nitesh Guinde 
> wrote:
> 
>> Hi Philip,
>>
>> I am trying to port gnuradio onto zedboard. I used the following link
>> https://github.com/balister/oe-gnuradio-manifest
>>
>> and build the images folder for zedboard-zynq7.
>>  Then I copied uImage, boot.bin dtb and uenv.txt onto the sd card boot
>> partition
>>
>> untarred the gnradio-dev-image-zedboard-zynq7.tar.gz onto the rootfs
>> partition..
>>
>> However the card doesnt boot.
>>
>> Just wanted to find out if the process given in the following links are
>> fine or any other tweaking is needed.
>>
>>
>> Thanks,
>> Nitesh B. Guinde
>>
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto sumo - upgrading gcc from 7.3 to 8.3 fails - C compiler cannot create executables

[Zoran Stojsavljevic]

Hello Eric,

Please, could you try gcc 8.2?

Thank you,
Zoran
___

On Mon, May 6, 2019 at 6:28 PM Eric Grunt  wrote:
>
> Hi,
>
> I tried to upgrade gcc from 7.3 to 8.3 by copying
> gcc directory from https://github.com/openembedded/openembedded-core.git
> (openembedded-core/meta/recipes-devtools/gcc)
> to meta-custom-layer/recipes-gcc,
> replacing requires to recipes-devtools/gcc/*inc in all bb files in there,
> eg
> require recipes-devtools/gcc/gcc-${PV}.inc/require becomes
> require gcc-${PV}.inc,
>
> changing gcc and sdk Version in local.conf to 8.%
>
> GCCVERSION = "8.%"
> SDKGCCVERSION = "8.%"
>
> and by removing gcc-initial dependency from glibc.
>
> diff --git a/sources/poky/meta/recipes-core/glibc/glibc-initial.inc
> b/sources/poky/meta/recipes-core/glibc/glibc-initial.inc
> index b86e2fb..4df63ae 100644
> --- a/sources/poky/meta/recipes-core/glibc/glibc-initial.inc
> +++ b/sources/poky/meta/recipes-core/glibc/glibc-initial.inc
> @@ -1,4 +1,4 @@
> -DEPENDS = "linux-libc-headers virtual/${TARGET_PREFIX}gcc-initial
> libgcc-initial"
> +DEPENDS = "linux-libc-headers virtual/${TARGET_PREFIX}gcc libgcc-initial"
>  PROVIDES = "virtual/${TARGET_PREFIX}libc-initial"
>
>  PACKAGES = ""
> diff --git a/sources/poky/meta/recipes-core/glibc/glibc.inc
> b/sources/poky/meta/recipes-core/glibc/glibc.inc
> index ce1222b..69b15ec 100644
> --- a/sources/poky/meta/recipes-core/glibc/glibc.inc
> +++ b/sources/poky/meta/recipes-core/glibc/glibc.inc
> @@ -32,7 +32,7 @@ siteconfig_do_siteconfig_gencache_prepend = " \
>  "
>
>  # nptl needs unwind support in gcc, which can't be built without glibc.
> -DEPENDS = "virtual/${TARGET_PREFIX}gcc-initial libgcc-initial
> linux-libc-headers virtual/${TARGET_PREFIX}libc-initial"
> +DEPENDS = "virtual/${TARGET_PREFIX}gcc libgcc-initial
> linux-libc-headers virtual/${TARGET_PREFIX}libc-initial"
>  # nptl needs libgcc but dlopens it, so our shlibs code doesn't detect this
>  #RDEPENDS_${PN} += "${@['','libgcc']['nptl' in '${GLIBC_ADDONS}']}"
>
>
> After that, bitbake core-image-minimal fails at do_populate_sysroot
> step for glibc_2.27:
>
> | DEBUG: Executing shell function do_siteconfig_gencache
> | configure: WARNING: unrecognized options: --disable-silent-rules,
> --disable-dependency-tracking, --with-libtool-sysroot
> | configure: creating cache glibc_cache
> | checking for arm-poky-linux-gnueabi-gcc...
> arm-poky-linux-gnueabi-gcc  -march=armv7ve -marm -mfpu=neon
> -mfloat-abi=hard -mcpu=cortex-a7
> --sysroot=/home/yocto/sigma/yocto-sumo/build/tmp_dev/work/cortexa7hf-neon-poky-linux-gnueabi/glibc/2.27-r0/recipe-sysroot
> | checking whether the C compiler works... no
> | configure: error: in
> `/home/yocto/sigma/yocto-sumo/build/tmp_dev/work/cortexa7hf-neon-poky-linux-gnueabi/glibc/2.27-r0/site_config_imx6ul-var-dart':
> | configure: error: C compiler cannot create executables
> | See `config.log' for more details
> | WARNING: exit code 77 from a shell command.
> | DEBUG: Python function siteconfig_do_siteconfig finished
> | DEBUG: Python function do_siteconfig finished
> | DEBUG: Python function sstate_task_postfunc finished
> | ERROR: Function failed: do_siteconfig_gencache
>
> Do I have to perform something additional to be able to use gcc 8.3?
> --
> ___
> 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] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

[Volosincu, Andreea S]

Good points to keep in mind. I will add them to the agenda for the upcoming 
advocacy call.

Thanks!
Andreea

-Original Message-
From: Josef Holzmayr [mailto:holzm...@rsi-elektrotechnik.de] 
Sent: Monday, May 6, 2019 3:45 AM
To: Behan Webster 
Cc: Volosincu, Andreea S ; Yocto list 
discussion ; yocto-advoc...@yoctoproject.org
Subject: Re: [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer 
Days

I'd actually word it a little bit differently:

If there is only *ONE* attendee who did not properly do the homework, it will 
have a massive impact an the rest of the group. And that somebody will show up 
unpreparedly is absolutely certain in my opinion.

As someone who actually got started through the YPDD beginner track (and also 
often recommends it to new beginners), my opinion is clearly that we either 
should have it, be it only for a handful of attendees, or offer a *real* 
replacement, with face to face training. My experience is that this personal 
thing in the very beginning is an absolutely essential part of many YP/OE 
careers.

Greetz

On Sun, May 05, 2019 at 04:46:12PM -0700, Behan Webster wrote:
> Just for the record, speaking as a professional trainer, and someone who 
> makes material available before classes in the hopes that people will do 
> “pre-class homework”, almost nobody even glances through any material sent 
> before class. And many people claim to have never received it (for various 
> reasons, but often because it ends up ignored or in spam).
> 
> Essentially I wouldn’t count on anyone actually looking at anything before 
> arriving, because statistically nobody does.
> 
> Behan
> 
> Sent from my Mobile Computer which is also a phone
> 
> > On May 5, 2019, at 2:45 PM, Volosincu, Andreea S 
> >  wrote:
> > 
> > That’s correct. We’ll provide previous beginner material as pre-class 
> > homework.
> >  
> > Andreea
> >  
> > From: Behan Webster [mailto:beh...@converseincode.com]
> > Sent: Saturday, May 4, 2019 4:30 AM
> > To: Volosincu, Andreea S 
> > Cc: akuster ; yocto-advoc...@yoctoproject.org; 
> > Yocto list discussion 
> > Subject: Re: [Yocto-Advocacy] Yocto Project Upcoming Conferences and 
> > Developer Days
> >  
> > So does this mean there won’t be a beginner class at all?
> >  
> > Behan
> > 
> > Sent from my Mobile Computer which is also a phone
> > 
> > On May 3, 2019, at 6:01 PM, Volosincu, Andreea S 
> >  wrote:
> > 
> > Hi Armin,
> >  
> > Thanks for letting us know. The security summit overlaps with a lot of 
> > things, including the first ELC day.
> >  
> > Hopefully we can make it work by fine-tuning the agenda in such a way that 
> > you attend just the portion of the day that is interesting to you, or you 
> > are presenting.
> >  
> > Let’s talk more during the advocacy call.
> >  
> > Thanks!
> > Andreea
> >  
> > From: akuster [mailto:akus...@mvista.com]
> > Sent: Friday, May 3, 2019 11:07 AM
> > To: Volosincu, Andreea S ; 
> > yocto-advoc...@yoctoproject.org; Yocto list discussion 
> > 
> > Subject: Re: [Yocto-Advocacy] Yocto Project Upcoming Conferences and 
> > Developer Days
> >  
> >  
> > 
> > On 5/3/19 11:01 AM, Volosincu, Andreea S wrote:
> > Greetings,
> >  
> > Yocto Project is pleased to announce the plans for the upcoming Embedded 
> > Linux Conferences in NA and Europe.
> >  
> > Here is a snapshot of our schedule:
> >  
> > ELC NA – Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront, San 
> > Diego, CA
> >Yocto Project is a sponsor. We’ll see you on the 
> > show floor
> >  
> > ELC NA Dev Day – Tuesday, August 20, 2019 - 8:00AM - 6:00PM
> > Set-up: 1 Meeting Room - Classroom Seating ( 60 people)
> > Level: Intermediate – Advanced. Participants will receive beginner 
> > material (videos and presentations) as pre-requisites
> > Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with 
> > light appetizers So beer is a prerequisite for Intermediate level?
> > 
> > This is a conflict with Linux Security summit unless someone can convince 
> > me to be part of the training?
> > 
> > - armin
> > 
> > 
> > 
> >  
> > ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France
> >   Yocto Project is a sponsor. We’ll see you on the show 
> > floor
> >  
> > ELCE Yocto Project Summit – Dates & Times:
> > Thursday, October 31, 2019 - 8:00AM - 6:00PM
> >November 1, 2019 - 8:00 am - 6:00PM
> > Set-up:
> > Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project 
> > talks Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 
> > 60 & Classroom seating for 40 (for maintainers and users)
> > Includes:
> > Morning Break for 2 days
> > Buffet Lunch for 2 days
> > Beer & Wine Reception with light appetizers for 1 day The goal for 
> > the second day of the summit is to build and bring the community together. 
> > We are interested to hear your opinions and ideas on how that day and those 
> > rooms should be used for. Please send your ideas to Andr

Re: [yocto] Yocto Project Upcoming Conferences and Developer Days

[Volosincu, Andreea S]

Hi Joshua,

The event will be listed on the co-located events page and there will be a cost 
associated with it. Please check this page in a couple of days - 
https://events.linuxfoundation.org/events/elc-north-america-2019/program/co-located-events/

You will be able to add this to your ELC registration.

Thanks!
Andreea

From: Joshua Watt [mailto:jpewhac...@gmail.com]
Sent: Monday, May 6, 2019 8:07 AM
To: Volosincu, Andreea S ; 
yocto-advoc...@yoctoproject.org; Yocto list discussion 
Subject: Re: [yocto] Yocto Project Upcoming Conferences and Developer Days

On Fri, 2019-05-03 at 18:01 +, Volosincu, Andreea S wrote:
Greetings,

Yocto Project is pleased to announce the plans for the upcoming Embedded Linux 
Conferences in NA and Europe.

Here is a snapshot of our schedule:

ELC NA – Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront, San Diego, 
CA
   Yocto Project is a sponsor. We’ll see you on the show floor

ELC NA Dev Day – Tuesday, August 20, 2019 - 8:00AM - 6:00PM
Set-up: 1 Meeting Room - Classroom Seating ( 60 people)
Level: Intermediate – Advanced. Participants will receive beginner material 
(videos and presentations) as pre-requisites
Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with light 
appetizers

Is there any registration cost for this event, and how does one register?



ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France
  Yocto Project is a sponsor. We’ll see you on the show floor

ELCE Yocto Project Summit – Dates & Times:
Thursday, October 31, 2019 - 8:00AM - 6:00PM
   November 1, 2019 - 8:00 am - 6:00PM
Set-up:
Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project talks
Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 60 & Classroom 
seating for 40 (for maintainers and users)
Includes:
Morning Break for 2 days
Buffet Lunch for 2 days
Beer & Wine Reception with light appetizers for 1 day

The goal for the second day of the summit is to build and bring the community 
together. We are interested to hear your opinions and ideas on how that day and 
those rooms should be used for. Please send your ideas to Andreea Volosincu and 
Philip Balister.

We will call out an Advocacy meeting in a couple of weeks to go over plans and 
vote on the ideas for the second day of the summit.

Thanks!
Andreea
Yocto Project Advocacy Lead

--
Joshua Watt mailto:jpewhac...@gmail.com>>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Project Upcoming Conferences and Developer Days

[Volosincu, Andreea S]

Hi Greg,

Linux Foundation is adding the info right now. Please check back in a couple of 
days. The Dev Day will be listed with the co-located events and you will be 
able to add it to your ELC registration.

Thanks!
Andreea

-Original Message-
From: Greg Wilson-Lindberg [mailto:gwil...@sakuraus.com] 
Sent: Monday, May 6, 2019 10:06 AM
To: akuster ; Joshua Watt ; 
Volosincu, Andreea S ; 
yocto-advoc...@yoctoproject.org; Yocto list discussion 
Subject: RE: [yocto] Yocto Project Upcoming Conferences and Developer Days

I just visited the Embedded Linux Conference site and the Dev day on the 20th 
is not listed, does anyone know how to get more information on it. I'm very 
interested in attending along with one of my coworkers.
Regards,
Greg Wilson-Lindberg
Principal Firmware Engineer | Sakura Finetek USA, Inc.  
 

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of akuster
Sent: Monday, May 06, 2019 09:22 AM
To: Joshua Watt ; Volosincu, Andreea S 
; yocto-advoc...@yoctoproject.org; Yocto list 
discussion 
Subject: Re: [yocto] Yocto Project Upcoming Conferences and Developer Days


On 5/6/19 8:06 AM, Joshua Watt wrote:
On Fri, 2019-05-03 at 18:01 +, Volosincu, Andreea S wrote:
Greetings,
 
Yocto Project is pleased to announce the plans for the upcoming Embedded Linux 
Conferences in NA and Europe.
 
Here is a snapshot of our schedule:
 
ELC NA – Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront, San Diego, 
CA
       Yocto Project is a sponsor. We’ll see you on the show floor
 
ELC NA Dev Day – Tuesday, August 20, 2019 - 8:00AM - 6:00PM
   Set-up: 1 Meeting Room - Classroom Seating ( 60 people)
   Level: Intermediate – Advanced. Participants will receive beginner 
material (videos and presentations) as pre-requisites
   Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with light 
appetizers

Is there any registration cost for this event, and how does one register?
For the training portion there normally has been. I am sure the details will be 
provided once things are setup.

- armin


 
ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France
  Yocto Project is a sponsor. We’ll see you on the show floor
 
ELCE Yocto Project Summit – Dates & Times: 
   Thursday, October 31, 2019 - 8:00AM - 6:00PM
   November 1, 2019 - 8:00 am - 6:00PM
   Set-up: 
   Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project talks
   Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 60 & 
Classroom seating for 40 (for maintainers and users)
   Includes:
   Morning Break for 2 days
   Buffet Lunch for 2 days
   Beer & Wine Reception with light appetizers for 1 day The goal for the 
second day of the summit is to build and bring the community together. We are 
interested to hear your opinions and ideas on how that day and those rooms 
should be used for. Please send your ideas to Andreea Volosincu and Philip 
Balister.
 
We will call out an Advocacy meeting in a couple of weeks to go over plans and 
vote on the ideas for the second day of the summit.
 
Thanks!
Andreea
Yocto Project Advocacy Lead
--
Joshua Watt 



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

Re: [yocto] Yocto Project Upcoming Conferences and Developer Days

[Volosincu, Andreea S]

Hi Jupiter,

Melbourne Australia is not in the plan for the near future, but you could help 
remotely as well. 

For instance, have you checked out the first live streaming that we had? 
Developers worldwide could help us with this, showing other developers how they 
work with the project. Here it is: https://www.twitch.tv/yocto_project/videos. 
Please let me know what you think.

Thanks!
Andreea

-Original Message-
From: JH [mailto:jupiter@gmail.com] 
Sent: Saturday, May 4, 2019 4:50 AM
To: Volosincu, Andreea S 
Cc: yocto-advoc...@yoctoproject.org; Yocto list discussion 

Subject: Re: [yocto] Yocto Project Upcoming Conferences and Developer Days

Any planning to have a conference to Melbourne Australia in the near future? I 
am keen to help.

Thank you.

Kind regards,

- jupiter

On 5/4/19, Volosincu, Andreea S  wrote:
> Greetings,
>
> Yocto Project is pleased to announce the plans for the upcoming 
> Embedded Linux Conferences in NA and Europe.
>
> Here is a snapshot of our schedule:
>
> ELC NA - Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront, 
> San Diego, CA
>Yocto Project is a sponsor. We'll see you on the 
> show floor
>
> ELC NA Dev Day - Tuesday, August 20, 2019 - 8:00AM - 6:00PM
> Set-up: 1 Meeting Room - Classroom Seating ( 60 people)
> Level: Intermediate - Advanced. Participants will receive beginner 
> material (videos and presentations) as pre-requisites
> Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with 
> light appetizers
>
> ELCE - Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France
>   Yocto Project is a sponsor. We'll see you on the show 
> floor
>
> ELCE Yocto Project Summit - Dates & Times:
> Thursday, October 31, 2019 - 8:00AM - 6:00PM
>November 1, 2019 - 8:00 am - 6:00PM
> Set-up:
> Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project 
> talks Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 60 
> & Classroom seating for 40 (for maintainers and users)
> Includes:
> Morning Break for 2 days
> Buffet Lunch for 2 days
> Beer & Wine Reception with light appetizers for 1 day The goal for the 
> second day of the summit is to build and bring the community together. 
> We are interested to hear your opinions and ideas on how that day and 
> those rooms should be used for. Please send your ideas to Andreea 
> Volosincu and Philip Balister.
>
> We will call out an Advocacy meeting in a couple of weeks to go over 
> plans and vote on the ideas for the second day of the summit.
>
> Thanks!
> Andreea
> Yocto Project Advocacy Lead
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Project Upcoming Conferences and Developer Days

[Greg Wilson-Lindberg]

I just visited the Embedded Linux Conference site and the Dev day on the 20th 
is not listed, does anyone know how to get more information on it. I'm very 
interested in attending along with one of my coworkers.
Regards,
Greg Wilson-Lindberg  
Principal Firmware Engineer | Sakura Finetek USA, Inc.  
 

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of akuster
Sent: Monday, May 06, 2019 09:22 AM
To: Joshua Watt ; Volosincu, Andreea S 
; yocto-advoc...@yoctoproject.org; Yocto list 
discussion 
Subject: Re: [yocto] Yocto Project Upcoming Conferences and Developer Days


On 5/6/19 8:06 AM, Joshua Watt wrote:
On Fri, 2019-05-03 at 18:01 +, Volosincu, Andreea S wrote:
Greetings,
 
Yocto Project is pleased to announce the plans for the upcoming Embedded Linux 
Conferences in NA and Europe.
 
Here is a snapshot of our schedule:
 
ELC NA – Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront, San Diego, 
CA
       Yocto Project is a sponsor. We’ll see you on the show floor
 
ELC NA Dev Day – Tuesday, August 20, 2019 - 8:00AM - 6:00PM
   Set-up: 1 Meeting Room - Classroom Seating ( 60 people)
   Level: Intermediate – Advanced. Participants will receive beginner 
material (videos and presentations) as pre-requisites
   Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with light 
appetizers

Is there any registration cost for this event, and how does one register?
For the training portion there normally has been. I am sure the details will be 
provided once things are setup.

- armin


 
ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France
  Yocto Project is a sponsor. We’ll see you on the show floor
 
ELCE Yocto Project Summit – Dates & Times: 
   Thursday, October 31, 2019 - 8:00AM - 6:00PM 
   November 1, 2019 - 8:00 am - 6:00PM
   Set-up: 
   Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project talks
   Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 60 & 
Classroom seating for 40 (for maintainers and users)
   Includes:
   Morning Break for 2 days
   Buffet Lunch for 2 days
   Beer & Wine Reception with light appetizers for 1 day
The goal for the second day of the summit is to build and bring the community 
together. We are interested to hear your opinions and ideas on how that day and 
those rooms should be used for. Please send your ideas to Andreea Volosincu and 
Philip Balister.
 
We will call out an Advocacy meeting in a couple of weeks to go over plans and 
vote on the ideas for the second day of the summit.
 
Thanks!
Andreea
Yocto Project Advocacy Lead
-- 
Joshua Watt 



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

[yocto] yocto sumo - upgrading gcc from 7.3 to 8.3 fails - C compiler cannot create executables

[Eric Grunt]

Hi,

I tried to upgrade gcc from 7.3 to 8.3 by copying
gcc directory from https://github.com/openembedded/openembedded-core.git
(openembedded-core/meta/recipes-devtools/gcc)
to meta-custom-layer/recipes-gcc,
replacing requires to recipes-devtools/gcc/*inc in all bb files in there,
eg
require recipes-devtools/gcc/gcc-${PV}.inc/require becomes
require gcc-${PV}.inc,

changing gcc and sdk Version in local.conf to 8.%

GCCVERSION = "8.%"
SDKGCCVERSION = "8.%"

and by removing gcc-initial dependency from glibc.

diff --git a/sources/poky/meta/recipes-core/glibc/glibc-initial.inc
b/sources/poky/meta/recipes-core/glibc/glibc-initial.inc
index b86e2fb..4df63ae 100644
--- a/sources/poky/meta/recipes-core/glibc/glibc-initial.inc
+++ b/sources/poky/meta/recipes-core/glibc/glibc-initial.inc
@@ -1,4 +1,4 @@
-DEPENDS = "linux-libc-headers virtual/${TARGET_PREFIX}gcc-initial
libgcc-initial"
+DEPENDS = "linux-libc-headers virtual/${TARGET_PREFIX}gcc libgcc-initial"
 PROVIDES = "virtual/${TARGET_PREFIX}libc-initial"

 PACKAGES = ""
diff --git a/sources/poky/meta/recipes-core/glibc/glibc.inc
b/sources/poky/meta/recipes-core/glibc/glibc.inc
index ce1222b..69b15ec 100644
--- a/sources/poky/meta/recipes-core/glibc/glibc.inc
+++ b/sources/poky/meta/recipes-core/glibc/glibc.inc
@@ -32,7 +32,7 @@ siteconfig_do_siteconfig_gencache_prepend = " \
 "

 # nptl needs unwind support in gcc, which can't be built without glibc.
-DEPENDS = "virtual/${TARGET_PREFIX}gcc-initial libgcc-initial
linux-libc-headers virtual/${TARGET_PREFIX}libc-initial"
+DEPENDS = "virtual/${TARGET_PREFIX}gcc libgcc-initial
linux-libc-headers virtual/${TARGET_PREFIX}libc-initial"
 # nptl needs libgcc but dlopens it, so our shlibs code doesn't detect this
 #RDEPENDS_${PN} += "${@['','libgcc']['nptl' in '${GLIBC_ADDONS}']}"


After that, bitbake core-image-minimal fails at do_populate_sysroot
step for glibc_2.27:

| DEBUG: Executing shell function do_siteconfig_gencache
| configure: WARNING: unrecognized options: --disable-silent-rules,
--disable-dependency-tracking, --with-libtool-sysroot
| configure: creating cache glibc_cache
| checking for arm-poky-linux-gnueabi-gcc...
arm-poky-linux-gnueabi-gcc  -march=armv7ve -marm -mfpu=neon
-mfloat-abi=hard -mcpu=cortex-a7
--sysroot=/home/yocto/sigma/yocto-sumo/build/tmp_dev/work/cortexa7hf-neon-poky-linux-gnueabi/glibc/2.27-r0/recipe-sysroot
| checking whether the C compiler works... no
| configure: error: in
`/home/yocto/sigma/yocto-sumo/build/tmp_dev/work/cortexa7hf-neon-poky-linux-gnueabi/glibc/2.27-r0/site_config_imx6ul-var-dart':
| configure: error: C compiler cannot create executables
| See `config.log' for more details
| WARNING: exit code 77 from a shell command.
| DEBUG: Python function siteconfig_do_siteconfig finished
| DEBUG: Python function do_siteconfig finished
| DEBUG: Python function sstate_task_postfunc finished
| ERROR: Function failed: do_siteconfig_gencache

Do I have to perform something additional to be able to use gcc 8.3?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Project Upcoming Conferences and Developer Days

[akuster]

On 5/6/19 8:06 AM, Joshua Watt wrote:
> On Fri, 2019-05-03 at 18:01 +, Volosincu, Andreea S wrote:
>>
>> Greetings,
>>
>>  
>>
>> Yocto Project is pleased to announce the plans for the upcoming
>> Embedded Linux Conferences in NA and Europe.
>>
>>  
>>
>> Here is a snapshot of our schedule:
>>
>>  
>>
>> ELC NA – Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront,
>> San Diego, CA
>>
>>        Yocto Project is a sponsor. We’ll see you on the
>> show floor
>>
>>  
>>
>> ELC NA Dev Day – Tuesday, August 20, 2019 - 8:00AM - 6:00PM
>>
>> Set-up: 1 Meeting Room - Classroom Seating ( 60 people)
>>
>> Level: Intermediate – Advanced. Participants will receive beginner
>> material (videos and presentations) as pre-requisites
>>
>> Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with
>> light appetizers
>>
>
> Is there any registration cost for this event, and how does one register?
For the training portion there normally has been. I am sure the details
will be provided once things are setup.

- armin
>
>>  
>>
>> ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France
>>
>>   Yocto Project is a sponsor. We’ll see you on the show floor
>>
>>  
>>
>> ELCE Yocto Project Summit – Dates & Times:
>>
>> Thursday, October 31, 2019 - 8:00AM - 6:00PM
>>
>>    November 1, 2019 - 8:00 am - 6:00PM
>>
>> Set-up:
>>
>> Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project talks
>>
>> Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 60 &
>> Classroom seating for 40 (for maintainers and users)
>>
>> Includes:
>>
>> Morning Break for 2 days
>>
>> Buffet Lunch for 2 days
>>
>> Beer & Wine Reception with light appetizers for 1 day
>>
>> The goal for the second day of the summit is to build and bring the
>> community together. We are interested to hear your opinions and ideas
>> on how that day and those rooms should be used for. Please send your
>> ideas to Andreea Volosincu and Philip Balister.
>>
>>  
>>
>> We will call out an Advocacy meeting in a couple of weeks to go over
>> plans and vote on the ideas for the second day of the summit.
>>
>>  
>>
>> Thanks!
>>
>> Andreea
>>
>> Yocto Project Advocacy Lead
>>
> -- 
> Joshua Watt mailto:jpewhac...@gmail.com>>
>

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

Re: [yocto] xilinx Zynq zedboard gnuradio

[Nitesh Guinde]

The following links were used to bitbake the image

https://github.com/balister/oe-gnuradio-manifest

https://wiki.gnuradio.org/index.php/Zynq

On Mon, May 6, 2019 at 2:40 PM Nitesh Guinde 
wrote:

> Hi Philip,
>
> I am trying to port gnuradio onto zedboard. I used the following link
> https://github.com/balister/oe-gnuradio-manifest
>
> and build the images folder for zedboard-zynq7.
>  Then I copied uImage, boot.bin dtb and uenv.txt onto the sd card boot
> partition
>
> untarred the gnradio-dev-image-zedboard-zynq7.tar.gz onto the rootfs
> partition..
>
> However the card doesnt boot.
>
> Just wanted to find out if the process given in the following links are
> fine or any other tweaking is needed.
>
>
> Thanks,
> Nitesh B. Guinde
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] xilinx Zynq zedboard gnuradio

[Nitesh Guinde]

Hi Philip,

I am trying to port gnuradio onto zedboard. I used the following link
https://github.com/balister/oe-gnuradio-manifest

and build the images folder for zedboard-zynq7.
 Then I copied uImage, boot.bin dtb and uenv.txt onto the sd card boot
partition

untarred the gnradio-dev-image-zedboard-zynq7.tar.gz onto the rootfs
partition..

However the card doesnt boot.

Just wanted to find out if the process given in the following links are
fine or any other tweaking is needed.


Thanks,
Nitesh B. Guinde
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Defining group of machines

[Westermann, Oliver]

> > is that what you were after?
> override is the first thing that crossed my mind...   

Thanks both of you, an additional machine override was exactly what we needed.

Best regards, Olli
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

[Bas Mevissen]

On 5/6/19 12:45 PM, Josef Holzmayr wrote:

I'd actually word it a little bit differently:

If there is only *ONE* attendee who did not properly do the homework, it
will have a massive impact an the rest of the group. And that somebody
will show up unpreparedly is absolutely certain in my opinion.



With sufficient trainers, one can continue for most and provide some 
assistance to the one falling behind.



As someone who actually got started through the YPDD beginner track (and
also often recommends it to new beginners), my opinion is clearly that
we either should have it, be it only for a handful of attendees, or
offer a *real* replacement, with face to face training. My experience is
that this personal thing in the very beginning is an absolutely
essential part of many YP/OE careers.



I agree. That is how I started, next to a compressed Linux Foundation 
Yocto training that was offered just before the event then.


So it might be wise to ask LF or get something organised. It would 
mostly require a room and a sponsor for some small devkit.




Greetz

On Sun, May 05, 2019 at 04:46:12PM -0700, Behan Webster wrote:

Just for the record, speaking as a professional trainer, and someone who makes 
material available before classes in the hopes that people will do “pre-class 
homework”, almost nobody even glances through any material sent before class. 
And many people claim to have never received it (for various reasons, but often 
because it ends up ignored or in spam).

Essentially I wouldn’t count on anyone actually looking at anything before 
arriving, because statistically nobody does.

Behan

Sent from my Mobile Computer which is also a phone


On May 5, 2019, at 2:45 PM, Volosincu, Andreea S 
 wrote:

That’s correct. We’ll provide previous beginner material as pre-class homework.
  
Andreea
  
From: Behan Webster [mailto:beh...@converseincode.com]

Sent: Saturday, May 4, 2019 4:30 AM
To: Volosincu, Andreea S 
Cc: akuster ; yocto-advoc...@yoctoproject.org; Yocto list 
discussion 
Subject: Re: [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer 
Days
  
So does this mean there won’t be a beginner class at all?
  
Behan


Sent from my Mobile Computer which is also a phone

On May 3, 2019, at 6:01 PM, Volosincu, Andreea S 
 wrote:

Hi Armin,
  
Thanks for letting us know. The security summit overlaps with a lot of things, including the first ELC day.
  
Hopefully we can make it work by fine-tuning the agenda in such a way that you attend just the portion of the day that is interesting to you, or you are presenting.
  
Let’s talk more during the advocacy call.
  
Thanks!

Andreea
  
From: akuster [mailto:akus...@mvista.com]

Sent: Friday, May 3, 2019 11:07 AM
To: Volosincu, Andreea S ; 
yocto-advoc...@yoctoproject.org; Yocto list discussion 
Subject: Re: [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer 
Days
  
  


On 5/3/19 11:01 AM, Volosincu, Andreea S wrote:
Greetings,
  
Yocto Project is pleased to announce the plans for the upcoming Embedded Linux Conferences in NA and Europe.
  
Here is a snapshot of our schedule:
  
ELC NA – Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront, San Diego, CA

Yocto Project is a sponsor. We’ll see you on the show floor
  
ELC NA Dev Day – Tuesday, August 20, 2019 - 8:00AM - 6:00PM

Set-up: 1 Meeting Room - Classroom Seating ( 60 people)
Level: Intermediate – Advanced. Participants will receive beginner material 
(videos and presentations) as pre-requisites
Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with light 
appetizers
So beer is a prerequisite for Intermediate level?

This is a conflict with Linux Security summit unless someone can convince me to 
be part of the training?

- armin



  
ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France

   Yocto Project is a sponsor. We’ll see you on the show floor
  
ELCE Yocto Project Summit – Dates & Times:

Thursday, October 31, 2019 - 8:00AM - 6:00PM
November 1, 2019 - 8:00 am - 6:00PM
Set-up:
Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project talks
Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 60 & Classroom 
seating for 40 (for maintainers and users)
Includes:
Morning Break for 2 days
Buffet Lunch for 2 days
Beer & Wine Reception with light appetizers for 1 day
The goal for the second day of the summit is to build and bring the community 
together. We are interested to hear your opinions and ideas on how that day and 
those rooms should be used for. Please send your ideas to Andreea Volosincu and 
Philip Balister.
  
We will call out an Advocacy meeting in a couple of weeks to go over plans and vote on the ideas for the second day of the summit.
  
Thanks!

Andreea
Yocto Project Advocacy Lead



  
--

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

Re: [yocto] Yocto Project Upcoming Conferences and Developer Days

[Bas Mevissen]

On 5/6/19 5:06 PM, Joshua Watt wrote:

On Fri, 2019-05-03 at 18:01 +, Volosincu, Andreea S wrote:


Greetings,

Yocto Project is pleased to announce the plans for the upcoming 
Embedded Linux Conferences in NA and Europe.


Here is a snapshot of our schedule:

ELC NA – Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront, 
San Diego, CA


       Yocto Project is a sponsor. We’ll see you on the 
show floor


ELC NA Dev Day – Tuesday, August 20, 2019 - 8:00AM - 6:00PM

Set-up: 1 Meeting Room - Classroom Seating ( 60 people)

Level: Intermediate – Advanced. Participants will receive beginner 
material (videos and presentations) as pre-requisites


Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with 
light appetizers




Is there any registration cost for this event, and how does one register?



ELC and ELCE are Linux Foundation organised events. Check their website 
for the pricing.



ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France

  Yocto Project is a sponsor. We’ll see you on the show floor

ELCE Yocto Project Summit – Dates & Times:

Thursday, October 31, 2019 - 8:00AM - 6:00PM

   November 1, 2019 - 8:00 am - 6:00PM

Set-up:

Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project talks

Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 60 & 
Classroom seating for 40 (for maintainers and users)


Includes:

Morning Break for 2 days

Buffet Lunch for 2 days

Beer & Wine Reception with light appetizers for 1 day

The goal for the second day of the summit is to build and bring the 
community together. We are interested to hear your opinions and ideas 
on how that day and those rooms should be used for. Please send your 
ideas to Andreea Volosincu and Philip Balister.


We will call out an Advocacy meeting in a couple of weeks to go over 
plans and vote on the ideas for the second day of the summit.


Thanks!

Andreea

Yocto Project Advocacy Lead


--

Joshua Watt mailto:jpewhac...@gmail.com>>



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

Re: [yocto] Yocto Project Upcoming Conferences and Developer Days

[Joshua Watt]

On Fri, 2019-05-03 at 18:01 +, Volosincu, Andreea S wrote:
> Greetings,
> 
>  
> 
> Yocto Project is pleased to announce the plans for the upcoming
> Embedded Linux Conferences in NA and Europe.
> 
>  
> 
> Here is a snapshot of our schedule:
> 
>  
> 
> ELC NA – Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront,
> San Diego, CA
> 
>Yocto Project is a sponsor. We’ll see you on the
> show floor
> 
>  
> 
> ELC NA Dev Day – Tuesday, August 20, 2019 - 8:00AM - 6:00PM
> 
> Set-up: 1 Meeting Room - Classroom Seating ( 60 people)
> 
> Level: Intermediate – Advanced. Participants will receive beginner
> material (videos and presentations) as pre-requisites
> 
> Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with
> light appetizers

Is there any registration cost for this event, and how does one
register?
>  
> ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon,
> France
>   Yocto Project is a sponsor. We’ll see you on the show
> floor
>  
> ELCE Yocto Project Summit – Dates & Times: 
> Thursday, October 31, 2019 - 8:00AM - 6:00PM
> 
>November 1, 2019 - 8:00 am - 6:00PM
> Set-up: 
> Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project
> talks
> Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 60 &
> Classroom seating for 40 (for maintainers and users)
> Includes:
> Morning Break for 2 days
> Buffet Lunch for 2 days
> Beer & Wine Reception with light appetizers for 1 day
> 
> The goal for the second day of the summit is to build and bring the
> community together. We are interested to hear your opinions and ideas
> on how that day and those rooms should be used for. Please send your
> ideas to Andreea Volosincu and
>  Philip Balister.
>  
> We will call out an Advocacy meeting in a couple of weeks to go over
> plans and vote on the ideas for the second day of the summit.
>  
> Thanks!
> Andreea
> Yocto Project Advocacy Lead
> 
> 
> 
-- 
Joshua Watt 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to define and build device tree in Yocto?

[Bas Mevissen]

On 5/5/19 2:03 PM, JH wrote:

Hi,



Hi JH,


I think the device tree blob is build from device tree source, but I
could not find any dts files in recipe source directory, there are
many dts files in build directory and there are dtb in build
directory.



Already answered by Gabriele.


If I have a device tree source, where I should put it and how to
define the recipe to built it?



My usual way of doing it is as follows:

I usually don't need to make large modifications to the kernel source, 
so I don't need to clone the kernel, but use the default kernel for the 
SoC with some patches.


I use a platform support layer and add a .bbappend file for the (arm) 
kernel to add a custom dts and .config files, together with some small 
patches:


*** File meta-/recipes-kernel/linux/linux-_%.bbappend:

THISAPPENDFILESDIR := "${THISDIR}/files"
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

require linux-set-custom-defconfig.inc
require linux-add-custom-dts.inc

# The first patch simply appends my custom DTS to the list of DTD files 
in the Makefile

SRC_URI += \
"file://add-custom-dts.patch \
 file://some_other.patch \
 file://another_driver_patch.patch \
"

*** File meta-/recipes-kernel/linux/linux-add-custom-dts.inc

do_add_platform_dts() {
cp -f "${THISAPPENDFILESDIR}/custom.dts" \
"${WORKDIR}/git/arch/arm/boot/dts"
}

addtask add_platform_dts before do_preconfigure after do_patch

*** File meta-/recipes-kernel/linux/linux-set-custom-defconfig.inc

do_set_custom_defconfig() {
cp -f "${THISAPPENDFILESDIR}/defconfig" "${WORKDIR}/defconfig"
}

addtask set_custom_defconfig before do_preconfigure after do_patch


It is maybe a bit complex, but it saves cloning the kernel for the sake 
of just adding a single DTS with defconfig and a few patches.


Hope this helps,

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

Re: [yocto] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

[Ta, Lieu]

Andreea, Philip and I had a pre-planning call and we all agreed that we want to 
solicit the community for ideas and then finalizing them at an Advocacy 
meeting. We are doing something different this year.  If you do not want to 
send ideas to this wide distribution, please don’t hesitate to send them 
directly to Andreea 
(andreea.volosi...@windriver.com).

It takes a lot of hard work to plan, promote, and execute these events, 
especially when the work is all on volunteering basis.  If you can help with 
the planning please also send Andreea a note.

Again, I would like to remind everyone that the CALL to ACTION is to submit 
IDEAS for the upcoming events.  My responses to the criticisms are inline below.


Regards,
Lieu Ta
Advisory Board Chair, Yocto Project

From: yocto-advocacy-boun...@yoctoproject.org 
 On Behalf Of Behan Webster
Sent: Sunday, May 05, 2019 5:08 PM
To: Volosincu, Andreea S 
Cc: Yocto list discussion ; 
yocto-advoc...@yoctoproject.org
Subject: Re: [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer 
Days

If community building is the plan please don’t exclude OpenEmbedded from the 
name nor the material (in other words, acknowledging which parts are from 
OpenEmbedded). Part of the community building aspect is going to have to be 
acknowledging that Yocto Project is an umbrella project made up of other 
projects, and then celebrating those projects.
[Ta, Lieu] Noted

The original idea I put forward was to have a joint OpenEmbedded/Yocto project 
2-day event to replace the separate ypdd and OEDEM, not merely a larger Yocto 
project event.

I am personally already seeing a negative reaction to these plans from others, 
which is IMHO sadly contributing to destroying community instead of building it.
[Ta, Lieu] I am personally seeing positive reaction that we’re promoting Yocto 
Project and Open Embedded..  We can’t please everyone.  If we want to build 
together, we need to stand together.  Nitpicking and negativity would only 
crack the foundation we’re building on.

I, personally, would like nothing more than a simpler way to describe the whole 
thing. However as it stands we essentially have 2 camps that continue to 
separate instead of coming together. Let’s try and fix that bit first.
[Ta, Lieu] We are two camps if we continue to define ourselves so.

And I surely hope that things other than beer and wine are made available. 
There are actually a lot of attendees who don’t drink from what I can tell, 
which was made extremely evident to me in Edinburgh where the non alcoholic 
options kept on running out and how much alcohol was left at the end of the 
night. Wine and beer isn’t a draw for everyone anymore.
[Ta, Lieu] While I agree that the wine was not a big winner, beers were 
excessively appreciated.  The wines were traded in for beers by popular 
demands.  The beers were practically gone when I left.
However, the idea of adding more soft drinks to the mix, is a good one.

Thanks,

Behan
Sent from my Mobile Computer which is also a phone

On May 3, 2019, at 11:01 AM, Volosincu, Andreea S 
mailto:andreea.volosi...@windriver.com>> wrote:
Greetings,

Yocto Project is pleased to announce the plans for the upcoming Embedded Linux 
Conferences in NA and Europe.

Here is a snapshot of our schedule:

ELC NA – Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront, San Diego, 
CA
   Yocto Project is a sponsor. We’ll see you on the show floor

ELC NA Dev Day – Tuesday, August 20, 2019 - 8:00AM - 6:00PM
Set-up: 1 Meeting Room - Classroom Seating ( 60 people)
Level: Intermediate – Advanced. Participants will receive beginner material 
(videos and presentations) as pre-requisites
Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with light 
appetizers

ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France
  Yocto Project is a sponsor. We’ll see you on the show floor

ELCE Yocto Project Summit – Dates & Times:
Thursday, October 31, 2019 - 8:00AM - 6:00PM
   November 1, 2019 - 8:00 am - 6:00PM
Set-up:
Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project talks
Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 60 & Classroom 
seating for 40 (for maintainers and users)
Includes:
Morning Break for 2 days
Buffet Lunch for 2 days
Beer & Wine Reception with light appetizers for 1 day
The goal for the second day of the summit is to build and bring the community 
together. We are interested to hear your opinions and ideas on how that day and 
those rooms should be used for. Please send your ideas to Andreea Volosincu and 
Philip Balister.

We will call out an Advocacy meeting in a couple of weeks to go over plans and 
vote on the ideas for the second day of the summit.

Thanks!
Andreea
Yocto Project Advocacy Lead
--
___
yocto-advocacy mailing list
yocto-advoc...@yoctoproject.org

Re: [yocto] [PATCH 3/3] recipes-bsp/u-boot: update to the latest version

[Trevor Woerner]

On Sat 2019-05-04 @ 06:43:34 PM, ayaka wrote:
> 
> On 5/4/19 11:06 AM, Trevor Woerner wrote:
> > On Wed 2019-04-24 @ 10:59:18 PM, Randy 'ayaka' Li wrote:
> > > From: Randy Li 
> > > 
> > > Signed-off-by: Randy Li 
> > > ---
> > >   recipes-bsp/u-boot/u-boot-rockchip_git.bb | 18 ++
> > >   1 file changed, 18 insertions(+)
> > >   create mode 100644 recipes-bsp/u-boot/u-boot-rockchip_git.bb
> > > 
> > > diff --git a/recipes-bsp/u-boot/u-boot-rockchip_git.bb 
> > > b/recipes-bsp/u-boot/u-boot-rockchip_git.bb
> > > new file mode 100644
> > > index 000..aa4b84d
> > > --- /dev/null
> > > +++ b/recipes-bsp/u-boot/u-boot-rockchip_git.bb
> > > @@ -0,0 +1,18 @@
> > > +# Copyright (C) 2019 SUMOMO Computer Assocation
> > > +# Released under the MIT license (see COPYING.MIT for the terms)
> > > +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> > > +
> > > +include u-boot-rockchip.inc
> > > +
> > > +DESCRIPTION = "Rockchip U-Boot"
> > > +
> > > +LIC_FILES_CHKSUM = 
> > > "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6"
> > > +
> > > +SRC_URI = " \
> > > + git://github.com/rockchip-linux/u-boot.git;branch=release; \
> > > + file://binutils-2.28-ld-fix.patch \
> > > + file://gcc7_fixup.patch \
> > > + "
> > > +
> > > +S = "${WORKDIR}/git"
> > > +PV = "v2019.01"
> > This doesn't even get past the fetching stage:
> I am sorry, I forget that ssh git protocol only work for those users who
> uploaded their key to the github, I would change it back to https.
> > 
> > WARNING: u-boot-rockchip-1_v2019.01-r0 do_fetch: Failed to fetch URL 
> > git://github.com/rockchip-linux/u-boot.git;branch=release;, attempting 
> > MIRRORS if available
> > ERROR: u-boot-rockchip-1_v2019.01-r0 do_fetch: Fetcher failure: Unable 
> > to find revision 3c99166441bf3ea325af2da83cfe65430b49c066 in branch release 
> > even from upstream
> > ERROR: u-boot-rockchip-1_v2019.01-r0 do_fetch: Fetcher failure for URL: 
> > 'git://github.com/rockchip-linux/u-boot.git;branch=release;'. Unable to 
> > fetch URL from any source.
> > ERROR: u-boot-rockchip-1_v2019.01-r0 do_fetch:
> > ERROR: u-boot-rockchip-1_v2019.01-r0 do_fetch: Function failed: 
> > base_do_fetch
> > ERROR: Task 
> > (/opt/oe/configs/z/build-master/meta-rockchip/layers/meta-rockchip/recipes-bsp/u-boot/u-boot-rockchip_git.bb:do_fetch)
> >  failed with exit code '1'

The problem is that it's trying to fetch commit 3c9916 which doesn't exist on
github.com/rockchip-linux/u-boot.git. That revision is on upstream U-Boot.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Multiple ubifs partition

[Gabriele Zampieri]

Perfect, thank you!

Gabriele

Il giorno lun 6 mag 2019 alle ore 14:15 Ulrich Ölmann <
u.oelm...@pengutronix.de> ha scritto:

> Hi Gabriele,
>
> On Mon, May 06 2019 at 13:32 +0200, Gabriele Zampieri <
> gabbla.mal...@gmail.com> wrote:
> > thank you very much for your explanation. The provided genimage.config
> > looks similar to mine, so I guess it is ok. I will try when I come back
> to
> > the office. The point I missed was that I need to call: bitbake
> > your-customized-ubi and not bitbake my-custom-image, right?
>
> correct - "my-custom-image" will indirectly become a dependency via the
> variable GENIMAGE_ROOTFS_IMAGE, see [1].
>
> Best regards
> Ulrich
>
>
> [1]
> https://github.com/pengutronix/meta-ptx/blob/master/classes/genimage.bbclass#L88
>
> > Thank you again,
> > Gabriele
> >
> >
> > Il giorno ven 3 mag 2019 alle ore 07:59 Ulrich Ölmann <
> > u.oelm...@pengutronix.de> ha scritto:
> >
> >> Hi Gabriele,
> >>
> >> On Thu, May 02 2019 at 13:25 +0200, Gabriele Zampieri <
> >> gabbla.mal...@gmail.com> wrote:
> >> > ok, I guess I miss-understand how that class works. I thought that I
> >> > had to add the customization on my own image recipe.
> >> > So the correct way is to write a 'customization recipe' and install
> >> > via IMAGE_INSTALL? Can you provide an example?
> >>
> >> use your custom image recipe as before to just produce your root-
> >> filesystem which results in a (compressed) tar-file in ${DEPLOY_DIR_
> >> IMAGE}. It will be referenced from the genimage recipe without any file
> >> extension via GENIMAGE_ROOTFS_IMAGE. Now your UBI-recipe (e.g. 'your-
> >> customized-ubi.bb') could look like
> >>
> >> inherit genimage
> >> LICENSE = "MIT"
> >> LIC_FILES_CHKSUM =
> >>
> "file://${COREBASE}/meta/files/common-licenses/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
> >>
> >> SRC_URI += "file://genimage.config"
> >>
> >> # to not confuse the flashable UBI-image ('ubi')
> >> # with the UBI-filesystems ('ubifs') it contains
> >> GENIMAGE_IMAGE_SUFFIX = "ubi"
> >>
> >> # the name of the root-filesystem genimage should use
> >> GENIMAGE_ROOTFS_IMAGE = "your-customized-rootfs"
> >>
> >> with the accompanying 'genimage.config' for example as follows
> >>
> >> #
> >> # Manufacturer ID: 0x2c, Chip ID: 0xda
> >> # -> Micron MT29F2G08ABAEAWP
> >> # 256 MiB, SLC
> >> #
> >> flash nand {
> >> pebsize = 131072
> >> lebsize = 126976
> >> numpebs = 2044
> >> minimum-io-unit-size = 2048
> >> sub-page-size = 2048
> >> }
> >>
> >> image @IMAGE@ {
> >> flashtype = "nand"
> >> ubi {
> >> }
> >>
> >> partition rootfs {
> >> image = rootfs.ubifs
> >> size = 64MiB
> >> }
> >>
> >> partition opt {
> >> image = opt.ubifs
> >> size = 32MiB
> >> }
> >>
> >> partition data {
> >> image = data.ubifs
> >> autoresize = true
> >> }
> >> }
> >>
> >> image rootfs.ubifs {
> >> flashtype = "nand"
> >> ubifs {
> >> extraargs = "-x lzo"
> >> max-size = 64MiB
> >> }
> >> mountpoint = "/"
> >> }
> >>
> >> image opt.ubifs {
> >> flashtype = "nand"
> >> ubifs {
> >> extraargs = "-x lzo"
> >> max-size = 32MiB
> >> }
> >> mountpoint = "/opt"
> >> }
> >>
> >> image data.ubifs {
> >> flashtype = "nand"
> >> ubifs {
> >> extraargs = "-x lzo"
> >> max-size = 192MiB
> >> }
> >> mountpoint = "/data"
> >> }
> >>
> >> In a UBI-image almost all UBI-volumes need to have a fixed size and only
> >> one is allowed to use the autoresize mechanism which blows it up to use
> >> the remaining space when it is UBI-attached for the first time. Distinct
> >> from that is the UBI-filesystem's max-size parameter which prescribes
> >> the maximum size of an UBI-volume that shall be addressable by this
> >> filesystem. This means that if you would re-use 'data.ubifs' in a volume
> >> that has been autoresized to e.g. 1024MiB the filesystem would not be
> >> able to make use of it.
> >>
> >> I neither tested the recipe nor the genimage.config, so please give some
> >> feedback.
> >>
> >> Best regards
> >> Ulrich
> >>
> >>
> >> > Thanks,
> >> > Gabriele
> >> >
> >> > Il giorno mer 24 apr 2019 alle ore 15:15 Ulrich Ölmann <
> >> > u.oelm...@pengutronix.de> ha scritto:
> >> >
> >> >> Hi Gabriele,
> >> >>
> >> >> On Wed, Apr 24 2019 at 14:06 +0200, Gabriele Zampieri <
> >> >> gabbla.mal...@gmail.com> wrote:
> >> >> > I'm now testing genimage via meta-ptx in my Yocto workflow, but I
> >> found a
> >> >> > problem: I cannot set a SRC_URI in my custom image recipe (that
> >> inherit
> >> >> > from core-image which in turn inherit from image) because do_fetch
> and
> >> >> > do_unpack

Re: [yocto] Multiple ubifs partition

[Ulrich Ölmann]

Hi Gabriele,

On Mon, May 06 2019 at 13:32 +0200, Gabriele Zampieri  
wrote:
> thank you very much for your explanation. The provided genimage.config
> looks similar to mine, so I guess it is ok. I will try when I come back to
> the office. The point I missed was that I need to call: bitbake
> your-customized-ubi and not bitbake my-custom-image, right?

correct - "my-custom-image" will indirectly become a dependency via the
variable GENIMAGE_ROOTFS_IMAGE, see [1].

Best regards
Ulrich


[1] 
https://github.com/pengutronix/meta-ptx/blob/master/classes/genimage.bbclass#L88

> Thank you again,
> Gabriele
>
>
> Il giorno ven 3 mag 2019 alle ore 07:59 Ulrich Ölmann <
> u.oelm...@pengutronix.de> ha scritto:
>
>> Hi Gabriele,
>>
>> On Thu, May 02 2019 at 13:25 +0200, Gabriele Zampieri <
>> gabbla.mal...@gmail.com> wrote:
>> > ok, I guess I miss-understand how that class works. I thought that I
>> > had to add the customization on my own image recipe.
>> > So the correct way is to write a 'customization recipe' and install
>> > via IMAGE_INSTALL? Can you provide an example?
>>
>> use your custom image recipe as before to just produce your root-
>> filesystem which results in a (compressed) tar-file in ${DEPLOY_DIR_
>> IMAGE}. It will be referenced from the genimage recipe without any file
>> extension via GENIMAGE_ROOTFS_IMAGE. Now your UBI-recipe (e.g. 'your-
>> customized-ubi.bb') could look like
>>
>> inherit genimage
>> LICENSE = "MIT"
>> LIC_FILES_CHKSUM =
>> "file://${COREBASE}/meta/files/common-licenses/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
>>
>> SRC_URI += "file://genimage.config"
>>
>> # to not confuse the flashable UBI-image ('ubi')
>> # with the UBI-filesystems ('ubifs') it contains
>> GENIMAGE_IMAGE_SUFFIX = "ubi"
>>
>> # the name of the root-filesystem genimage should use
>> GENIMAGE_ROOTFS_IMAGE = "your-customized-rootfs"
>>
>> with the accompanying 'genimage.config' for example as follows
>>
>> #
>> # Manufacturer ID: 0x2c, Chip ID: 0xda
>> # -> Micron MT29F2G08ABAEAWP
>> # 256 MiB, SLC
>> #
>> flash nand {
>> pebsize = 131072
>> lebsize = 126976
>> numpebs = 2044
>> minimum-io-unit-size = 2048
>> sub-page-size = 2048
>> }
>>
>> image @IMAGE@ {
>> flashtype = "nand"
>> ubi {
>> }
>>
>> partition rootfs {
>> image = rootfs.ubifs
>> size = 64MiB
>> }
>>
>> partition opt {
>> image = opt.ubifs
>> size = 32MiB
>> }
>>
>> partition data {
>> image = data.ubifs
>> autoresize = true
>> }
>> }
>>
>> image rootfs.ubifs {
>> flashtype = "nand"
>> ubifs {
>> extraargs = "-x lzo"
>> max-size = 64MiB
>> }
>> mountpoint = "/"
>> }
>>
>> image opt.ubifs {
>> flashtype = "nand"
>> ubifs {
>> extraargs = "-x lzo"
>> max-size = 32MiB
>> }
>> mountpoint = "/opt"
>> }
>>
>> image data.ubifs {
>> flashtype = "nand"
>> ubifs {
>> extraargs = "-x lzo"
>> max-size = 192MiB
>> }
>> mountpoint = "/data"
>> }
>>
>> In a UBI-image almost all UBI-volumes need to have a fixed size and only
>> one is allowed to use the autoresize mechanism which blows it up to use
>> the remaining space when it is UBI-attached for the first time. Distinct
>> from that is the UBI-filesystem's max-size parameter which prescribes
>> the maximum size of an UBI-volume that shall be addressable by this
>> filesystem. This means that if you would re-use 'data.ubifs' in a volume
>> that has been autoresized to e.g. 1024MiB the filesystem would not be
>> able to make use of it.
>>
>> I neither tested the recipe nor the genimage.config, so please give some
>> feedback.
>>
>> Best regards
>> Ulrich
>>
>>
>> > Thanks,
>> > Gabriele
>> >
>> > Il giorno mer 24 apr 2019 alle ore 15:15 Ulrich Ölmann <
>> > u.oelm...@pengutronix.de> ha scritto:
>> >
>> >> Hi Gabriele,
>> >>
>> >> On Wed, Apr 24 2019 at 14:06 +0200, Gabriele Zampieri <
>> >> gabbla.mal...@gmail.com> wrote:
>> >> > I'm now testing genimage via meta-ptx in my Yocto workflow, but I
>> found a
>> >> > problem: I cannot set a SRC_URI in my custom image recipe (that
>> inherit
>> >> > from core-image which in turn inherit from image) because do_fetch and
>> >> > do_unpack tasks have noexec set to 1. If I specify the SRC_URI with my
>> >> > genimage.config, bitbake exits, complaining about LIC_FILE_CHECKSUM
>> (that
>> >> > is correctly specified). If I hack image.bbclass and comment out
>> >> >
>> >> > #do_fetch[noexec] = "1"
>> >> >
>> >> >
>> >> > #do_unpack[noexec] = "1"
>> >> >
>> >> > The process start correctly. Is there a way to avoid touching
>> >> image.bbclass
>> >> > and install my configuration from t

Re: [yocto] Multiple ubifs partition

[Gabriele Zampieri]

Hi Ulrich,

thank you very much for your explanation. The provided genimage.config
looks similar to mine, so I guess it is ok. I will try when I come back to
the office. The point I missed was that I need to call: bitbake
your-customized-ubi and not bitbake my-custom-image, right?

Thank you again,
Gabriele


Il giorno ven 3 mag 2019 alle ore 07:59 Ulrich Ölmann <
u.oelm...@pengutronix.de> ha scritto:

> Hi Gabriele,
>
> On Thu, May 02 2019 at 13:25 +0200, Gabriele Zampieri <
> gabbla.mal...@gmail.com> wrote:
> > ok, I guess I miss-understand how that class works. I thought that I
> > had to add the customization on my own image recipe.
> > So the correct way is to write a 'customization recipe' and install
> > via IMAGE_INSTALL? Can you provide an example?
>
> use your custom image recipe as before to just produce your root-
> filesystem which results in a (compressed) tar-file in ${DEPLOY_DIR_
> IMAGE}. It will be referenced from the genimage recipe without any file
> extension via GENIMAGE_ROOTFS_IMAGE. Now your UBI-recipe (e.g. 'your-
> customized-ubi.bb') could look like
>
> inherit genimage
> LICENSE = "MIT"
> LIC_FILES_CHKSUM =
> "file://${COREBASE}/meta/files/common-licenses/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
>
> SRC_URI += "file://genimage.config"
>
> # to not confuse the flashable UBI-image ('ubi')
> # with the UBI-filesystems ('ubifs') it contains
> GENIMAGE_IMAGE_SUFFIX = "ubi"
>
> # the name of the root-filesystem genimage should use
> GENIMAGE_ROOTFS_IMAGE = "your-customized-rootfs"
>
> with the accompanying 'genimage.config' for example as follows
>
> #
> # Manufacturer ID: 0x2c, Chip ID: 0xda
> # -> Micron MT29F2G08ABAEAWP
> # 256 MiB, SLC
> #
> flash nand {
> pebsize = 131072
> lebsize = 126976
> numpebs = 2044
> minimum-io-unit-size = 2048
> sub-page-size = 2048
> }
>
> image @IMAGE@ {
> flashtype = "nand"
> ubi {
> }
>
> partition rootfs {
> image = rootfs.ubifs
> size = 64MiB
> }
>
> partition opt {
> image = opt.ubifs
> size = 32MiB
> }
>
> partition data {
> image = data.ubifs
> autoresize = true
> }
> }
>
> image rootfs.ubifs {
> flashtype = "nand"
> ubifs {
> extraargs = "-x lzo"
> max-size = 64MiB
> }
> mountpoint = "/"
> }
>
> image opt.ubifs {
> flashtype = "nand"
> ubifs {
> extraargs = "-x lzo"
> max-size = 32MiB
> }
> mountpoint = "/opt"
> }
>
> image data.ubifs {
> flashtype = "nand"
> ubifs {
> extraargs = "-x lzo"
> max-size = 192MiB
> }
> mountpoint = "/data"
> }
>
> In a UBI-image almost all UBI-volumes need to have a fixed size and only
> one is allowed to use the autoresize mechanism which blows it up to use
> the remaining space when it is UBI-attached for the first time. Distinct
> from that is the UBI-filesystem's max-size parameter which prescribes
> the maximum size of an UBI-volume that shall be addressable by this
> filesystem. This means that if you would re-use 'data.ubifs' in a volume
> that has been autoresized to e.g. 1024MiB the filesystem would not be
> able to make use of it.
>
> I neither tested the recipe nor the genimage.config, so please give some
> feedback.
>
> Best regards
> Ulrich
>
>
> > Thanks,
> > Gabriele
> >
> > Il giorno mer 24 apr 2019 alle ore 15:15 Ulrich Ölmann <
> > u.oelm...@pengutronix.de> ha scritto:
> >
> >> Hi Gabriele,
> >>
> >> On Wed, Apr 24 2019 at 14:06 +0200, Gabriele Zampieri <
> >> gabbla.mal...@gmail.com> wrote:
> >> > I'm now testing genimage via meta-ptx in my Yocto workflow, but I
> found a
> >> > problem: I cannot set a SRC_URI in my custom image recipe (that
> inherit
> >> > from core-image which in turn inherit from image) because do_fetch and
> >> > do_unpack tasks have noexec set to 1. If I specify the SRC_URI with my
> >> > genimage.config, bitbake exits, complaining about LIC_FILE_CHECKSUM
> (that
> >> > is correctly specified). If I hack image.bbclass and comment out
> >> >
> >> > #do_fetch[noexec] = "1"
> >> >
> >> >
> >> > #do_unpack[noexec] = "1"
> >> >
> >> > The process start correctly. Is there a way to avoid touching
> >> image.bbclass
> >> > and install my configuration from the image recipe?
> >> >
> >> > Thanks,
> >> > Gabriele
> >>
> >> you need one or more recipe(s) that construct(s) your filesystem(s) and
> >> a separate one that makes a flashable image out of that (see the
> >> introductory documentation in 'genimage.bbclass'). In the former you
> >> inherit 'core-image' and only in the latter which inherits 'genimage'
> >> you have to set the SRC_URI to point to your 'genimage.config'.
> >>
> >> Best reg

Re: [yocto] How to define and build device tree in Yocto?

[Gabriele Zampieri]

Hi,

> but there is no imx6ull-14x14-evk.dts

it is located in arch/arm/boot/dts/imx6ull-14x14-evk.dts and it is compiled
(among others dts) while building virtual/kernel task.

Setting KERNEL_DEVICETREE =  "imx6ull-14x14-evk.dtb" simply tells to
bitbake to put a copy of imx6ull-14x14-evk.dtb inside your image deploy
directory. You can dig through meta/classes/kernel-devicetree.bbclass to
see how KERNEL_DEVICETREE is used.

If you do not need to modify the dts, you will find all the image related
stuff in poky/build/tmp/deploy/images//.

If you need to patch the dts (or any other kernel related file):

- Clone you kernel source tree locally
- Checkout the correct branch
- Do your edits, then commit
- Get a patch with the customization through git format-patch (or any other
way)

Now, in your meta layer:
- create recipes-kernel/linux/.bbappend file
- create recipes-kernel/linux/files// directory

Then:
- Copy your patch in recipes-kernel/linux/files/
- Edit the bbappend file with:
FILESEXTRAPATHS_prepend := "${THISDIR}/files:" # Add files to the search
paths
SRC_URI_append_ = " file://0001-your-commit-message.patch"

bitbake will apply the patch after the kernel unpack automatically, then
build the tree with the patch(es) applied.

You can also add a completely new dts via patch, then add it to
KERNEL_DEVICETREE.

Best regards,
Gabriele

Il giorno lun 6 mag 2019 alle ore 09:36 JH  ha
scritto:

> Thanks Gabriele,
>
> Yes, I have already added KERNEL_DEVICETREE =  "imx6ull-14x14-evk.dtb"
> to generate an image running on imx6 EVK. What I don't understand is
> how that imx6ull-14x14-evk.dtb was compiled? I thought all dtb are
> compiled from dts files, but there is no imx6ull-14x14-evk.dts, the
> imx6ullevk.conf defined the EVK but there is no detail in that file.
>
> My second question is my new hardware based on imx6ull MCU now has a
> dts file, since I could not see any samples how is the dtb compiled
> from a dts file, I have no idea where to put the dts file, how to link
> that dts file to generate a dtb file in recipe. Appreciate more
> clarification.
>
> Thank you.
>
> - jh
>
> On 5/6/19, Gabriele Zampieri  wrote:
> > Hi,
> >
> > The easiest way is to add them via patches. You can write a recipe that
> > patch the Linux tree and put it in your meta layer (usually in
> > meta-xxx/recipes-kernel/linux). Then you need to tell Yocto to export the
> > dtb via KERNEL_DEVICETREE variable (
> >
> https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-KERNEL_DEVICETREE
> ).
> > I usually put this variable in my machine configuration.
> >
> > Gabriele
> >
> > Il giorno dom 5 mag 2019 alle ore 14:04 JH  ha
> > scritto:
> >
> >> Hi,
> >>
> >> I think the device tree blob is build from device tree source, but I
> >> could not find any dts files in recipe source directory, there are
> >> many dts files in build directory and there are dtb in build
> >> directory.
> >>
> >> If I have a device tree source, where I should put it and how to
> >> define the recipe to built it?
> >>
> >> Thank you.
> >>
> >> Kind regards,
> >>
> >> - jupiter
> >> --
> >> ___
> >> 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] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

[Josef Holzmayr]

Howdy!

On Sun, May 05, 2019 at 05:07:30PM -0700, Behan Webster wrote:
> If community building is the plan please don’t exclude OpenEmbedded from the 
> name nor the material (in other words, acknowledging which parts are from 
> OpenEmbedded). Part of the community building aspect is going to have to be 
> acknowledging that Yocto Project is an umbrella project made up of other 
> projects, and then celebrating those projects.
> 
> The original idea I put forward was to have a joint OpenEmbedded/Yocto 
> project 2-day event to replace the separate ypdd and OEDEM, not merely a 
> larger Yocto project event.
> 
> I am personally already seeing a negative reaction to these plans from 
> others, which is IMHO sadly contributing to destroying community instead of 
> building it.
> 
> I, personally, would like nothing more than a simpler way to describe the 
> whole thing. However as it stands we essentially have 2 camps that continue 
> to separate instead of coming together. Let’s try and fix that bit first.

Completely agreed. I've personally never understood the (until now,
mostly) friendly mutual heckling, but its a thing we have to cope with
and sort out. The sooner, the better.
 
> And I surely hope that things other than beer and wine are made available. 
> There are actually a lot of attendees who don’t drink from what I can tell, 
> which was made extremely evident to me in Edinburgh where the non alcoholic 
> options kept on running out and how much alcohol was left at the end of the 
> night. Wine and beer isn’t a draw for everyone anymore.

Another point I'm just stepping up to fully support. We can run out of
booze - its better if we don't but hey, we absolutely must not run out
of water and coffee.

Greetz

PS: Yes, its actually *ME* writing that.

> 
> Thanks,
> 
> Behan
> 
> Sent from my Mobile Computer which is also a phone
> 
> > On May 3, 2019, at 11:01 AM, Volosincu, Andreea S 
> >  wrote:
> > 
> > Greetings,
> >  
> > Yocto Project is pleased to announce the plans for the upcoming Embedded 
> > Linux Conferences in NA and Europe.
> >  
> > Here is a snapshot of our schedule:
> >  
> > ELC NA – Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront, San 
> > Diego, CA
> >Yocto Project is a sponsor. We’ll see you on the show 
> > floor
> >  
> > ELC NA Dev Day – Tuesday, August 20, 2019 - 8:00AM - 6:00PM
> > Set-up: 1 Meeting Room - Classroom Seating ( 60 people)
> > Level: Intermediate – Advanced. Participants will receive beginner material 
> > (videos and presentations) as pre-requisites
> > Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with light 
> > appetizers
> >  
> > ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France
> >   Yocto Project is a sponsor. We’ll see you on the show floor
> >  
> > ELCE Yocto Project Summit – Dates & Times:
> > Thursday, October 31, 2019 - 8:00AM - 6:00PM
> >November 1, 2019 - 8:00 am - 6:00PM
> > Set-up:
> > Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project talks
> > Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 60 & Classroom 
> > seating for 40 (for maintainers and users)
> > Includes:
> > Morning Break for 2 days
> > Buffet Lunch for 2 days
> > Beer & Wine Reception with light appetizers for 1 day
> > The goal for the second day of the summit is to build and bring the 
> > community together. We are interested to hear your opinions and ideas on 
> > how that day and those rooms should be used for. Please send your ideas to 
> > Andreea Volosincu and Philip Balister.
> >  
> > We will call out an Advocacy meeting in a couple of weeks to go over plans 
> > and vote on the ideas for the second day of the summit.
> >  
> > Thanks!
> > Andreea
> > Yocto Project Advocacy Lead
> > -- 
> > ___
> > yocto-advocacy mailing list
> > yocto-advoc...@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto-advocacy

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


-- 
———
Josef Holzmayr
Software Developer Embedded Systems

Tel: +49 8444 9204-48
Fax: +49 8444 9204-50

R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
www.rsi-elektrotechnik.de
———
Amtsgericht Ingolstadt – GmbH: HRB 191328 – KG: HRA 170393
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
Ust-IdNr: DE 128592548 

_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548

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

Re: [yocto] [Yocto-Advocacy] Yocto Project Upcoming Conferences and Developer Days

[Josef Holzmayr]

I'd actually word it a little bit differently:

If there is only *ONE* attendee who did not properly do the homework, it
will have a massive impact an the rest of the group. And that somebody
will show up unpreparedly is absolutely certain in my opinion.

As someone who actually got started through the YPDD beginner track (and
also often recommends it to new beginners), my opinion is clearly that
we either should have it, be it only for a handful of attendees, or
offer a *real* replacement, with face to face training. My experience is
that this personal thing in the very beginning is an absolutely
essential part of many YP/OE careers.

Greetz

On Sun, May 05, 2019 at 04:46:12PM -0700, Behan Webster wrote:
> Just for the record, speaking as a professional trainer, and someone who 
> makes material available before classes in the hopes that people will do 
> “pre-class homework”, almost nobody even glances through any material sent 
> before class. And many people claim to have never received it (for various 
> reasons, but often because it ends up ignored or in spam).
> 
> Essentially I wouldn’t count on anyone actually looking at anything before 
> arriving, because statistically nobody does.
> 
> Behan
> 
> Sent from my Mobile Computer which is also a phone
> 
> > On May 5, 2019, at 2:45 PM, Volosincu, Andreea S 
> >  wrote:
> > 
> > That’s correct. We’ll provide previous beginner material as pre-class 
> > homework.
> >  
> > Andreea
> >  
> > From: Behan Webster [mailto:beh...@converseincode.com] 
> > Sent: Saturday, May 4, 2019 4:30 AM
> > To: Volosincu, Andreea S 
> > Cc: akuster ; yocto-advoc...@yoctoproject.org; Yocto 
> > list discussion 
> > Subject: Re: [Yocto-Advocacy] Yocto Project Upcoming Conferences and 
> > Developer Days
> >  
> > So does this mean there won’t be a beginner class at all?
> >  
> > Behan
> > 
> > Sent from my Mobile Computer which is also a phone
> > 
> > On May 3, 2019, at 6:01 PM, Volosincu, Andreea S 
> >  wrote:
> > 
> > Hi Armin,
> >  
> > Thanks for letting us know. The security summit overlaps with a lot of 
> > things, including the first ELC day.
> >  
> > Hopefully we can make it work by fine-tuning the agenda in such a way that 
> > you attend just the portion of the day that is interesting to you, or you 
> > are presenting.
> >  
> > Let’s talk more during the advocacy call.
> >  
> > Thanks!
> > Andreea
> >  
> > From: akuster [mailto:akus...@mvista.com] 
> > Sent: Friday, May 3, 2019 11:07 AM
> > To: Volosincu, Andreea S ; 
> > yocto-advoc...@yoctoproject.org; Yocto list discussion 
> > 
> > Subject: Re: [Yocto-Advocacy] Yocto Project Upcoming Conferences and 
> > Developer Days
> >  
> >  
> > 
> > On 5/3/19 11:01 AM, Volosincu, Andreea S wrote:
> > Greetings,
> >  
> > Yocto Project is pleased to announce the plans for the upcoming Embedded 
> > Linux Conferences in NA and Europe.
> >  
> > Here is a snapshot of our schedule:
> >  
> > ELC NA – Wednesday, August 21 - 23, 2019, Hilton San Diego Bayfront, San 
> > Diego, CA
> >Yocto Project is a sponsor. We’ll see you on the show 
> > floor
> >  
> > ELC NA Dev Day – Tuesday, August 20, 2019 - 8:00AM - 6:00PM
> > Set-up: 1 Meeting Room - Classroom Seating ( 60 people)
> > Level: Intermediate – Advanced. Participants will receive beginner material 
> > (videos and presentations) as pre-requisites
> > Includes: Morning Break, Buffet Lunch, Beer & Wine Reception with light 
> > appetizers
> > So beer is a prerequisite for Intermediate level?
> > 
> > This is a conflict with Linux Security summit unless someone can convince 
> > me to be part of the training?
> > 
> > - armin
> > 
> > 
> > 
> >  
> > ELCE – Monday, October 28 -30, 2019, Lyon Convention Centre, Lyon, France
> >   Yocto Project is a sponsor. We’ll see you on the show floor
> >  
> > ELCE Yocto Project Summit – Dates & Times:
> > Thursday, October 31, 2019 - 8:00AM - 6:00PM
> >November 1, 2019 - 8:00 am - 6:00PM
> > Set-up:
> > Day 1: 1 Meeting Room - Theater Seating for 100 for Yocto Project talks
> > Day 2: 2 Meeting Rooms - Mixed Classroom/Theater seating for 60 & Classroom 
> > seating for 40 (for maintainers and users)
> > Includes:
> > Morning Break for 2 days
> > Buffet Lunch for 2 days
> > Beer & Wine Reception with light appetizers for 1 day
> > The goal for the second day of the summit is to build and bring the 
> > community together. We are interested to hear your opinions and ideas on 
> > how that day and those rooms should be used for. Please send your ideas to 
> > Andreea Volosincu and Philip Balister.
> >  
> > We will call out an Advocacy meeting in a couple of weeks to go over plans 
> > and vote on the ideas for the second day of the summit.
> >  
> > Thanks!
> > Andreea
> > Yocto Project Advocacy Lead
> > 
> > 
> > 
> >  
> > -- 
> > ___
> > yocto-advocacy mailing list
> > yocto-advoc...@yoctoproject.org
> > https://lists.yoctoproject.or

[yocto] gdb remote debugging not working correctly

[Moritz Porst]

Hello everyone,

I am having trouble to remote debug using gdb (v 8.2.0) with QTCreator (4.8.0).

My remote target features QT 5.12.0. I configured it like the following ( only relevant configurations ) :

---

inherit populate_sdk_qt5 # QT5 in SDK
 

IMAGE_INSTALL_append = " gdbserver"

IMAGE_FEATURES_append = " dev-pkgs dbg-pkgs" # dbg-pkgs for debug-libraries. Not sure if the dev-pkgs is really required, but it should not do any harm (except for bloat the image)

---

Now from my build/development machine I start the QT example "boxes". Executing in debug configuration >locally< it takes around 5 seconds to hit the first breakpoint (at the very beginning of main). On a breakpoint after the widget was created I can expand the widget variable which contains 8 objects. I can further expand (e.g.) [QWidget] which again contains several objects like [QObject].

Executing the debug configuration >remote< only takes around 1 second until first breakpoint. Expanding "widget" shows it is empty. No objects at all and the "expand arrow" is gone. When trying to step out of the actual main using f11 ("step into") I receive a SIGSEGV.

 

What I tried but didn't work:

- build the SDK again (because I had an older version)

- check versions: gdbserver on remote target (8.2.0); gdb on development machine (8.2.0)

- tried system gdb (7.11.1) which shows the exact same behaviour.

 

In remote debugging I am however able to use breakpoints, step through MY code (not code coming from 3rd party libraries -> SIGSEGV) and expanding variables that do not come from 3rd party variables (like argv).

I am not sure on how to proceed from here. It might be that I do something wrong but it could also be that this is an actual bug in gdb (?).

 

Any advice is appreciated ! System information below.

 

Best regards

Moritz

 

System information:

Target uses a modified intel-corei7-64 machine and modified poky distribution. I removed following distro features:

DISTRO_FEATURES_remove = "bluetooth alsa wifi 3g wayland vulkan pulseaudio bluez5"

Dev machine runs an ubuntu 16.04.

 

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

Re: [yocto] How to define and build device tree in Yocto?

[JH]

Thanks Gabriele,

Yes, I have already added KERNEL_DEVICETREE =  "imx6ull-14x14-evk.dtb"
to generate an image running on imx6 EVK. What I don't understand is
how that imx6ull-14x14-evk.dtb was compiled? I thought all dtb are
compiled from dts files, but there is no imx6ull-14x14-evk.dts, the
imx6ullevk.conf defined the EVK but there is no detail in that file.

My second question is my new hardware based on imx6ull MCU now has a
dts file, since I could not see any samples how is the dtb compiled
from a dts file, I have no idea where to put the dts file, how to link
that dts file to generate a dtb file in recipe. Appreciate more
clarification.

Thank you.

- jh

On 5/6/19, Gabriele Zampieri  wrote:
> Hi,
>
> The easiest way is to add them via patches. You can write a recipe that
> patch the Linux tree and put it in your meta layer (usually in
> meta-xxx/recipes-kernel/linux). Then you need to tell Yocto to export the
> dtb via KERNEL_DEVICETREE variable (
> https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-KERNEL_DEVICETREE).
> I usually put this variable in my machine configuration.
>
> Gabriele
>
> Il giorno dom 5 mag 2019 alle ore 14:04 JH  ha
> scritto:
>
>> Hi,
>>
>> I think the device tree blob is build from device tree source, but I
>> could not find any dts files in recipe source directory, there are
>> many dts files in build directory and there are dtb in build
>> directory.
>>
>> If I have a device tree source, where I should put it and how to
>> define the recipe to built it?
>>
>> Thank you.
>>
>> Kind regards,
>>
>> - jupiter
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto