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

[Gabriele Zampieri]

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

[Volosincu, Andreea S]

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 
mailto:andreea.volosi...@windriver.com>> 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 
mailto:andreea.volosi...@windriver.com>>; 
yocto-advoc...@yoctoproject.org; Yocto 
list discussion mailto:yocto@yoctoproject.org>>
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
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

[JH]

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

Re: [yocto] [meta-mingw][PATCH V2] testsdk: enhance extract sdk part

[Changqing Li]

Hi, Joshua

OE-core patch have merge to master: 
https://git.openembedded.org/openembedded-core/commit/?id=57a33048a89a422cfdc986d3489c67b2d297e1e7


please help to merge this patch, thanks.

On 1/21/19 10:47 PM, Joshua Watt wrote:

Just FYI, I haven't forgot about this patch. I want to wait until the
dependent OE-core patch is at least in the master-next branch before I
apply this to the MinGW master-next branch. If you want to give me a
ping when the OE-core patch shows up in master-next, it would be very
helpful.

Thanks

On Thu, 2019-01-17 at 17:49 +0800, changqing...@windriver.com wrote:

From: Changqing Li 

Current sdk type is tar.xz, but for mingw sdk, since we
have symlink under the sdk folder, 7zip which used to
extract tar.xz cannot handle it, refer 7zip upstream bug:
https://sourceforge.net/p/sevenzip/discussion/45797/thread/c71d6b96/
so oe-core have add support of change SDK type to .zip, so correct
the extract function.

Signed-off-by: Changqing Li 
---
  lib/oeqa/sdkmingw/testsdk.py | 11 +--
  1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/lib/oeqa/sdkmingw/testsdk.py
b/lib/oeqa/sdkmingw/testsdk.py
index 85fe3c6..173cfd9 100644
--- a/lib/oeqa/sdkmingw/testsdk.py
+++ b/lib/oeqa/sdkmingw/testsdk.py
@@ -12,7 +12,7 @@ class TestSDKMinGW(TestSDK):
  """
  Get the name of the SDK file
  """
-return
d.expand("${SDK_DEPLOY}/${TOOLCHAIN_OUTPUTNAME}.tar.xz")
+return
d.expand("${SDK_DEPLOY}/${TOOLCHAIN_OUTPUTNAME}.${SDK_ARCHIVE_TYPE}")
  
  def extract_sdk(self, tcname, sdk_dir, d):

  """
@@ -23,7 +23,14 @@ class TestSDKMinGW(TestSDK):
  try:
  # TODO: It would be nice to try and extract the SDK in
Wine to make
  # sure it is well formed
-subprocess.check_output(['tar', '-xf', tcname, '-C',
sdk_dir])
+
+# TODO: Extract SDK according to SDK_ARCHIVE_TYPE, need
to change if
+# oe-core support other types.
+if d.getVar("SDK_ARCHIVE_TYPE") == "zip":
+subprocess.check_output(['unzip', '-d', sdk_dir,
tcname])
+else:
+subprocess.check_output(['tar', '-xf', tcname, '-C',
sdk_dir])
+
  except subprocess.CalledProcessError as e:
  bb.fatal("Couldn't install the SDK:\n%s" %
e.output.decode("utf-8"))
  
--

2.7.4


--
BRs

Sandy(Li Changqing)

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